Thanks for the advice. I canceled it and got most of the data I needed so I think I'm good!
Thanks! Peace... Tom On 12/27/2010 01:45 PM, andrew zajac wrote: > Hi Tom. > > You used a log file, so yes, you can stop the process and resume > later. Just issue the same command (you can use different switches, > just keep the same input,output and log file parameters). > > One caveat is that you will need to either mount the filesystem(s) on > the image as read-only or copy them and then work on the copy. if you > make any changes to the data on the image, continuing the recovery > procedure may inflict mode data loss rather than than get more data back. > > Regards, > > Andrew Zajac > > --- On *Mon, 12/27/10, Tom Williams /<[email protected]>/* wrote: > > > From: Tom Williams <[email protected]> > Subject: [Bug-ddrescue] Question about "splitting failed blocks" > processing > To: [email protected] > Received: Monday, December 27, 2010, 2:22 PM > > Hi! I'm running ddrescue 1.11 on Ubuntu 10.10 Linux to recover data > from a dying 160GB hard drive. > > The process has been running non-stop for about 65 hours now and has > been in the "Splitting failed blocks" phase for about the past 12 hours > or so. I have no idea how long it will take for the process to finish > but I'm wondering if I can safely cancel it to access the data that has > already been recovered. Is this possible? I'm recovering the data from > the bad hard drive to a good hard drive which is connected to the system > using a USB external hard drive enclosure. > > This is sample status output: > > t...@deathstar:~$ !507 > sudo ddrescue /dev/sdc /dev/sdh nawanna-rescue.log > > > Press Ctrl-C to interrupt > Initial status (read from logfile) > rescued: 0 B, errsize: 0 B, errors: 0 > Current status > rescued: 159820 MB, errsize: 221 MB, current rate: 0 B/s > rescued: 159828 MB, errsize: 213 MB, current rate: 0 B/s > ipos: 156842 MB, errors: 971, average rate: 723 kB/s > opos: 156842 MB, time from last successful read: 9.9 m > Splitting failed blocks... > > Given how close to 160GB the process seems to be, I don't want to cancel > it but it's been "this close" for the past 12 hours, at least. > > Can I safely cancel the process or should I just let it run? > > Thanks! > > Peace... > > Tom > > > -----Inline Attachment Follows----- > > _______________________________________________ > Bug-ddrescue mailing list > [email protected] </mc/[email protected]> > http://lists.gnu.org/mailman/listinfo/bug-ddrescue > >
_______________________________________________ Bug-ddrescue mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-ddrescue
