1 6 7 8 9 10 Previous Next 199 Replies Latest reply: Apr 3, 2014 8:30 AM by Kikonda12 Go to original post
  • 105. Re: Will not boot into Safe Mode
    siavoshmahboubian Level 1 Level 1 (0 points)

    I have just re-installed Mac OS X Mountain Lion again from scratch (Macbook Air mid-2012 8GB), and safe mode still doesn't work. It doesn't have anything to do with the RAM, since I haven't touched anything from when I bought it, and therefore I think that it must be a problem with the operating system itself. Hopefully they will send out an update soon to address the issue.

  • 106. Re: Will not boot into Safe Mode
    nelfo Level 1 Level 1 (0 points)

    FWIW I too removed one of my two self-installed RAM modules, then switched both back to the original modules and neither allowed me to boot into safe mode.

     

    After 20 over years and roughly 10 Macs, now sitting here staring at beach balls and system hangs while powerless to do anything about it, I'm beginning to think about switching to Linux. At least then I won't be paying a premium for my headaches.

     

    If anyone has heard anything encouraging from Apple on this issue, please share.

  • 107. Re: Will not boot into Safe Mode
    Peter Berglund Level 1 Level 1 (40 points)

    Just an update. It has now been roughly two weeks since I solved my console log issue by Safe Boot. So far the original issue has not come back and the console is still very "empty". For me, the DiskWarrior repair worked to get to Safe Boot.  I will let you know if the log problem comes back.

  • 108. Re: Will not boot into Safe Mode
    laughing_badger Level 1 Level 1 (0 points)

    I was also hit by the problem where I couldn't safe boot to clear the 'mdworker: Unable to talk to lsboxd' issue. This is how I resolved it:

     

    cd /sbin

    sudo mv fsck_hfs fsck_hfs_orig

    sudo cp ~/true fsck_hfs

    sudo chmod ugo+rx fsck_hfs

    nvram boot-args="-x -v"

     

    reboot, log in

     

    sudo nvram boot-args=""

     

    reboot

     

    cd /sbin

    sudo mv fsck_hfs_orig fsck_hfs

     

    It doesn't seem to be the fsck on safe boot that resolves this issue, so disabling fsck for the duration of the safe boot seemed to work. I compiled my own version of true, but the system one in /usr/bin/true would probably work ok too.

     


  • 109. Re: Will not boot into Safe Mode
    Cerniuk Level 1 Level 1 (10 points)

    Good debugging leads but....  One of the main reasons for Joe User to boot into Safe Boot is to have it run its fsck.

     

    Imagine you have an Administrative Assistant, a Surgeon, or an 85 yr old dad remotely with a hard disk problem.  It is easy to coach them into a reboot and hold the shift key down.  It is agnonizing to coach them into a reboot to a recovery disk which may not show up, to run through menus and options to get to Disk Utility to run Disk Repair, yadda yadda, 1/2 a day is shot.  Add in a little ADD action at the end user side and thanks, but I would rather have someone stab me in the eye with a fork. (it's quicker).

     

    Good start on diagnosing this but I would be careful about calling it "resolved". Def NOT the resolution we want Apple to pursue... :-)

  • 110. Re: Will not boot into Safe Mode
    Olaf Barthel Level 1 Level 1 (0 points)

    I salute you: this is the perfect workaround for the stalling file system check issue (until a real solution comes around)!

  • 111. Re: Will not boot into Safe Mode
    Eyeless77 Level 1 Level 1 (0 points)

    Maybe I'm doing something wrong, but I get an error on the third step:

     

    eyelessmacbook:sbin Eyeless$ sudo cp ~/true fsck_hfs

    cp: /Users/Eyeless/true: No such file or directory

  • 112. Re: Will not boot into Safe Mode
    Olaf Barthel Level 1 Level 1 (0 points)

    laughing_badger wrote that he compiled the "true" command locally. The following might work for you:

     

    sudo cp -p /usr/bin/true fsck_hfs

     

    Bonus: "cp -p" preserves the file access rights, which means that you do not need to enter the "chmod ugo+rx fsck_hfs" command (the rights are all set by the time the copy is made).


  • 113. Re: Will not boot into Safe Mode
    Demetri Alekseev Level 1 Level 1 (0 points)

    The latest Mac OS X beta seems to fix this problem...

  • 114. Re: Will not boot into Safe Mode
    Eyeless77 Level 1 Level 1 (0 points)

    Thank you and laughing_badger, that worked for me!

  • 115. Re: Will not boot into Safe Mode
    Michael_505 Level 1 Level 1 (0 points)

    Thanks for the info laughing_badger. I'm still waiting for my FileVault to decrypt (I started this for troubleshooting before I read this thread), so I have not yet confirmed this works for me. I'm not sure what "true" means here, and my /usr/bin/true is not a directory (it's a file), so I must have missed something.

     

    I have to say that if this does work, Disk Utility seems to be the thing lacking here -- I have encountered many situations now where Disk Utility should have been able to detect a problem, and many situations where it detected problems but was unable to fix them and only suggested a restore from backup. This is unacceptable for any current disk repair tool, let alone one that ships with one of the the most expensive computer brands on the market.

     

    It feels like this lack of open bug reporting (as described earlier by Dave) and this lack of providing the user with adequate tools to even diagnose the problem is just getting worse and worse with Apple. I get the feeling that they have pulled most of their resources away from desktop and laptop development and put them on iOS, where they make more of their money. This could precipitate a vicious cycle for the OS X devices (lower development = lower quality = fewer customers = less revenue = lower development = ...). I certainly hope to see things turn the other way, but it's not looking very good right now. 

  • 116. Re: Will not boot into Safe Mode
    Michael_505 Level 1 Level 1 (0 points)

    Update: after I disabled FileVault and rebooted, I was able to safe boot, so my problem was not the same as others described here. I thought Apple fixed the FileVault safe mode boot problem, but I guess not.

     

    Other things that are possibly useful here:

     

    1) I recently had major file system problems (caused by a bug between MS Word 2011 and TimeMachine), and did a full system restore from TimeMachine backup last night. this may have fixed some of the file system problems others may be running into, but I'm not sure.

     

    2) I have 16 GB of RAM (Kingston) in my late 2011 15" Macbook Pro (which is only supposed to take up to 8 GB from Apple, but I successfully ran a memory test -- Apple's, not memtest86 since I could never get memtest86+ to actually boot on my system). This may help quench some of the memory concerns(?).

     

    3) I upgraded my system from 10.7 to 10.8 while FileVault was on, and I never safe booted since the upgrade, so my problem is possibly due to the old bug where safe booting was not possible with FileVault.

     

    4) The safe boot seems to have fixed the sandbox issues I was having like so many others have reported. This is what led me to this thread (trying to safe boot) and this seems to be a very serious problem -- especially for those who can't safe boot. The problems are stacking up like a train wreck here, Apple: you have bugs on top of bugs on top of bugs, and all of which have to do with some very critical parts of the OS.

  • 117. Re: Will not boot into Safe Mode
    nelfo Level 1 Level 1 (0 points)

    Michael_505 wrote:

     

    Apple: you have bugs on top of bugs on top of bugs, and all of which have to do with some very critical parts of the OS.

     

    Likely one reason they have had eleven beta builds of 10.8.3 since November.

  • 118. Re: Will not boot into Safe Mode
    mhaitjem Level 1 Level 1 (0 points)

    I have an iMac27 mid-2010 and a MacBookPro early-2011 both running 10.8.2 and both were unable to boot into safemode (hanging after displaying: ** Checking extended attributes file).

     

    The only thing that allowed me to boot into safe mode was to use the RAM that originally came with the machine.

    I tried many of the suggestions listed in this thread and the only one that worked for me was to remove the additional 3rd party memory and reinsert the original RAM sticks that came with my machines. After doing this I was able to boot into safe mode and fix the sandbox issues that some others have also mentioned. Hope this helps anyone who runs into a similar situation.

  • 119. Re: Will not boot into Safe Mode
    kallisti Level 1 Level 1 (0 points)

    I'm eager to learn the finer details of precisely what this does if anyone has the time to break it down command-by-command for me; I would tremendously appreciate the education:

     

     

    laughing_badger wrote:

     

    I was also hit by the problem where I couldn't safe boot to clear the 'mdworker: Unable to talk to lsboxd' issue. This is how I resolved it:

     

    cd /sbin

    sudo mv fsck_hfs fsck_hfs_orig

    sudo cp ~/true fsck_hfs

    sudo chmod ugo+rx fsck_hfs

    nvram boot-args="-x -v"

     

    reboot, log in

     

    sudo nvram boot-args=""

     

    reboot

     

    cd /sbin

    sudo mv fsck_hfs_orig fsck_hfs

     

     

     


1 6 7 8 9 10 Previous Next