Re: [Bug-ddrescue] ddrescue strange(?) behavour

[bakegoodz]

sgd wrote:
> 
> Hi, 
> Working on my phd, because of lack of space, stupidly was not making
> regular backups.
> hdd dies: system was working over night, the next day won't write, says
> "read-only file system".
> did reboot, won't see the partitions of the disk anymore (The disk is
> present on /dev/)
> 
> tried tu rescue with ddrescue (1.15)...
> 
> 1st Run:
> /usr/local/bin/ddrescue -n /dev/sdb /mnt/tmp/temp/imagefile
> /mnt/tmp/temp/image.logfile 
> 
> Press Ctrl-C to interrupt
> rescued:         0 B,  errsize:       0 B,  current rate:        0 B/s
>    ipos:         0 B,   errors:       0,    average rate:        0 B/s
>    opos:         0 B,     time from last successful read:       1 s
> Finished                   
> 
> -----------------------
> Second Run:
> /usr/local/bin/ddrescue -d -r3 /dev/sdb /mnt/tmp/temp/imagefile
> /mnt/tmp/temp/image.logfile 
> 
> 
> Press Ctrl-C to interrupt
> rescued:         0 B,  errsize:       0 B,  current rate:        0 B/s
>    ipos:         0 B,   errors:       0,    average rate:        0 B/s
>    opos:         0 B,     time from last successful read:       1 s
> Finished                   
> 
> ------------------------
> Fourth run:
> 
> /usr/local/bin/ddrescue -i1 -n /dev/sdb /mnt/tmp/temp/imagefile
> /mnt/tmp/temp/image.logfile 
> 
> 
> Press Ctrl-C to interrupt
> Initial status (read from logfile)
> rescued:         0 B,  errsize:   9223 PB,  errors:       1
> Current status
> rescued:         0 B,  errsize:   9223 PB,  current rate:        0 B/s
>    ipos:         0 B,   errors:       1,    average rate:        0 B/s
>    opos:         0 B,     time from last successful read:       0 s
> Finished
> 
> #Petabytes!!!??
> 
> -------------------------
> 
> Fifth run:
> 
> /usr/local/bin/ddrescue -i1 -d -r3  /dev/sdb /mnt/tmp/temp/imagefile
> /mnt/tmp/temp/image.logfile 
> 
> 
> Press Ctrl-C to interrupt
> Initial status (read from logfile)
> rescued:         0 B,  errsize:   9223 PB,  errors:       1
> Current status
> rescued:         0 B,  errsize:   9223 PB,  current rate:        0 B/s
>    ipos:     1152 PB,   errors:       1,    average rate:        0 B/s
>    opos:     1152 PB,     time from last successful read:      16 s
> ^Clitting failed blocks...
> Interrupted by user
> 
> --------------------------------------------
> 
> Sixth run: 
> 
> /usr/local/bin/ddrescue -i1 -s146815733760 -d -r3  /dev/sdb
> /mnt/tmp/temp/imagefile /mnt/tmp/temp/image.logfile 
> 
> 
> Press Ctrl-C to interrupt
> Initial status (read from logfile)
> rescued:         0 B,  errsize:    146 GB,  errors:       1
> Current status
> rescued:         0 B,  errsize:    146 GB,  current rate:        0 B/s
>    ipos:    98768 MB,   errors:       1,    average rate:        0 B/s
>    opos:    98768 MB,     time from last successful read:      21 s
> Splitting failed blocks...
> Interrupted by user.
> 
> #ipos and opos keeps cycling from several MB to thousand of MB...
> 
> 
> The disk:  (SAS) SCSI SEAGATE, Model: ST3146854SS, 136.7 GB
> (146,815,733,760 bytes). 
> 
> What I am doing wrong? what could be done? please help!!!!
> 
> Guillermo.
> 

You drive looks pretty bad, I see no problems with your syntax.
This is what I would do in the following order:

1. Try a -r 0 for no retrys and a -R for reverse copy (needs version >=
1.14) and keep the -n (no split) 
option too.
2. Sometimes freezing it for a couple hours helps, most the time not
3. Pay $$$$ to professional recovery lab
4. Pray to a higher power 
5. Mourn for the lost of your data
-- 
View this message in context: 
http://old.nabble.com/ddrescue-strange%28-%29-behavour-tp33400471p33403790.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.