reallymine
reallymine copied to clipboard
andlabs
troubleshooting creating an image file of drive smaller than actual size
So I've managed to successfully execute the program but I've run into another problem. The image tries to duplicate the exact size of the volume.
I have a 1.5TB drive and I know the data on there is significantly less than the full drive, say 70GB. I also noted there is a command "disk-size int" within the program. Is there a way that I can claim that the drive is 80 GB and try to create a decrypted image file that way? How would I write that out?
Would this also work if I know that there is roughly that much space on the drive? or will some of my files be damaged?
Well. Reallymine just does decryption on a per sector base. I usually dump a 1.5tb to a 2tb drive. In your case you might get lucky but not 100% sure you might have file damage. Especially fragmented files. The drive image might not mount properly if so. Check with maddoctor he has methods of mounting wdc encrypted drives.
On Dec 16, 2017 8:55 AM, "J188" [email protected] wrote:
So I've managed to successfully execute the program but I've run into another problem. The image tries to duplicate the exact size of the volume.
I have a 1.5TB drive and I know the data on there is significantly less than the full drive, say 80GB. I also noted there is a command "disk-size int" within the program. Is there a way that I can claim that the drive is 80 GB and try to create a decrypted image file that way? How would I write that out?
Would this also work if I know that there is roughly that much space on the drive? or will some of my files be damaged?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/andlabs/reallymine/issues/57, or mute the thread https://github.com/notifications/unsubscribe-auth/AQE6xVhyU50Fi2oWSW_fx106vzZ6dO09ks5tA9nUgaJpZM4REW14 .
