![]() Later you can work with the ddrescue log/mapfile to try to be more aggressive about bad blocks if you want but at least you'll know most of your data were saved. In a recovery scenario, getting an (possibly partial) image ASAP is best practice - this is what ddrescue does, skipping bad/slow blocks on the first pass to read as much as possible before getting aggressive. If you have a fully working disk you need to image, you can use partimage or ntfsclone to avoid copying empty blocks if you want. Identifying the bad files can be tricky, but there are ways to do it from the block list, at least. As far as 3: in most cases you would rather have 0s written to bad blocks in the file, than for the copy to completely fail, at least some data may be recoverable. Most tools assume the disk is good and will have this problem, which is why you need ddrescue. You might get lucky and the bad blocks don't affect any files/metadata and it copies cleanly, but if the bad blocks affect the filesystem at all, you will likely have a hard time getting the process to proceed past the read errors. You'll get stuck in retry loops with long timeouts in the OS, putting stress on the drive and bad sectors, and sometimes this will cause bus resets and other nastiness. If you have a failing disk, this will almost certainly not work well for you, despite not even creating an image as was requested. btw my current disk recovery/backup tool is AOMEI Backupper, i also keep the other recovery tools install files like EaseUS et al in case AOMEI cant do the job. ![]() or have you read this? searching the internet may give you some light. if you try to recover some important softwares, try to save as much as you can esp Windows registry and probably some files installed in Windows or System32 folders? or maybe try to create "disk image" as intermediary process instead of directly "clone" attempt may work? (skip CRC, bad sectors or any other errors) or else maybe try the "surface to surface match" cloning technique if available. the CRC that causes indefinite halting maybe on the XP system files that are recoverable by reinstalling fresh XP. can you try copying on file by file level first? say using Windows Explorer to another disk, most important files first. Perhaps one less elegant solution is a solution, but ymmv. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |