

Do NOT write anything to this drive, that would completely defeat the purpose of data recovery.Īlso I'm thinking whether it would be worth to use ddrescue, but I don't have `/dev/disk5sxxx` and only `/dev/disk5` so I'm not sure whether it would work - never done that before.Ĭloning is a good place to start in most cases.

With testdisk, I can also see the partition, but I got to a point where the next step would be to "write" and I got uncomfortable, since I'm not entirely sure it that's what I should be doing.įorget TestDisk exists. If it’s failing, you should not be scanning it directly for files.

I ran dmde and it can see the partition and I can recover files, but I couldn't find a way to recover it all, only in a file-by-file basis (and not folder for example), I still need to understand the software more to make it work I guess.
