build 3186 filesystem corruption/kernel panic

[cfg]

Has anyone else had problems with 3186 corrupting your filesystem? I've got a MacBook Pro 2.33ghz/3GB RAM, running 10.4.8. I had a VM from my boot camp partition, and it wouldn't hide if I hit cmd+h or hid it using Hide/Hide Others. At one point I quit another application and suddenly Parallels hid. After that it wouldn't show again, although the Finder reported it was responding. I quit all other applications, but switching to Parallels gave me a Firefox menu bar, complete with all options.

I finally had to force quite Parallels and about 15 seconds later had a kernel panic. Each subsequent OS X boot resulted in a kernel panic until I booted into single user mode and ran

fsck_hfs -d -r -y -f /dev/rdisk0s2

to repair the filesystem. Attempting to boot into Windows/Boot Camp gave me an error about a missing hal.dll. After repairing the filesystem my boot camp partition needed to be remounted.

Anyone else experienced anything similar?

 

[LLBrian]

This sounds very much like what happened to me this week.

On Friday afternoon I experienced a hard freeze on my 2 x 2.66/1GB Mac Pro while running 10.4.8, Parallels 3186 and an XP Boot Camp Install. I shut down by holding the power key, restarted, and left for the weekend. When I returned on Monday I logged in as usual and worked for a couple of hours, including running XP via Parallels. I then had a second hard freeze, and the machine would net reboot, kernal panicking shortly after the Apple logo appears. Clearing the PRAM, holding the shift key, even trying to start from the install disks all had the same result.

After taking it to the Apple store, I was able to start up in target mode, and copy my Users folder before performing an erase and install. Both crashes happend while I was Alt-tabbing through applications, and while Parallels was running.

I am now unable to boot into Windows, getting the "missing hal.dll" message. Any help fixing problem this would be greatly appreciated.

 

[hirosama]

i had this happen also, exactly same symptoms as the second poster after starting the Mac up again. i had to use diskpart from the Repair option of the XP setup CD, delete the Mac partitions, before it let me boot up from the OS X install disc.

there, i reformatted the entire drive and had to reinstall both OS X and XP from scratch. good thing i had nothing important in either, but setting everything from scratch is VERY annoying.

the problem is that OS X (and the Install Disc) would kernel panic whenever it tried to mount the OS X partition, which of course, it needs to do. in Single User mode, fsck doesn't detect any errors, and diskutil can't access the partition, but will also cause a kernel panic if you attempt to mount it so it can access it. :S

anyway, that is the last time i'll use Parallels with a Boot Camp partition, it's just not reliable. i'd be fine with it if it crashed the system but didn't cause all that much damage, but to screw up both the OS X partition and the Boot Camp XP partition is just too much to risk.

 

[zetsurin]

Me too

I also got this problem while away on a business trip and had to just stick with XP while I was away. Now I find I can't boot off the OSX Discs at all or my colleagues mag DiskWarrior disc! Not happy at all. The interesting thing is that Macdrive mounts the partition fine. This kind of leads me to think that Apple should make the code that mounts the filesystem just a tad more robust! Unless of course some binary code has been screwed up here. Regardless, this is the last I am using Parallels (despite being a registered user since early beta phase) and the first thing I will do is get VMWare Fusion on there. It's not necessarily the fact that this has happened, it's the complete and utter silence from Parallels about this issue despite it popping up all over the place in the forums! I am a software developer by profession and thus understand that it's not all straightforward and things can and sometimes will go wrong, but the silence is deafening. Not impressed.