bug-ddrescue
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-ddrescue] ddrescue - disk 2 disk (ntfs)


From: Tom
Subject: Re: [Bug-ddrescue] ddrescue - disk 2 disk (ntfs)
Date: Wed, 15 Jul 2009 09:41:45 +1000

Your syntax does not seem correct, I think this command would image sdb to /storage and save a log file to test.bin you it may be a transcription typo, and you could try copying the good areas first.

sudo ddrescue -v /dev/sdb /storage test.bin testlog


suggestion:

copy the error free areas first

    ddrescue -n /dev/sdb /storage/test.bin testlog

attempt to recover any bad sectors

    ddrescue -r 1 /dev/sdb /storage/test.bin testlog





On Wed, Jul 15, 2009 at 5:28 AM, Al Grant <bigal.nz@gmail.com> wrote:

Hi,
Well the plot thickens I have given up trying to clone the drives but are
now trying simply to create a bin file of the bad drive.

This is what happens so far:

1. Initally I was using a USB-SATA bridge, and mounting a 250Gb NTFS drive,
and trying to image the 160Gb PATA drive. The PATA drive was not mounted.
The NTFS drive is mounted to /storage.

The problem with this was that it was very slow and every day or so it would
stop or the computer would freeze. I estimated it was going to take about 7
days doing 25Gb/day. I was using this command:

sudo ddrescue -v /dev/sdb /storage test.bin testlog

2. So I went out and brought a SATA/PATA PCI card to make things easier.

Now the bad disk is plugged into the motherboard PATA controller and the
target SATA drive is on its own PCI card controller.

Again I was mounting the good drive to /storage and issuing a similar
command to above. Heres whats strange:

(a) I can see the image file created so far. Its 3Gb. If I restart the
rescue, with the same parameters, so it should resume the 3Gb doesnt get any
bigger, even tho the output window of ddrescue tells me its rescued 2200Mb.
Now I know i am writing to the 3Gb file because the time stamp is changing.

What is also weird is how small the log file is, its only about 30 lines - I
assume for 2200Gb it should be much bigger???

And whats more I left this running overnight (I was connected via a remote
desktop session) - when I went to check on it in the morning the remote
session was dead and logging into the computer when infront of it started a
new session, so I am not really sure what was happening, if anything, in the
old session.

So....I think I am geting closer but not sure if the crashing is the
computer, the remote session or ddrescue.

Any ideas?

Anyone here on skype able help via IM?

Also anyone know how to reconnect to a dead remote session without starting
a new one?

THanks in advance,
-Al


MacXperte wrote:
>
> Al Grant <bigal.nz@gmail.com> schreibt am 11.7.2009 10:07 Uhr:
>
>> When I try "sudo ddrescue -v /dev/sdb/ /dev/sdc logfile"
>>
>> I get "no space left on device"
>>
>> I asusme its something to do with the new disk, maybe having to
>> copy/mount
>> in raw? please help.
>
> Maybe the error is not about writing to sdc but about writing the logfile.
>
> What is your current working directory (pwd)?
> What happens if you try: echo test >> logfile
>
> Florian
>
>
>
> _______________________________________________
> Bug-ddrescue mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-ddrescue
>
>

--
View this message in context: http://www.nabble.com/ddrescue---disk-2-disk-%28ntfs%29-tp24438174p24486211.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.



_______________________________________________


reply via email to

[Prev in Thread] Current Thread [Next in Thread]