Ddrescue gui mac
This process took another 3-hours, and reduced the size of the errors on the image to about 200MB. The next step ddrescue goes through is a reverse pass, where it re-reads the bad sectors, and trims out the still good data. Once the initial pass was complete, about 370MB of bad sectors were found on the drive. The last 150 gigs took about 3 hours to get through. The first 350gigs took roughly an hour and 20 minutes. Yay.Ībout 350gigs into the read, ddrescue started to run into problems on the drive. So now, my estimated time was roughly 2 hours. Suddenly the ddrescue speed jumped up to 70MB/sec. Some google searching lead me to a great tool which allows you to suppress the mounting of disks and images- Disk Arbitrator ( ). I figured, it must be the finder pinging the drive, trying to mount it. Then the I/O error started hitting every second or so again. Suddenly the speed burst up to 30MB/sec, but only for about 10 seconds. I thought it might be that I had parallels running, so I quit parallels. I noticed that the read was interrupted (drive sound wise) whenever the console would output that I/O error which was happening every second or so. When this started, it was moving through the disk at about 23kb/sec, which by my calculation would take roughly 264 days to read the drive. It also outputs a log at Rescue.log (this is important- it allows you to interrupt the copy, and start up where you left off). This is launching ddrescue in verbose mode (-v), will skip the splitting failed blocks step (-n), sets the cluster size of sectors read to 4096, and copies the raw disk data from /dev/rdisk3s2 to a dmg named Rescue. Sudo /opt/local/bin/ddrescue -v -n -c 4096 /dev/rdisk3s2 Rescue.dmg Rescue.log I also noticed that in the console I was getting periodic lines of: Disk Utility is showing a greyed out "Macintosh HD" partition, that is formatted with HFS+, which was promising, but there was no way to access the files.
Ddrescue gui mac mac#
Plugged it into my Mac Pro, and no go, the drive will not mount. So I got out the micro screw drivers, and T6 torx bit, and pulled the drive, to put it in an external FW case. Thought 2- this is an old machine (2007 MBP), perhaps it is the SATA chip on board that is dying. Tried to connect the MBP in FireWire mode to my Mac Pro- no go. My first thought was "No biggie- we have Time Machine!" So I go and look through the remote TM drive files, and realize that the last time my wife's machine was backed up, was roughly a year ago, around the time we installed Lion on it. I quickly shut the machine off in order to prevent further damage in case anything was salvageable. Upon a reboot in verbose mode (as the machine wouldn't boot) I was getting the dreaded Bus I/O error when the drive was being accessed. So on Wednesday night, my wife's MBP hard drive suddenly died. Back Story - (skip down to the next section for the data recovery portion)
![ddrescue gui mac ddrescue gui mac](http://e-cartouche.ch/content_reg/cartouche/ui_access/en/image/gui_hist/gui_mac_small.jpg)
I thought this might be useful to the rest of the MacAch, in case anyone else ends up in a similar situation.