Two computers, both running 10.8.2. 2009 MBP with File Vualt 2 enabled. I am able to boot into safe mode by holding down the shift key. I get a login screen where I have to login, then the boot proceeds as normal (safe boot).
Second machine is a new 2012 iMac. I cannot safe boot. I rebooted into single user mode with safe boot (nvram boot-args="-x -s") and ran fsck -fy and it has been running for several hours at "checking extended attributes file".
I can boot into the recovery partition and check the disk and there are no problems.
Same here. MBP 2013. Did a clean install of Mountain Lion. Now 10.8.2. Never activated file vault.
Can't boot into safe mode. Get stuck at "checking extended attributes file", if I boot into safe mode with verbose flag on.
Any updates on the bug report (which I can't access under number 12988864 that WebHarmony mentioned)?
I received notice from Apple.
They asked me to create a coredump on a server machine, which I was not able to do because the server machine reported "Cable Unplugged"
And they asked me to set nvram using sudo command which I did.
And send send them the last lines on the screen, which I did.
You might also try
sudo nvram boot-args="-v -x"
then reboot. This would put the machine in "permanent" safe mode, but with verbose booting. Let us know what the last messages on the screen are. To reset this back to normal, try "sudo nvram -d boot-args" or reset PRAM (cmd-opt-P-R at boot)
My machine got stuck so I had to use the reset PRAM option, which I had to try 4 or 5 time, so be careful if you want to try it yourself.
The last lines of my machine were:
last messages on screen:
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attribute file.
Firewire (OHCI) Lucent ID 5901 built-in: 51 bus resets in last 3 minutes
- waited some more
Firewire (OHCI) Lucent ID 5901 built-in: 52 bus resets in last 3 minutes
Here mine got stuck and I had to use Power Button to get it going again.
I went through exactly the same steps on December 1st 2012 to see how far the process would get. My MacBook Pro (2011) did not get any further than the "** Checking extended attribute file." line, although I switched it off after about four hours when it did not seem to be getting anywhere.
If necessary, I'll be happy to repeat the test.
This morning I took some time and removed my extra installed 3rd party RAM.
Booting normally went fine.
Safe Mode boot (Pressing the Shift key) went fine, took about 3 minutes.
Normal Boot again, went fine
Safe Mode Boot with Verbose mode (Pressing Shift + Command + V) went fine , took about 3.30
Normal Boot again, went fine, about 30 secs
Safe Mode Boot again, went fine, about 3 minutes.
Installed the extra 3rd party RAM.
Normal Boot, went fine.
Safe Mode Boot, killed it after 10 minutes by pressing and holding the power button.
Normal Boot, went fine, about 30 secs.
So, I conclude that in my case, the problem is in the 3rd party RAM
I noted all the numbers:
Assy in China (2)
Hope this will be helpfull to some.
I will enter this information also into the bugreport at Apple, as this in any case points to a problem.
So maybe they will be able to solve not being able to Boot into Safe Mode when this kind of extra RAM is installed.
I'm not sure the exact type, but I have Mushkin RAM in my MBP running 10.8.2 so if RAM is the problem, it's not isolated to Kingston.
From system profiler:
Size: 4 GB
Speed: 1333 MHz
Part Number: 0x393731363437410000000000000000000000
Serial Number: 0x00000000