Using Testdisk on a ddrescue'd drive that has been inserted in Windows
Posted: 03 Apr 2023, 20:32
Good day or night, depending on your time zone, also I'm sorry if I made a mistake and posted this in the wrong board,
I've been having a lot of trouble figuring out how to rescue an old Hard Disk that took a bit of a fall a few years back. My question is in the title of the post, but to summarize the events that transpired (link to the original discussion in https://stackoverflow.com/questions/758 ... -raw-data/) :
I've used gddrescue to save data from a defective hard drive onto a newer one of the same size (both are 2TBs Toshiba hard disks). More specifically, I used the command to copy the entire thing. It took 5 days due to the only laptop I'm currently able to use being really outdated, with fans keeping both disks and laptop cool. As it was approaching its completion, the BADDISK started emitting uncomfortably loud clicking noise during the parsing for bad sectors phase, which prompted me to stop. As I didn't quite understand the state it would be in once it was done copying stuff, I inserted GOODDISK (pardon the use of these words, but I wasn't able to communicate it properly last time) on a Windows 7 partition to check if it worked right and after noticing that files were still missing I securely unplugged.
At this point I tried using Testdisk on GOODDISK to see if I could recover anything from it, the only information shown though were the same kind of files that I could see on the fileview on both Windows and Linux Mint. As I notified a kind soul that was helping me, I was told that I committed a mistake and should have completed the rescue operation. I tried running it again, this time as and it completed, though Testdisk still only sees a few files and not the complete thiing (the relevant information should be around 500GBs/2TBs, but I can only access about 25GBs).
Now, what I'd like to know is:
1) How much did I screw up?
2) Testdisk also lets me perform a deeper search, but it also takes quite some time (again, kind of forced due to low resources). Should I bother attempting it on GOODDISK before doing anything else? Will it return a list of candidates of possible files to be saved onto yet another drive?
3) If not, then are there any other steps that I should take on GOODDISK to at least attempt a recovery on the files?
Infinite thanks for your patience and for making tools such as these. Again, sorry if I didn't use proper etiquette.
I've been having a lot of trouble figuring out how to rescue an old Hard Disk that took a bit of a fall a few years back. My question is in the title of the post, but to summarize the events that transpired (link to the original discussion in https://stackoverflow.com/questions/758 ... -raw-data/) :
I've used gddrescue to save data from a defective hard drive onto a newer one of the same size (both are 2TBs Toshiba hard disks). More specifically, I used the command
Code: Select all
sudo ddrescue -f BADDISK GOODDISK logfile.logAt this point I tried using Testdisk on GOODDISK to see if I could recover anything from it, the only information shown though were the same kind of files that I could see on the fileview on both Windows and Linux Mint. As I notified a kind soul that was helping me, I was told that I committed a mistake and should have completed the rescue operation. I tried running it again, this time as
Code: Select all
sudo ddrescue -f -C BADDISK GOODDISK logfile.logNow, what I'd like to know is:
1) How much did I screw up?
2) Testdisk also lets me perform a deeper search, but it also takes quite some time (again, kind of forced due to low resources). Should I bother attempting it on GOODDISK before doing anything else? Will it return a list of candidates of possible files to be saved onto yet another drive?
3) If not, then are there any other steps that I should take on GOODDISK to at least attempt a recovery on the files?
Infinite thanks for your patience and for making tools such as these. Again, sorry if I didn't use proper etiquette.