Sep
22
29

Mac Woes

Apple, Asides

After a security update my 12″ Powerbook asked me to reboot, after which it decided that it will only boot to a command line. I have no idea how to even start to fix this, I can navigate around it like it’s Linux but there is no indication of what went wrong or how to fix it. I’m going to take it to the Genius bar in hopes they can do something, but all-in-all this is pretty disappointing.


29 Comments

  • Lloyd D Budd September 22, 2006 @ 2:54 pm

    Dang. Is there anything interesting/understandable written to console?

    Does it relate to the problem Barry had?

    It is Apple’s way of telling you that it is time to buy a new Mac :groan:

  • Matt September 22, 2006 @ 2:59 pm

    Nothing interesting on the console. It’s perfectly functional… except for having a graphical user interface. If I navigate the command line it looks like all my files are there and fine.

  • Dougal Campbell September 22, 2006 @ 3:06 pm

    Does anything happen if you run the ‘startx’ command?

    I’m not sure if that’s valid for OSX, though.

  • Robert Accettura September 22, 2006 @ 3:54 pm

    May want to keep an eye on MacFixIt.com for similar issues, or perhaps submit a report on yours, and see if others respond. Their forums are extremely helpful too.

  • Daniel Gattermann September 22, 2006 @ 4:29 pm

    ‘startx’ starts X11 if you have it installed. But that’s not what Matt wants…

    Maybe you could try the solution mentioned in this thread:
    http://discussions.apple.com/message.jspa?messageID=710541#710541

  • Smoove D September 22, 2006 @ 4:30 pm

    I didn’t realize Bill Gates bought Apple.

  • zach September 22, 2006 @ 4:38 pm

    if you haven’t rebooted it, give that a try. the command for a safe reboot is: shutdown -h now
    this will safely shutdown your system. wish i could offer you more help.

  • Ryan September 22, 2006 @ 5:02 pm

    I bet you $10 it’s a corrupt font. Who wants to take the bet?

  • Jess September 22, 2006 @ 5:12 pm

    How about booting from a cd or external drive?

  • Ray September 22, 2006 @ 5:52 pm

    OMG an Apple problem? You mean it doesn’t just “work” all the time? Don’t tell Alex, or he and his goons will take you out…

  • Doug Stewart September 22, 2006 @ 6:08 pm

    Sounds like you may have booted into single-user mode.
    What happens when you type “exit”? What about “reboot”?

  • adam September 22, 2006 @ 6:18 pm

    heh, douglas said what i was thinking. except x runs inside quartz.
    maybe startquartz?

    backup your files before you go to the genius bar. they have a habit of charging you to protect your data if you haven’t already.

  • Matt September 22, 2006 @ 6:49 pm

    Update

    The guy at the genius bar booted into single-user mode and ran fsck which found some core files and system information corrupted, and repaired it.

    On another reboot it did exactly the same thing, it looks like it boots perfectly and then it dumps out to the command line.

    He suggested I do a re-install of the OS, which I guess I’ll try after I get all my data off.

  • Lloyd D Budd September 22, 2006 @ 8:06 pm

    Dang brother that is the suck.

    How did the fsck look? The security update was likely a red herring then. Boot is the most likely time a bad disk will rear its ugly head.

    How did the fsck look? Do additional fsck find anything? Had you previously noticed slow boots?

    I would be cautious about a bad hard disk, and depending on how important your productivity is on that computer be ready to replace it, or even replace it now.

  • Jacques Distler September 22, 2006 @ 11:11 pm

    I’ve seen this happen a couple of times on my wife’s iBook. The solution mentioned in comment #5 worked both times.

    Clearly, what is happening is the GUI is dying before getting to the stage of presenting you with a graphical login prompt (from loginwindow.app). I would strongly recommend perusing /var/log/system.log to see what’s failing between the reboot and when the system drops you into single-user mode.

    A corrupt .plist file is far more likely a culprit than something requiring a full OS reinstall.

    (Of course, in all the years I’ve used MacOSX, I’ve never done an OS reinstall. So maybe I’m just prejudiced.)

  • Mike September 22, 2006 @ 11:15 pm

    Matt, this article will show you how to reinstall OS X without losing any data:

    http://docs.info.apple.com/article.html?artnum=107120

    You’ll probably need to reinstall a few applications, but most apps will still work, and your data will stay intact.

  • Daniel Gattermann September 23, 2006 @ 1:24 am

    Matt, if you just install OS X over the old version you shouldn’t lose any data or settings. Just a couple of custom preference panes may need a reinstall. At least that was my experience with my last reinstall after I did some bad things to my system (removing all PowerPC binaries instead of the X86 ones on a PowerBook).
    Of course: backup first.

  • KO September 23, 2006 @ 1:31 am

    It seems the Apple support guys are taking a leaf out of Microsoft’s pet answer to all ailments: “Reinstall the OS”. Pretty bad, that one.

  • Anthony September 23, 2006 @ 8:32 am

    KO, it’s not a reinstall. It’s called an Archive and Install. You don’t lose your data, only a few system level settings.

  • Luke September 23, 2006 @ 12:03 pm

    Did anyone read about a similar problem with an Ubuntu security fix?

  • elissa September 23, 2006 @ 4:06 pm

    burn. remind me not to update until they figure out what’s up. you think it’s the OS update or do you think it’s your computer?

  • Pete September 23, 2006 @ 7:50 pm

    The command-line you are in, is it a light colored background with black text? If that is the case, you are in Open Firmware Mode. To fix this, type the following:

    reset-nvram

    reset-all

    Hit return after each line. That should clear your non-volatile RAM and force the machine to reboot. If that doesn’t solve it and you end up in the same spot, you can also try typing:

    mac-boot

    Again, hit return.

    Good luck!

    –Pete

  • Kevin Burton September 25, 2006 @ 3:52 am

    This has happened to me before…….

    You can do an “archive and re-install……” It takes your current OS files, backs them up, and then lays down a new OS. It requires an extra 4G since you basically now have two OSs on your disk but you don’t have to worry about backing up your files.

    I’d do a backup just in case though :-P ….. This process is still easier than a full re-format…..

  • Arne September 25, 2006 @ 6:28 am

    if you have another mac, you could try connecting the two of them with a firewire cable and booting it in target mode.

    cheers

  • option8 September 25, 2006 @ 10:58 am

    for this, and many other reasons, i install applejack on every mac i work on: http://applejack.sourceforge.net/

    works in single-user mode to do fscks, clear caches, repair permissions, find and remove corrupted .plists – most of the things that will cause trouble on OS X. since it works in single-user mode, you can still run it, even if aqua or the finder are b0rked.

  • Matt September 25, 2006 @ 3:05 pm

    Update: An archive and install did work, and I’m back up and running.

  • Stilgherrian September 25, 2006 @ 4:06 pm

    It’s interesting to see how resistant people are to reinstalling the operating system — even more so in OS X land than in Windows. If the OS is corrupt, then fiddling with things until the symptoms go away doesn’t mean there isn’t still some lurking problem. A reinstallation at least means you’re starting with a clean slate and can move forward.

    In many cases, deciding from the very beginning that the OS is screwed and starting with a clean install gets to you to the end much faster — provided you don’t waste hours trying things at random based on blogger speculation. ;)

    The trick is to keep a backup of your clean-install-with-apps, not just your data. That way a recovery is (1) wipe hard drive and install OS, (2) install disc imaging tool, (3) copy disc image — a procedure which isn’t necessarily “quick” (lots of data to be copied) but at least it’s of known duration and a no-brainer.

    Of course if you know _precisely_ what’s wrong and _precisely what’ll fix it is good — if you know it.

    And option8 is right — applejack is your friend. :)

  • mattyrob September 26, 2006 @ 2:42 am

    Presumably you followed the Mac Update Mantra?!?

    1/ Quit any running Applications
    2/ Repair Permissions
    3/ Run the update
    4/ Repair Permissions

    Don’t forget that re-installing Windows(TM) periodically is virtually a recognised part of system maintenance!!

Share Your Thoughts