Hi Elmar, is it unusual for hfsprescue to take several days to run step 1 on a ~250GB hfs+ filesystem on a damaged ssd?
I am trying to recover files on a damaged ssd in an 11,1 imac that won't boot. I put your latest precompiled hfsprescue tar on a bootable osx el capitan install image I had sitting around on an sd card. I have booted into the osx version on the sd card, and have been executing hfsprescue from terminal. It has been running for about a day and has only made about 1% progress. I am tailing the step 1 log file in another window so I can watch which sector, block, offset is currently being processed, and it's been on the same 4k block for several hours now.
I did notice that, at 0.04% progress in step 1, it took hours to process the block/offset it was at. I am assuming that this is normal for certain damaged disks that encounter i/o errors (and associated latencies), but I just wanted to confirm with you that this behavior is indeed expected.
Also I wanted to ask you whether there are other tools that can help me narrow the scope of my recovery process.
* I did see that hfsprescue has the option to recover individual files. Is it required for step 1 to complete before this can be done?
* Is there a way to time-limit each read operation that occurs in step 1?
Thank you for sharing this software and service! Much appreciated!