> I'm trying to rescue to is an external USB drive. The "problem" drive is connected to my computer internally and the drive As expected, there are a TON of errors reading the "problem" > I used Alt-F2 to open a new console and was able to look at the kernel > Cc: Subject: Re: Question about reported errorsize > mean this process is most likely going to fail? Is it Question:? does the fact that 500GB was reported as > going to try to split the 500GB of "errors" reported in > 51MB of data and is in the "splitting" phase now. > ddrescue has reported only ONE error and the errorsize is > I'm hoping to move the data to a new hard drive so it can > hard drive with two NTFS partitions on it.? The hard > To: Received: Tuesday, December 6, 2011, 12:26 PM Using -D or -d switches can also slow things down and regulate speed in a useful way. I find some drives tend to faint easily at high speeds, which makes the slower USB speeds an asset in these cases. I regularly have to physically unplug and plug back in the USB connector to a drive that has dropped out like that. That way, you can stop and resume the recover. Would run Gnu ddrescue in the same way, but I would use a log. > That being said, I like those kinds of interfaces because you can hotplug the drive and potentially bring it back online without power cycling it. This happens sometimes when the kernel can see the drive controller even if there is no drive attached, as with some USB-SATA connections. In this case, I would wonder if the drive went offline but the kernel didn't notice. > and that shows me what the kernel sees - I pay attention to devices dropping offline. In another console, I usually run something like: > First off, I like to see what's going on while I read a faulty drive. > Content-Type: text/plain charset=iso-8859-1 ![]() > Subject: Re: Question about reported errorsize > Antonio Diaz, GNU ddrescue author and maintainer. > * The default block size for ddrescuelog has been changed to 512, > * The "split or skip" algorithm of the split pass has been improved. > * Non-tried blocks are now read aligned to cluster-size sectors. > * Ddrescue now verifies that infile, outfile and logfile are all > * The new option "-x, -extend-outfile" has been added. The new option "-I, -verify-input-size" has been added. > yet distribute the lzip program, you can download it from > This version is also available in lzip format. > logfiles, tests rescue status, and can delete a logfile if the rescue > logfile contents, converts logfiles to/from other formats, compares > GNU Ddrescuelog is a tool that manipulates ddrescue logfiles, shows > block device (hard disc, cdrom, etc) to another, trying hard to rescue > Please, test it and report any bugs you find. > Version 1.15-rc1 of GNU ddrescue is ready for testing here > "trying hard to rescue data in case of read errors.\n" > std::printf( "Copies data from one file or block device to another,\n" > + std::printf( "%s %s - Data recovery tool.\n", Program_name, > - std::printf( "%s - Data recovery tool.\n", Program_name ) > void show_help( const int cluster, const int hardbs ) throw() > version of ddrescue being run is included in the output. This way, when someone runs "ddrescue -h", the > I have worked up a small patch to add the ddrescue version number to the > To: Subject: Re: Version 1.15-rc1 of GNU ddrescue released > I believe I'm running ddrescue 1.14, but I'm not sure. > the time to go through the "splitting" phase? > mean this process is most likely going to fail? Is it worth spending ![]() > My question: does the fact that 500GB was reported as the errorsize > going to try to split the 500GB of "errors" reported in "errorsize". Reported only ONE error and the errorsize is 500GB. > I'm hoping to move the data to a new hard drive so it can be saved. > hard drive with two NTFS partitions on it. > I'm running ddrescue from a Trinity Rescue CD (3.4-bld-372) on a 500GB > Content-Type: text/plain charset=ISO-8859-1 > To: Subject: Question about reported errorsize Re: Version 1.15-rc1 of GNU ddrescue released (Antonio Diaz Diaz) Request for example of rescuing a dvd data disk (Bob) Re: Question about reported errorsize (Tom Williams) Re: Question about reported errorsize (andrew zajac) Re: Version 1.15-rc1 of GNU ddrescue released (Tom Williams) Question about reported errorsize (Tom Williams) ![]() > than "Re: Contents of Bug-ddrescue digest." > When replying, please edit your Subject line so it is more specific > You can reach the person managing the list at > or, via email, send a message with subject or body 'help' to ![]() > To subscribe or unsubscribe via the World Wide Web, visit > Send Bug-ddrescue mailing list submissions to Some kind of noise? Was the HDD detected by BIOS?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |