Your drive has an internal problem, possibly a firmware issue.
Can you show us the output of the ATA Identify Device command?
Smartmontools can do this, as can CrystalDiskInfo and others.
Can you also retrieve a SMART report?
If you would be prepared to indulge me, I could help you try to retrieve
the drive's firmware modules. This will help us to determine whether there
is anything we could do at the physical level to get your drive to the
point where ddrescue will be able to work with it. There is no "logical"
software tool which will be able to retrieve a single byte from your drive
in its present state. Therefore I respectfully suggest that you stop
hammering it with ddrescue and others.
-Franc Zabkar
At 08:52 AM 6/05/14, you wrote:
I'm trying to rescue a HDD and I first issued this command:
# ddrescue -vv --no-split /dev/sde /mnt/flash/sde.img
/mnt/flash/sde.log
GNU ddrescue 1.16
About to copy 2199 GBytes from /dev/sde to /mnt/flash/sde.img
Starting positions: infile = 0 B, outfile = 0 B
Copy block size: 128 sectors Initial skip size: 128 sectors
Sector size: 512 Bytes
Max retries: 0
Direct: no Sparse: no Split: no Truncate: no
Press Ctrl-C to interrupt
rescued: 185150 MB, errsize: 0 B, current rate: 524 kB/s
ipos: 185150 MB, errors: 0, average rate: 585 kB/s
opos: 185150 MB, time since last successful read: 0 s
Actually, the capacity of the drive is 160Go, so something is wrong. As
you see, I canceled the ddrescue command at 185Go.
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
