I wanted the errors to go down, which is why I tried imaging again. But perhaps they differ from mechanical disks in that if you can't read a bad block, most likely you won't be able to, no matter how many times you retry. I'm assuming data recovery services have vastly superior software and hardware tools that could read bad blocks from an SSD, however. This SSD drive has been slaved quite a few times to analyze and also attempt decryption. I've cloned with it Clonezilla (which claims it's physically damaged), and then I imaged it twice with GNU ddrescue with one parameter value increased and the image results are exactly the same. One would think that with all that this drive has been through, if it was failing, it would take a long time to read from/write to and the number of errors would increase. My goal is to rebuild my user files, so RAW files are fine if I can find them.Maybe I'm just getting lucky and it is physically damaged. The rescue software got me my file directories and files with the right size, but a portion were corrupted, so I was trying to do a better attempt at cloning to work off and this time copy the whole disk. DMG file of the problematic partition using the built in Disk Utility. The disk has 2 partitions, 1 is intact and accessible still (but DDRescue failed with that one too). It's a USB drive, and one of the partitions wasn't showing in the finder, and now I don't have access to it at all. The app is supposed to re-scan bad sectors, but it didn't spot any, despite there obviously being problems. The drive I captured to is also now greyed out. So, IOW with some file systems or with certain type of damage RAW recovery is expected, in others it's not.ĭDRescue is supposed to create a mountable file from the data it clones, drive to drive. or file system is quite severely damaged. What's the file system of the partition that refused to mount? And what happened to it? If all these quite good tools are unable to reconstruct a file system then either the file system wipes meta data upon deletion, formatting etc. Sure you imaged to file then? I never use ddrescue but if destination was drive rather than image file then story makes sense. Is the DMDE sector by sector function worth trying? Is there a way to remedy this situation with the DDRescue_GUI scan? But the DDRescue scan only did 1 pass and didn't show any issues. The newly scanned info is in worse shape because that at least still has file structures on one partition appearing in the finder, and doesn't show the same errors in the recovery apps that recognize the drive and partition name. I tried to rescue the contents of the DDRescue_GUI clone using DMDE and (demos of) R-Tool, and UFS, but it's showing errors, no file structure, and doesn't appear to have preserved the current state of the troubled drive.and now I have a new troubled drive showing new errors in those recovery programs. I must have done something wrong, since it wouldn't mount. I tried to clone a drive (it has a partition which doesn't mount) using DDRescue_GUI and after the scan completed (no bad sectors, didn't need to make a second pass, no indication of problems) it wouldn't create the image file, and now the destination drive no longer mounts at all.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |