headers
Paul L Daniels | 11 May 2013 06:59

Some guidance or advice please on migrating from 512 -> 4K drives

I've got a client drive that I'm recovering, VFAT, 2TB, 512Byte
sectors, but the drive I'm trying to migrate it to is a 4K sector AF
type unit; so when I did the usual;

   ddrescue -v -f /dev/sdd /dev/sde migrate.log

... even though it "worked" the data on destination drive wasn't
accessible directly.

Is there anything I can do other than to first make an image of the
failing drive, then do a slow "cp -av" from the image to the
destination?

Paul.

--

-- 
Computer Repairs for Charters towers - http://ctpc.biz
A.B.N. 19 500 721 806
Permalink | Reply | 2 comments |
headers
Andreas Boman | 7 May 2013 23:56
Picon

ddrescue very slow, and specific data to copy help.

Hi,

Sorry for writing the list not about a bug, I've been working on trying 
to solve this dilemma for several days now.

I've had ddrescue running for a few days trying to recover a disk that 
failed out of a linux md array.

The first pass ran with options -g -n (no -f version 1.11) ran very 
quickly (around 100 MB/s), seemed to recover around 600 GB or so before 
completing. I then started a second pass with options -d -r3. This was 
running around 32 MB/s and ran over night. In the morning it had 
recovered most of the disk, less some 7 GB, and was running at 512 B/s. 
This is the current status and has been for a few days, at this rate it 
will take over 160 days to finish the run. I've tried to run a few 
different options to speed it up.

I compiled version 1.17-rc3 from source to try to use --min-read-rate= 
to make it skip ahead, but that option seemed to do nothing (no 
skipping, no speedup).

This is what is currently running (time since last successful read has 
always been 0):

# ./ddrescue -f -d /dev/sdb /dev/sdf /root/rescue.log

GNU ddrescue 1.17-rc3
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:     1493 GB,  errsize:       0 B,  errors:       0
(Continue reading)

Permalink | Reply | 3 comments |
headers
Antonio Diaz Diaz | 2 May 2013 16:24
Picon

Version 1.17-rc3 of GNU ddrescue released

Version 1.17-rc3 of GNU ddrescue is ready for testing here
http://download.savannah.gnu.org/releases/ddrescue/ddrescue-1.17-rc3.tar.lz

The md5sum is:
1ec43497b8c79394737c44a9bca47951  ddrescue-1.17-rc3.tar.lz

Please, test it and report any bugs you find.

GNU ddrescue is a data recovery tool. It copies data from one file or 
block device (hard disc, cdrom, etc) to another, trying hard to rescue 
data in case of read errors.

GNU Ddrescuelog is a tool that manipulates ddrescue logfiles, shows 
logfile contents, converts logfiles to/from other formats, compares 
logfiles, tests rescue status, and can delete a logfile if the rescue is 
done.

The homepage is at http://www.gnu.org/software/ddrescue/ddrescue.html

Test versions of ddrescue are released in lzip format. In the improbable 
case that lzip is not packaged in your distro, you can download it from 
http://www.nongnu.org/lzip/lzip.html

Changes in this version:

   * The new option "-w, --ignore-write-errors", which makes fill mode 
ignore write errors, has been added. This is useful to avoid ddrescue 
exiting because of new errors developing while wiping the good sectors 
of a failing drive.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jonas | 1 May 2013 07:10

ddrescue --direct -b1

hi!
your manuals say:
sector size must be correctly set with the `--block-size' option for  --direct to work
i tried some things like :
ddrescue -d -b1 -c1 --retrim --try-again /dev/cciss/c0d9 /dev/cciss/c0d6 /gddrescuelog
and it seemed to get some additional bytes 
- but i dont understand: will wrong blocksize possibly result in corrupt data beeing written to the output file marked "+" in the log instead of "-"?

(currently using the debian stable package ddrescue 1.11 2009 but know newer ones too and really appreciate ddrescue)

Best regards, thanks!
Jonas
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@...
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
Permalink | Reply | 0 comments |
headers
Garegin Asatryan | 30 Apr 2013 05:59
Picon

Re: Bug-ddrescue Digest, Vol 87, Issue 15

badblocks has a problem with speed. this has been widely reported, but its developer- Theodore Tso, has constantly ignored pleas to fix it. as a result it literally takes two days to scan a 1tb hdd vs. ddrescue's couple of hours. 


On Mon, Apr 29, 2013 at 1:50 PM, <bug-ddrescue-request-mXXj517/zsQ@public.gmane.org> wrote:
Send Bug-ddrescue mailing list submissions to
        bug-ddrescue-1fE8/0vd1kM@public.gmane.orgg

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.gnu.org/mailman/listinfo/bug-ddrescue
or, via email, send a message with subject or body 'help' to
        bug-ddrescue-request-mXXj517/zsQ@public.gmane.org

You can reach the person managing the list at
        bug-ddrescue-owner-mXXj517/zsQ@public.gmane.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bug-ddrescue digest..."


Today's Topics:

   1. Re: Fill mode halting on write errors (Felix Ehlermann)
   2. Re: Fill mode halting on write errors (Niklas Holm)


----------------------------------------------------------------------

Message: 1
Date: Mon, 29 Apr 2013 18:19:53 +0200
From: Felix Ehlermann <fehlermann <at> gmx.net>
To: jadedcyborg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, bug-ddrescue-mXXj517/zsQ@public.gmane.org
Subject: Re: [Bug-ddrescue] Fill mode halting on write errors
Message-ID: <kxwgni5gl0728mvv6pwha9iw.1367252393059-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
Content-Type: text/plain; charset="utf-8"

Dear Niklas,

it seems you are tying to delete data on a damaged drive. From my understanding this is not the scope of ddrescue.
Is there a reason why you cant use tools like badblocks (using destructive read-write mode with a pattern of your preference)?

The way I use ddrescue I would be very unhappy if it silently ignored errors on my destination drive/image file, possibly having me end up with my rescued data on another faulty disk.

Kind Regards
Felix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/bug-ddrescue/attachments/20130429/c31f87de/attachment.html>

------------------------------

Message: 2
Date: Mon, 29 Apr 2013 19:50:21 +0200
From: Niklas Holm <jadedcyborg <at> gmail.com>
To: Felix Ehlermann <fehlermann <at> gmx.net>
Cc: bug-ddrescue <bug-ddrescue <at> gnu.org>
Subject: Re: [Bug-ddrescue] Fill mode halting on write errors
Message-ID:
        <CAPKCOXD0V2vZBk0XrACVaH3X3xoiVe0ym9BHw26kAZS2mGkirQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Content-Type: text/plain; charset="iso-8859-1"

Hi Felix!

Thank you for your answer.


2013/4/29 Felix Ehlermann <fehlermann-hi6Y0CQ0nG0@public.gmane.org>

> Dear Niklas,
>
> it seems you are tying to delete data on a damaged drive. From my
> understanding this is not the scope of ddrescue.
> Is there a reason why you cant use tools like badblocks (using destructive
> read-write mode with a pattern of your preference)?
>

Yes that is correct. The reason I don't use badblocks is because I didn't
know it can be used for that. Thank you for the tip! I'm pretty new at
this, I just recently found about ddrescue when trying to find a way to
rescue my bad drive. I do realize it's not the scope of ddrescue to wipe
drives, but my particular use case IS mentioned in the manual as one of the
possible usage areas for fill mode, so I think it should be properly
supported. It's seems to me like a quite easy fix too, just add a command
line argument to ignore write errors. Badblocks probably wasn't designed
for wiping drives originally either.


> The way I use ddrescue I would be very unhappy if it silently ignored
> errors on my destination drive/image file, possibly having me end up with
> my rescued data on another faulty disk.
>

I'm not asking you change the default behaviour.


>
> Kind Regards
> Felix
>


Best regards
Niklas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gnu.org/archive/html/bug-ddrescue/attachments/20130429/0da1afc0/attachment.html>

------------------------------

_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue-mXXj517/zsQ@public.gmane.org
https://lists.gnu.org/mailman/listinfo/bug-ddrescue


End of Bug-ddrescue Digest, Vol 87, Issue 15
********************************************

_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@...
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
Permalink | Reply | 1 comment |
headers
Niklas Holm | 29 Apr 2013 10:54
Picon

Fill mode halting on write errors

I'm finding ddrescue a bit lacking for my particular use case scenario, one which I find cannot be uncommon:

I'm working with some sensitive data on a crashed hard drive (piece of shit WD Green drive) and want to fill the drive with random data before sending it back to the manufacturer for warranty replacement. Preferably I want to do several passes to make sure data recovery is (sufficiently) impossible. I have already copied everything I can to a new hard drive and simply want to fill all writable sectors using with random data. I'm using the following command line:

ddrescue --verbose --force --fill=+ /dev/urandom /dev/sdb recovery.log

Where recovery.log is the log from my recovery operation. However, ddrescue constantly quits because of write errors:

ddrescue: write error: Input/output error

This is quite irritating because I constantly must go in to the log file and manually change the current position to make ddrescue skip the faulty sector (which obviously wasn't faulty when I did the original rescue). It would be so much simpler if I could give ddrescue a command-line option to skip ahead on write errors in fill mode, just as it does in recovery mode on read errors.

----
JayC
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@...
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
Permalink | Reply | 3 comments |
headers
Antoni Beksiak | 28 Apr 2013 11:08
Picon
Favicon

damaged hd onto a partition?

hello,
i have a damaged harddisk that doesn't even show a partition list (there were two: a fat32 one and an ntfs one).

can i use this method to resuce data to a partition? thanks in advance.

(taken from http://www.cgsecurity.org/wiki/Damaged_Hard_Disk)

The best method: Antonio Diaz's GNU 'ddrescue'

The best solution - both faster and more efficient - seems to be Antonio Diaz's 'ddrescue' (ddrescue)

# download ddrescue wget http://download.savannah.gnu.org/releases/ddrescue/ddrescue-1.8.tar.bz2 # extract the source code tar xjf ddrescue-1.8.tar.bz2 # compile ddrescue cd ddrescue-1.8 ./configure && make # first, grab most of the error-free areas in a hurry: ./ddrescue -n /dev/old_disk /dev/new_disk rescued.log # then try to recover as much of the dicy areas as possible: ./ddrescue -r 1 /dev/old_disk /dev/new_disk rescued.log to
Attachment (antoni_beksiak.vcf): text/x-vcard, 98 bytes
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@...
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
Permalink | Reply | 1 comment |
headers
John Summerfield | 27 Apr 2013 08:36
Picon

http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html


I have need of this program, and it's not going well. I have a seagate 
drive that is terminally ill. It seems to me its problem is on the 
circuit board rather than amongst the platters. It's in the fridge while 
I do some research.

First thing is that the above page needs revision. Recent drives have 4K 
sectors. See
http://www.seagate.com/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/
and other places. Hopefully, you can discover the native sector size 
programatically.

On this particular drive, things get a little bizarre. The kernel 
reported the drive capacity changed(!!) to zero, and ddrescue, going 
backwards at the time, concluded it had finished and left my image 
starting with (quite a) few gigabytes of zeros. I suspect the log isn't 
useful.

First, (after trying with dd), I went forwards, and when it stopped and 
I, not realising just how oddly the drive was behaving, restarted 
ddrescue in reverse. That destroyed the log file, it contained numbers 
way outside the drive's capacity.

The dodgy disk drive's capacity is 500 Gbytes, I don't have a lot of 
space for backing up images...

Since reverse gear doesn't seem to work with this drive, my next attempt 
will be to start again from the beginning. When it fails, the drive 
returns to the cool place for a while, and then I will simply rerun 
using the existing files.

I will, of course, override the blocksize. While I am looking at it, I 
suggest the default cluster-size be a function of available RAM. Using a 
64K buffer might have been reasonable on RHL 7.x or Debian Potato, but 
with 8 Gbytes of RAM I can spare a little more.

The version of ddrescue I tried is that shipped on the systemrescuecd 
that I downloaded withing the past week.

I am creating my own rescue image based on Fedora 18, there are aspects 
of the systemrescuecd which I don't like. Using a read-write image on a 
usb disk, I can customise whenever I like, including on the system I'm 
trying to rescue.

It's time I tried again.
--

-- 
John
Permalink | Reply | 0 comments |
headers
Seth Baker | 24 Apr 2013 16:23
Picon
Favicon

Re: Bug-ddrescue Digest, Vol 87, Issue 9

Sounds like the service area of the drive is damaged and the drive not starting all the way up in ready mode. The service area saves parameters of the drive, the firmware and service area is loaded on startup, except the service area is in a non addressable part of the drive. Many data recovery companies use equimpemnt like Deepspar (starts at about $10,000) to bypass the startup and start coping sectors. My estimate it is about $800 to $1500 to have a company recover data on a drive like this.

--- On Tue, 4/23/13, bug-ddrescue-request-mXXj517/zsQ@public.gmane.org <bug-ddrescue-request-mXXj517/zsQ@public.gmane.org> wrote:

From: bug-ddrescue-request-mXXj517/zsQ@public.gmane.org <bug-ddrescue-request-mXXj517/zsQ@public.gmane.org>
Subject: Bug-ddrescue Digest, Vol 87, Issue 9
To: bug-ddrescue-mXXj517/zsQ@public.gmane.org
Date: Tuesday, April 23, 2013, 7:14 PM

Send Bug-ddrescue mailing list submissions to
    bug-ddrescue-mXXj517/zsQ@public.gmane.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.gnu.org/mailman/listinfo/bug-ddrescue
or, via email, send a message with subject or body 'help' to
    bug-ddrescue-request-mXXj517/zsQ@public.gmane.org

You can reach the person managing the list at
    bug-ddrescue-owner-mXXj517/zsQ@public.gmane.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bug-ddrescue digest..."


Today's Topics:

   1.  Error size? (des1)
   2.  Error size? (des1)
   3.  Error Size? (des1)
   4.  Error Size? (des1)


----------------------------------------------------------------------

Message: 1
Date: Tue, 23 Apr 2013 17:38:52 -0700 (PDT)
From: des1 <yasgodfather-uAjRD0nVeow@public.gmane.org>
To: Bug-ddrescue-mXXj517/zsQ@public.gmane.org
Subject: [Bug-ddrescue]  Error size?
Message-ID: <35328181.post-WJuSqJV8a7jRv0WFA/ZhaQ@public.gmane.orgle.com>
Content-Type: text/plain; charset=us-ascii


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also this is to no avail. Is this hdd declared dead? Should i now
try the freezer trick? Any help would be appreciated.
--
View this message in context: http://old.nabble.com/Error-size--tp35328181p35328181.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.




------------------------------

Message: 2
Date: Tue, 23 Apr 2013 17:40:23 -0700 (PDT)
From: des1 <yasgodfather-uAjRD0nVeow@public.gmane.org>
To: Bug-ddrescue-mXXj517/zsQ@public.gmane.org
Subject: [Bug-ddrescue]  Error size?
Message-ID: <35328186.post-WJuSqJV8a7j4yp35w1jErA@public.gmane.orgom>
Content-Type: text/plain; charset=us-ascii


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also this is to no avail. Is this hdd declared dead? Should i now
try the freezer trick? Any help would be appreciated.
--
View this message in context: http://old.nabble.com/Error-size--tp35328186p35328186.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.




------------------------------

Message: 3
Date: Tue, 23 Apr 2013 17:42:56 -0700 (PDT)
From: des1 <yasgodfather-uAjRD0nVeow@public.gmane.org>
To: Bug-ddrescue-mXXj517/zsQ@public.gmane.org
Subject: [Bug-ddrescue]  Error Size?
Message-ID: <35328193.post <at> talk.nabble.com>
Content-Type: text/plain; charset=us-ascii


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also is to no avail. Is this hdd declared dead? Should i now try
the freezer trick? Any help would be appreciated.
--
View this message in context: http://old.nabble.com/Error-Size--tp35328193p35328193.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.




------------------------------

Message: 4
Date: Tue, 23 Apr 2013 17:45:33 -0700 (PDT)
From: des1 <yasgodfather-uAjRD0nVeow@public.gmane.org>
To: Bug-ddrescue-mXXj517/zsQ@public.gmane.org
Subject: [Bug-ddrescue]  Error Size?
Message-ID: <35328201.post <at> talk.nabble.com>
Content-Type: text/plain; charset=us-ascii


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also is to no avail. Is this hdd declared dead? Should i now try
the freezer trick? Any help would be appreciated.
--
View this message in context: http://old.nabble.com/Error-Size--tp35328201p35328201.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.




------------------------------

_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue-mXXj517/zsQ@public.gmane.org
https://lists.gnu.org/mailman/listinfo/bug-ddrescue


End of Bug-ddrescue Digest, Vol 87, Issue 9
*******************************************
_______________________________________________
Bug-ddrescue mailing list
Bug-ddrescue@...
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
Permalink | Reply | 1 comment |
headers
des1 | 24 Apr 2013 03:14
Picon
Favicon
Gravatar

Error size


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also this is to no avail. Is this hdd declared dead? Should i now
try the freezer trick? Any help would be appreciated.
--

-- 
View this message in context: http://old.nabble.com/Error-size-tp35328276p35328276.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
des1 | 24 Apr 2013 02:54
Picon
Favicon
Gravatar

Error Size?


I have a WD 2tb hdd which recently failed, it makes a clicking noise but
still spins. It is found in the bios, device manager and in linux but I cant
mount the disk and it gives 49 currently unreadable sectors. I tried dd
rescue onto my 3tb ntfs hdd with the following command  ddrescue -f -d -r3
/dev/xxx /dev/yyy /path/to/logfile it starts up but nothing transfers it
gets 1 error and this error goes up to a size of 2tb?? then tries Trimming
but this also this is to no avail. Is this hdd declared dead? Should i now
try the freezer trick? Any help would be appreciated.
--

-- 
View this message in context: http://old.nabble.com/Error-Size--tp35328226p35328226.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |

Gmane