On 11/07/10 10:31, Volker Kuhlmann wrote:
On Sat 10 Jul 2010 12:37:22 NZST +1200, Daniel Hill wrote:
Sounds to me like the disk is dead because it's got read error,
do you reckon the USB-SATA adapter will be fine I couldn't use a direct
connection to my computer because I didn't have a spare SATA cable, so I
had to use the USB-SATA adapter once we fixed the SATA plug on it
not
because the sata plug broke. No amount of data damage you can do with a
broken plug would affect read performance with dd once you connect it up
properly.
You don't even need ddrescue. If you haven't yet done so, do
that now and start again.
I Used ddrescue because it seems better for the job of data recovery, dd
would just error about read errors, and I found ddrescue while looking
for a way of skipping read errors
If the disk had read errors (average 1MB/s sounds rather like it) then
technically you run rescue operations on a copy of a ddrescue copy. If
you don't have the space you get only 2 goes (one on the first copy, one
on the bad disk). Buy another disk if it's important.
OK I've fixed the Image of the disk with testdisk, seems to work OK,
able to mount it using an offset loopback device
and play music off of it, I'll recommend another disk too my friend
(it's his)
You can find out if the disk has surface errors by running the smartctl
command of the smartmontools package. Note that if you connect the disk
through anything involving USB then you need an adapter which is
designed properly, and a rather recent version of smartmontools.
Volker
I tried smartctl and it seemed to pass with no errors :/ maybe I'm using
the wrong arguments? (sorry I can't remember which ones I used)
thanks for the advice
Daniel
