reallymine
reallymine copied to clipboard
andlabs
Recovery is Stuck
I'm trying to run reallymine from a decrypted 2TB drive onto a fresh 3TB drive. I started it two days ago and it was making good progress, but it looks like it got stuck sometime last night. According to ls -lh on the mounted drive, the image file is stuck at 414GB and hasn't been growing for 12+ hours. Did it encounter a bad sector or is it done? I'm assuming it's still running since the command (in another terminal window) is still running. If it's errored out, should I stop it and try something else (such as ddrescue of the drive, then running reallymine on that instead?).
Thank you so much for all of your work on this project, I really appreciate it as do many others!
That's very strange; it shouldn't have stalled like that. Maybe there is a bad sector and it just hasn't failed outright yet? You can confirm this via badblocks or ddrescue; if you go with the latter, you can just run reallymine on the generated image.
Thanks! Would I be safe stopping reallymine at this point then? I'm actually going to order a new bridge and try to recover the data that way. But if that doesn't work, would it be best to just run ddrescue on the hard drive, then run reallymine on the image generated from ddrescue instead?
It's always better to work with a copy, especially if the original has problems.
@andlabs I'm having some trouble getting reallymine to stop (I've left it running this whole time). I've tried Ctrl+C, Ctrl+Z, & Escape, but the command is still running. Would I be safe exiting Terminal or re-starting the computer at this point? Just don't want to mess anything up. Thanks!