A catalogue of 'stuff' which somehow will help me through life by helping me remember problems I've solved, how I solved them and thoughts which will be otherwise forgotten (some of which might be of use later on).
Thursday, 3 February 2011
MacBook Pro 17" fsck error EXITED WITH SIGNAL 8
Rob brought in his 17" MacBook which wouldn't get past the white screen with a gray apple and spinning dotty thing. I tried resetting the PR RAM. Next I tried single user mode with /sbin/fsck -yf. Results as shown:
Rebuilding B-Tree could not repair volume /dev/rdisk1s2 (hfs) EXITED WITH SIGNAL 8
Looked this up and found quite a few people with MacBook Pro's having the same error, looked to be related just with the file system and probably not a hard drive fault (hopefully). As Rob needed stuff off the HD I found only one command which might fix it, found it here:
Boot off the OS X CD (reboot, hold C while booting).
The installer will load up, go to Utilities in the menu and run Terminal.
Type df and look for the drive that has your Mac system mounted---you'll have to unmount this. On my MacBook Pro, it was /dev/disk0s2.
Type umount /dev/disk0s2, replacing disk0s2 with whatever disk your OS lives on.
Type fsck_hfs -r /dev/disk0s2. If you umounted the wrong thing, it will complain that you can't repair a mounted drive. Go back and umount the right thing and repeat this step.
I found netbooting to a deploy studio image had the same results as using the install disk. Coinsidence or not it, it was disk0s2 that was the OS X partition.
Anyway, it came up with another error, saying volume could not be repaired. I put it in target disk mode and mounted it on another MacBook Pro. It came up saying that there are serious issues with the volume which cannot be repaired, it is only being mounted to retrieve files which should be backed up immediately.
I used Migration Assistant to get the user account across, and copied other erroneous files. I re-partitioned and re-imaged the macbook pro and all is well.