You are not logged in.

#1 2015-08-23 09:17:28

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

dd_rescue

Im ran dd rescue, didnt realize i needed to add the log manually,

cd dd/1
dd_rescue /dev/sda3 ./sda3.img 

then after it went for about 14 hours, i had to stop it, when i resumed it, i did mroe research, found that you need to add the log manually, so i added the log, and worked on the same image in reverse, and laid it onto a new image, that way i dont totally lose what data i had so far

dd_rescue /dev/sda3 ./sda3.img -l ./sda3.log -r

then i stopped it, it didnt restart
so i started all over to see what the hecks going on,
switched directories entirely,

cd dd/2
dd_rescue /dev/sda3 ./sda3.img -l ./sda3.log

then i stopped it after about 4 hours of good progess cause i needed to reboot, then i went right back to that directory with my new progress

dd_rescue /dev/sda3 ./sda3.img -l ./sda3.log

and again it didnt resume, then i tried it in reverse for kicks on this one

dd_rescue /dev/sda3 ./sda3.img -l ./sda3.log -r

stopped and restarted

dd_rescue /dev/sda3 ./sda3.img -l ./sda3.log -r

still each time, no matter what, it starts at 0& complete, and appears to be also styarting off at the same sector, even after i let it move to , and start on, the next sector before i stop it.  when i restart it, it acts like it never got to that next sector.

wtf am i missing?  got to be something stoopid!

what documentation i can find is here http://www.garloff.de/kurt/linux/ddrescue/ and here http://www.garloff.de/kurt/linux/ddresc … .dd_rescue, i have looked for keywords "resume", and others, including in the man dd_rescue.

Last edited by wolfdogg (2015-08-23 09:21:43)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

#2 2015-08-23 12:08:51

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 30,543
Website

Re: dd_rescue

How are you stopping it?  How are you resuming?  What makes you think dd_rescue is capable of being stopped and resumed?

It seems no suprise to me that if you run the same command a second time it will perform the same action.


"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman

Offline

#3 2015-08-23 14:26:52

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,435

Re: dd_rescue

From a quick glance, you probably want ddrescue (note the missing underscore) which is an entirely different program and it does advertise being able to pause/resume

Last edited by V1del (2015-08-23 14:36:47)

Offline

#4 2015-08-24 04:23:05

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

Re: dd_rescue

right, i know this very well, its just that i thought dd_rescue does this too? Yeah, its just a blatant stop ctrl-c, and start again after reboot. In the end, maybe the logs just have it skip over the bad sector checks again, but im thinking the data write part happens each time from the beginning.  Now this time i ran out of space on the destination drive.  This will be the 3rd full run, and 6th total run on this drive.  Its a GOOD THING this data wasn't totally important cause its magnetic surface is going to be strewn about by the time i get done with this drive.  I think i might switch to ddrescue first before doing anything. 

get this, smartmontools smartctl reports a 24 hours imminent failure, it literally says "LESS THAN 24 HOURS", and "Remove Data immediately"  Love that program!


EDIT, im running ddrescue this time around, i just cant take the risk of that happening again.  If anybody knows whats going on with dd_rescue resume, if it uses the logs, otherwise what are they for, and how to get it to resume, or what does it resume.  I think, after using it, it doesnt seem to resume the data, maybe it does, the file doesnt grow after restarting it, but it seems to have to take a new run the data it seems.

Last edited by wolfdogg (2015-08-24 04:41:34)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

#5 2015-08-24 07:47:01

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,435

Re: dd_rescue

From what I gather dd_rescue's logfile is just that, a logfile for you to interpret and see where it had to skip bad sectors (and adjust the command accordingly yourself so that you can make back/forward reads up to the sector)

EDIT: Unless he forgot to update http://www.garloff.de/kurt/linux/ddrescue/#Roadmap 5th bullet point pretty much confirms that it can't do this by itself and refers to ddr_help which itself recommends ddrescue

Last edited by V1del (2015-08-24 08:03:51)

Offline

#6 2015-08-28 21:53:53

wolfdogg
Member
From: Portland, OR, USA
Registered: 2011-05-21
Posts: 545

Re: dd_rescue

buahhh hahhh.  Good find, on the 5th bullet!   I think that sums it up, shit do we have to dig or what??  NO probs ther, and thanks for the kind help.  I learned, dont even bother with dd_rescue.  I had a GREAT exerience last time a couple years ago, now im SURE it was ddrescue, this time around i chose dd_rescue and thought i would have same great experience.  It appears dd_rescue should just be deprecated out of teh AUR.  is there any use for it when we have ddrescue wtih its resume, fill mode, and other sweet features?

Last edited by wolfdogg (2015-08-28 21:54:57)


Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Offline

Board footer

Powered by FluxBB