Posts: 101
Threads: 20
Joined: Feb 2014
Reputation:
0
Have 2 of these.
https://www.ebay.com.au/p/SATA-IDE-HDD-U...717&chn=ps
Works in Windows 7 & 10.
Whether connected via Esata or USB the entry in thunar for the drive has a spiney thing appear next to it but never loads the contents of a 3.63gb (in real terms) sata drive (WD Green WD40EZRX)
Have updated iscsi and the result is the same.
Cheers.
J
I'm just this guy ... Y'know!?
Registered Linux User 533331
Posts: 508
Threads: 55
Joined: Jan 2015
Have exactly the same Docking station.
Been using it on Linux Lite for last 18 months .
Currently booting LL 4.0 no problems at all.
I am connecting Dock with usb.
Posts: 101
Threads: 20
Joined: Feb 2014
Reputation:
0
Just found out it's any spinning platten drive, thumb drives are the only external media to succesfully mount
I'm just this guy ... Y'know!?
Registered Linux User 533331
Posts: 8,895
Threads: 541
Joined: Feb 2014
Reputation:
5
Have you tried accessing them via Disks?
Posts: 101
Threads: 20
Joined: Feb 2014
Reputation:
0
Yes, all seems as it should be except the drives entry is in red txt, the drives not set as bootable nor can Drives Mount them, they are all NTFS, have spent some time in gparted with this result on all drives
Could not mount /dev/sdb1 on /mnt/wwn-0x50014ee000d6b090-part1
[/size]
"# mount -v '/dev/sdb1' '/mnt/wwn-0x50014ee000d6b090-part1'
$MFTMirr does not match $MFT (record 24).
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.
# mount -v -t 'ntfs' '/dev/sdb1' '/mnt/wwn-0x50014ee000d6b090-part1'
$MFTMirr does not match $MFT (record 24).
Failed to mount '/dev/sdb1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details."
No faults are found when checked in microsoft [/size]chkdsk
I'm just this guy ... Y'know!?
Registered Linux User 533331
Posts: 101
Threads: 20
Joined: Feb 2014
Reputation:
0
A 265gb 2.5" drive was succesfully repaired by disks, the 4tb drive contues as unseable and disks fails to repair, perhaps the error the kernal detects yet Windows does not is something tolerable in Win yet intolerable in Linux.
I'm just this guy ... Y'know!?
Registered Linux User 533331
Posts: 8,895
Threads: 541
Joined: Feb 2014
Reputation:
5
Did you try the commands at the end of that page?
Posts: 101
Threads: 20
Joined: Feb 2014
Reputation:
0
Drive still unuseable, the scan took 14 hours.
C:\WINDOWS\system32>chkdsk /r e:
The type of the file system is NTFS.
Volume label is 2nd3.63tb green.
Stage 1: Examining basic file system structure ...
5888 file records processed.
File verification completed.
62 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
2492 reparse records processed.
6082 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
2492 reparse records processed.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
98 data files processed.
CHKDSK is verifying Usn Journal...
12187240 USN bytes processed.
Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
5872 files processed.
File data verification completed.
Stage 5: Looking for bad, free clusters ...
37340647 free clusters processed.
Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
3815317 MB total disk space.
1516979968 KB in 3654 files.
8640 KB in 99 indexes.
0 KB in bad sectors.
95615 KB in use by the system.
65536 KB occupied by the log file.
2333790 MB available on disk.
65536 bytes in each allocation unit.
61045087 total allocation units on disk.
37340647 allocation units available on disk.
C:\WINDOWS\system32>
I'm just this guy ... Y'know!?
Registered Linux User 533331