Dealing with Mac OS X Kernel Failures

√ Mac OSX Leopard quit booting on me unexpectedly and it was really bad. The only thing I got from it was a cold screen asking me to reboot. No safe mode, no single user, nothing worked and I had no options beside the Mac DVDs, which obviously I do not carry around for a two week trip to Europe. Moreover, apple resellers are scarce in Romania. I was lucky enough to get to one in Cluj Napoca and to convince them at least to borrow me a DVD to repair my system. But after a couple of hours, the diskutility did not find anything wrong with my drive. Still couldn’t boot ( a message to reboot over and over again). I had bootcamp and WinXP which worked well throughout. however, the macdrive 7 (program under Win) couldn't see the Mac partition as well. after about 5-6 verifications or the drive (all passed with flying colors), suddenly macdrive saw my OSx partition and files..and now even MacOSx booted successfully. Nothing really makes much sense (why the failure?...how come it recovers once every dozens of boot sequences?) just glad and hopeful that it will work from now on. I bought this macbook in september and I never had any issues or blue screens neither in MacOSx or WinXP. Untill now..

Update: actually it stopped booting right away. The funny thing is that DiskUtility did not find any permissions to repair or something wrong with the drive. It is just unmountable according to the Mac OSX recovery disk. Then, played around with Linux commands (fsck, disk repair stuff etc.). Nothing. There aren’t any other options from the Mac DVD…ridiculous. And I couldn’t do anything with the MBR (did not find anything on that on the web). Then I tried installing a partition manager supposedly a good one (Paragon) to attempt to revive the HSF+ one, but things got worse: now my Bootcamp-ed Win XP is also not booting. I guess they didn’t get along cause afterwards the MacOSx recovery disk didn’t see the Win partition as mountable anymore. And, just I tried before with the Mac HDD, you cannot mount anything, even after you check all the drives for permissions and errors. Which makes me wonder why the hell they even have such stupid utilities.
Desperation: Tried every single recovery software on the web (not that many anyways). I would recommend Hiren Boot CD. It has a mini XP on it which at least allows you to read the FAT (courtesy of a stupid Bootcamp rule) partition of Win. At this point the plan was to extract all the info from the Win disk and if it comes to the worst, just wipe it and install a clean Win. Then with MacDrive and/or a HFS+ reader I could have reached my (bulk) data on the Mac drive. But still, I wasn’t ready to give in.
However, despite the hours put in, I didn’t find anything that was able to fix even the boot for Win. Tried the installation cd with the recovery console, also other recovery packs/cds. None did the job for me.
Finally, and this is where it might get interesting for the reader, I came across a nice, small, elegant freeware that worked like a charm for Win. Its name is rEFIt and it is a boot menu and maintenance toolkit for EFI-based machines like the Intel Macs. You can use it to boot multiple operating systems easily, including triple-boot setups with Boot Camp according to their advertising. It also provides an easy way to enter and explore the EFI pre-boot environment. MacOSX also booted nicely afterwards, but also crashed. Perhaps the stupid 200 MB updates for the system, Quicktime and Iphotos or whatever applications did that but again, what is one suppose to do? First time after rEFIt, it worked fine so I thought let’s install also the mac updates that I’ve been postponing for a while now. Then, it crashed again.
Now, I am OK with the Win boot. Ran the diskutilities again and it found some messed-up permissions on the Macdrive…after the system updates (QuickTime and Iphoto) but still access to its using MacDrive7 is not consistent. But if you just need to read the partition HFSExplorer is perfect.
I will probably survive in this way until I get back to US and ghost my mac harddrive or backup everything in some other manner and then reinstall a fresh copy of Leopard.
A crazy week sacrificed solely on dealing with Mac crashes. Still, I have no clue as for what caused the initial crash, especially since I haven’t updated anything lately or played with the Bootcamp settings.

Fri Jun 26 07:16:05 2009
panic(cpu 0 caller 0x002D9B96): "nfs_boot_init failed with 6\n"@/SourceCache/xnu/xnu-1228.9.59/bsd/nfs/nfs_vfsops.c:851
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x4eedb8c8 : 0x12b4f3 (0x45b13c 0x4eedb8fc 0x1335e4 0x0)
0x4eedb918 : 0x2d9b96 (0x4850a8 0x6 0x6a372dc 0x0)
0x4eedbd68 : 0x1ddae8 (0x690fb84 0x6a43f40 0x5266cc 0x1)
0x4eedbea8 : 0x4d5d44 (0x5557f0 0x10 0x5557e8 0x4eedbf8c)
0x4eedbfa8 : 0x13815c (0x0 0xf4ab401f 0x1380de 0xd2ad007f)
0x4eedbfc8 : 0x1a017c (0x0 0xffffffff 0x1a302a 0x0)
Backtrace terminated-invalid frame pointer 0

BSD process name corresponding to current thread: kernel_task

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBook4,1 (Mac-F22788A