Can't boot after 10.6.6 update

I see lots of new complaints here about system slowness, apps not working, etc., but after updating my MacBook Pro from 10.6.5 to 10.6.6, I can no longer boot into OS X.
If I do a verbose boot, I see some complaints regarding VMware's vmnet adapter:
vmnet: Invalidating peer info for hub: 0, port: 0
vmnet: VNetUser-IfFree: freeing user If at [mem-address]
... and then it goes no further. I have let this run for over an hour without any progress.
I've also booted the install DVD and repaired permissions and the disk, but that didn't help.
I've also booted via "safe mode" (Shift on boot), which showed an additional progress bar at the bottom of the boot screen for a while and then went back to the spinning progress circle. This too has run for over an hour now.
Don't know what else to try at this point. Of course, I had written a presentation in Keynote that is due in an hour, and this is my only Mac.

Sorry ... what?!? I'm not sure from where you made this assumption, but of course I keep data back-ups; and I'm not sure what you classify as a "production machine", but I certainly don't consider a laptop a production system (again: my data is safely backed up).
If you have a presentation due in an hour, which is what your post said, surely you anticipate the ability to access that presentation in an hour, and not be beset by issues resulting from updates, hardware issues, etc, I would classify that as a production machine, because time sensitive access is a necessity. One should not be shooting oneself in the foot by modifying what is working until one is absolutely certain that it won't affect their ability to access time sensitive data. Since you are backed up, the issue presented here, is one of a machine which may need directory repair, or to be cleaned up so it isn't too full that the machine can't boot, or one of not having compatible firmware or drivers with the new operating system. Whichever, a recovery of a backup would allow one to continue as if no update had happened, it would also allow one to recover to another hard drive if the hard drive is dying, it would also allow one if the directory is too badly munged to recover data to another hard drive, but whichever the issue, you have within your power the ability to recover from this situation. To repair the directory I give directions here*:
http://www.macmaps.com/directoryfaq.html
If it can't be repaired, that's when you have to assume the drive may be dying.
If it can be repaired, but won't boot, that's when you assume that some driver was installed that won't work with the new operating system, and you'll have to downgrade.
Whichever the scenario, your backup saves you a lot of trouble.
- * Links to my pages may give me compensation. I merely have to say this whenever posting links to my site. That's just a given because of the terms of this forum.

Similar Messages

  • Can't boot after 10.7.3 update

    Hi,
    I installed the 10.7.3 update and now i cant boot....
    my mac hangs on the apple logo with the spinning weel and just stays there forever...
    i tried to reset the smc but still nothing.
    When i did the boot on verbose mode, this is the message i got when it hangs:
    dyld: library not loaded:/usr/lib/libxar-nossl.dylib
    referenced from:/system/library/frameworks/security.framework/versions/A/security reason:image not found
    com.apple.launchd1com. apple launchetl.system2
    the system bootstrapper has crashed: trace/bpf trap:5
    can anyone help me out? i need my mac to work and now can't use it...
    I Tried to do the re-install of lion on the recovery menu but it just hanged for the whole weekend on the "Loading Installation Information..." part....
    i have a decent internet connection so i don't think it's the internet's fault.....
    Thank you in advance

    Problems on the hard drive would be my guess. Here's the less invasive solution:
    Reinstalling Lion/Mountain Lion Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    This will install 10.8.3 so no update will be required afterwards.

  • HELP!  Can't boot after latest Apple Security Update (Released yesterday?)

    The latest security update, which came out yesterday (I think it's this update: http://docs.info.apple.com/article.html?artnum=305530 ) has ravaged my Mac.
    I have a PowerMac G4 Dual 1.25 MDD.
    I installed the update, and rebooted like it said.
    Once the computer came up, it got past the grey screen with the spinning wheel, the screen turned blue, right before it should present the login window... and then the grey (translucent) curtain slid down from the top, and a box in the center told me to hold down my power button and restart my computer.
    Now this happens EVERY TIME I TURN MY COMPUTER ON.
    I HAD a PERFECTLY RUNNING MAC BEFORE I INSTALLED THIS UPDATE. NOW IT'S COMPLETELY UN-USABLE.
    HELP! HELP! HELP!
    WHAT CAN I DO TO FIX THIS?
    I'm searching for bootable discs to try to get the Mac to come up so I can look at it. I haven't tried going in through single-user-mode (command prompt) yet. I came here first, because I need support FAST!!!
    By the way, before this update, I was completely up-to-date with my Apple patches/updates. I was running 10.4.9 (I don't remember the Build #, but I was CURRENT).
    Thanks in advance for any support (Apple?!?!)

    Ladies and Gentlemen:
    Sorry for the alarming post. I'm replying to my own post to let everyone know that I don't think the problem is the Security Update alone. For lack of anything better to do, I decided to try troubleshooting this problem by myself... and here's what I did:
    I booted the Mac in to Single-User mode, by holding down Command-S. Once in, I forced fsck to pass verification of the drive (fsck -fy). Then I mounted the root partition in Read/Write (mount -uw /). Once I had write access to the drive in the command prompt, I quickly decided to check out what applications and services were starting when my computer boots (/Library/StartupItems ; /Library/LaunchDaemons). From there I removed all third party applications and services. (I maintain a "StartupItems-Disabled" folder, and a "LaunchDaemons-Disabled" in the spirit of pre-OS X machines that had something similar in the System folder for extensions and control panels (if my memory serves me)... so that's where I put all the applications and services that I didn't want to boot (I moved them from the respective folders in to the "-Disabled" folders I had created).
    Anyway... after removing all the third-party software and services from Startup, I rebooted, and my Mac came up just fine. I'm going to sift through the logs to see if anything was written about what happened at boot all those times. With any luck I'll figure out which application or service wasn't playing nicely with the OS and/or Security Update.
    Good luck with your own endeavors. It's always scary when your Mac doesn't boot, so I hope this doesn't happen to anyone else (especially someone less technically inclined). I'll check the forums later to make sure no one else had similar problems... because I'm sure I could help them get to the bottom of their troubles.
    Cheers!

  • Will not start even in safe boot after installing latest camera update

    MacBook Pro will not start even in safe boot after installing latest camera update.
    I started my machine and did a software update. Only the camera update needed. So installed and when required I pressed restart. It restarted and did install. Then restarted again. I expected to get to the login screen and it turned itself off. Tried three more times. Each time shutting off. I unplugged everything, and pressed start waiting for log in window. No it shutdown before the log in window. I then tried safe mode and that did not work either on three more occasions.

    I have managed to resolve some issues. I can now restart the machine via a CD boot. If I do cmd C into something like tech tool pro, then restart from that disks menu it restarts every time.
    If I try a safe start it shuts down. If I try a normal start it shuts down. I have managed to repair permissions and that cleared up some start up permissions but with no improvement to the boot problem. The only way to load is via the cmd-C boot option. Any other ideas?

  • For Those Who Can't Boot After Upgrading To 10.5.6

    For Those Who Can't Boot After Upgrading To 10.5.6
    (and i am one of those)
    how is Apple supposed to make them able to install future fixes and updates
    once they finally acknowledge and address this horrible bug?
    will they send free bootable CDs with the updates to 10.5.6?

    What "Boot ROM version" do you have (check in the system profiler under "Hardware")? If it's not MBP31.0070.B07 or MBP21.00A5.B08, then you will need to update your MacBook Pro's firmware. To do this, you might need to connect an external display and mouse/keyboard, and then run the computer with the lid closed to bypass the laptop's monitor. Then apply the firmware patch and reboot the system. This might also be doable via "Screen Sharing" if you have that enabled and have another mac handy.
    The firmware update is here: http://www.apple.com/downloads/macosx/apple/firmware_hardware/macbookproefifirmw areupdate151.html
    Message was edited by: Topher Kessler

  • Kernel panic on first boot after 10.6.8 update

    Hi,
    Here are the fact:
    1) I systematically get a kernel panic on first boot after an attempt to update to 10.6.8 (was able to revert to 10.6.7 using Time Machine; now I'm running my tests on a clone). While doing the update, there are NO USB connexion to my laptop, nor ethernet connexion. Only the power cable.
    2) I DO NOT use the software Hands Off which is known to cause such an issue
    3) I've tested this on two different hard drive (with a clone of my system)
    4) I disabled all third app on startup just to be sure this wasn't a conflict problem
    5) After a kernel panic, I'm always able to boot in safe mode
    6) I did try both the normal update and the combo update (same result)
    Now I'm kinda stuck. The next test I'm thinking performing is to update while in safe mode. But I don't know if it will help.
    And yes, my permissions are all fine. Any idea how to troubleshoot this? I believe I need to be in 10.6.8 in order to update to Lion?
    Many thanks in advance!
    Parneix

    Hi,
    Sorry about that. Below you'll find the log of my latest kernel panic.
    I did follow instructions suggested by user "ds store". The only "kext" file that I've got (by running the commands in the Terminal) was related to the software LittleSnitch. I downloaded it again in order to run the uninstaller. I'll try again to update to 10.6.8 under those conditions and report here.
    Mon Jul  4 11:00:32 2011
    panic(cpu 0 caller 0x2abf6a): Kernel trap at 0x57cf1b5a, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00100000, CR4: 0x00000660
    EAX: 0x00000000, EBX: 0x096b8100, ECX: 0x01500000, EDX: 0x00000001
    CR2: 0x00000000, EBP: 0x57dd3df8, ESI: 0x00000001, EDI: 0x096b8100
    EFL: 0x00010206, EIP: 0x57cf1b5a, CS:  0x00000008, DS:  0x00000010
    Error code: 0x00000000
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x57dd3be8 : 0x21b837 (0x5dd7fc 0x57dd3c1c 0x223ce1 0x0)
    0x57dd3c38 : 0x2abf6a (0x59e3d0 0x57cf1b5a 0xe 0x59e59a)
    0x57dd3d18 : 0x2a1a78 (0x57dd3d30 0x10001 0x57dd3df8 0x57cf1b5a)
    0x57dd3d28 : 0x57cf1b5a (0xe 0x9790048 0x9790010 0x10)
    0x57dd3df8 : 0x57cf1951 (0x96b8100 0x57cf1f64 0x57cf1f5c 0x7d22fc0)
    0x57dd3e18 : 0x543f60 (0x96b8100 0x6c03f00 0x1 0x506b76)
    0x57dd3e78 : 0x542137 (0x6c03f00 0x96b8100 0x7d28a00 0x9791da0)
    0x57dd3f28 : 0x5426e9 (0x6c03f00 0x7d20340 0x0 0x516766)
    0x57dd3f78 : 0x5443d5 (0x6c03f00 0x8 0x57dd3fac 0x1)
    0x57dd3fc8 : 0x2a179c (0x9773aa0 0x0 0x2a17ab 0x7c1b000)
          Kernel Extensions in backtrace (with dependencies):
             com.apple.iokit.CHUDKernLib(3)@0x57cf0000->0x57cf3fff
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    10K540
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
    System model name: MacBookPro5,5 (Mac-F2268AC8)
    System uptime in nanoseconds: 54454580752
    unloaded kexts:
    (none)
    loaded kexts:
    com.Cycling74.driver.Soundflower          1.5.1 - last loaded 54075922238
    com.Logitech.Control Center.HID Driver          3.2.0
    at.obdev.nke.LittleSnitch          2.2.05
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.iokit.CHUDUtils          3
    com.apple.driver.AppleIntelYonahProfile          14
    com.apple.driver.AppleMikeyHIDDriver          1.2.0
    com.apple.iokit.CHUDProf          3
    com.apple.driver.AppleUpstreamUserClient          3.5.7
    com.apple.driver.AppleIntelPenrynProfile          17
    com.apple.driver.AppleMikeyDriver          2.0.5f13
    com.apple.driver.AppleHDA          2.0.5f13
    com.apple.driver.AppleGraphicsControl          2.10.6
    com.apple.driver.AppleMCCSControl          1.0.20
    com.apple.driver.AppleIntelNehalemProfile          11
    com.apple.driver.AirPortBrcm43xx          423.91.27
    com.apple.driver.AudioIPCDriver          1.1.6
    com.apple.nvenet          2.0.17
    com.apple.driver.AppleBacklight          170.0.46
    com.apple.kext.AppleSMCLMU          1.5.2d10
    com.apple.driver.SMCMotionSensor          3.0.1d2
    com.apple.driver.AppleIntelMeromProfile          19
    com.apple.driver.AirPortBrcm43224          428.42.4
    com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
    com.apple.driver.AppleLPC          1.5.1
    com.apple.GeForce          6.3.6
    com.apple.filesystems.autofs          2.1.0
    com.apple.driver.AppleUSBTCButtons          201.6
    com.apple.driver.AppleUSBTCKeyEventDriver          201.6
    com.apple.driver.AppleUSBTCKeyboard          201.6
    com.apple.driver.AppleIRController          303.8
    com.apple.driver.AppleUSBCardReader          2.6.1
    com.apple.iokit.SCSITaskUserClient          2.6.8
    com.apple.iokit.IOAHCIBlockStorage          1.6.4
    com.apple.BootCache          31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleUSBHub          4.2.4
    com.apple.driver.AppleFWOHCI          4.7.3
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleAHCIPort          2.1.7
    com.apple.driver.AppleUSBEHCI          4.2.4
    com.apple.driver.AppleUSBOHCI          4.2.0
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleSmartBatteryManager          160.0.0
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleACPIButtons          1.3.6
    com.apple.driver.AppleSMBIOS          1.7
    com.apple.driver.AppleACPIEC          1.3.6
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.12
    com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
    com.apple.iokit.KLog          2.4.5
    com.apple.iokit.IOSurface          74.2
    com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
    com.apple.iokit.IOSerialFamily          10.0.3
    com.apple.driver.AppleHDAHardwareConfigDriver          2.0.5f13
    com.apple.iokit.CHUDKernLib          3
    com.apple.driver.DspFuncLib          2.0.5f13
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.iokit.IOAudioFamily          1.8.3fc2
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.AppleHDAController          2.0.5f13
    com.apple.iokit.IOHDAFamily          2.0.5f13
    com.apple.driver.AppleBacklightExpert          1.0.1
    com.apple.nvidia.nv50hal          6.3.6
    com.apple.iokit.IOFireWireIP          2.0.3
    com.apple.iokit.IO80211Family          320.1
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.driver.NVSMU          2.2.7
    com.apple.driver.AppleSMC          3.1.0d5
    com.apple.driver.IOPlatformPluginFamily          4.7.0a1
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.iokit.AppleProfileFamily          41
    com.apple.NVDAResman          6.3.6
    com.apple.iokit.IONDRVSupport          2.2
    com.apple.iokit.IOGraphicsFamily          2.2
    com.apple.driver.AppleUSBMultitouch          207.7
    com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
    com.apple.iokit.IOBluetoothFamily          2.4.5f3
    com.apple.iokit.IOUSBHIDDriver          4.2.0
    com.apple.iokit.IOUSBMassStorageClass          2.6.7
    com.apple.iokit.IOSCSIBlockCommandsDevice          2.6.8
    com.apple.driver.AppleUSBMergeNub          4.2.4
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6.1
    com.apple.driver.XsanFilter          402.1
    com.apple.iokit.IOAHCISerialATAPI          1.2.6
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
    com.apple.driver.AppleFileSystemDriver          2.0
    com.apple.iokit.IOUSBUserClient          4.2.4
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IOAHCIFamily          2.0.6
    com.apple.iokit.IOUSBFamily          4.2.4
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.6
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.TMSafetyNet          6
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.driver.DiskImages          289.1
    com.apple.iokit.IOStorageFamily          1.6.3
    com.apple.driver.AppleACPIPlatform          1.3.6
    com.apple.iokit.IOPCIFamily          2.6.5
    com.apple.iokit.IOACPIFamily          1.3.0

  • Can't boot after system update: unknown filesystem type

    After running a system update, including updating the kernel, I can't boot to the new kernel.
    On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
    mount: unknown filesystem type 'ext4'
    I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
    Thank goodness I happened to keep a spare kernel laying around in /boot.
    Thanks in advance.
    Last edited by jackrabbit (2012-03-22 23:25:28)

    The OP can read their partition initially though, it's only after udev that they can't.
    Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

  • Can't boot after update, getting "microcode: failed to load" error

    After restarting my computer, it's no longer able to boot, and just prints a continuous stream of errors. The first error it gives is "microcode: failed to load", and I looked it up and found that I should just have to install amd-ucode. Easy enough, except I can't boot. I tried booting into the latest live-usb image, and after connecting to the internet, mounting the partition to /mnt, and running
    # arch-chroot /mnt pacman -S amd-ucode
    I get the following error
    error: amd-ucode: signature from "Allan McRae <[email protected]>" is invalid
    error: failed to commit transaction (invalid or corrupted package (PGP signature))
    Errors occurred, no packages were upgraded.
    I'm not very familiar with how chrooting works, especially not arch-chroot, so I don't trust myself to fix the problem without breaking something. I was thinking of just putting the package on a flashdrive and installing it with
    # arch-chroot /mnt pacman -U amd-ucode-package-name
    Should I do it this way or am I misunderstanding how arch-chroot works?
    By the way, this is an issue with my desktop. startx stopped working on my laptop right before I went to use my desktop and rebooted it, so after this issue is fixed I'll be making another thread about my laptop >_> Any help is much appreciated.

    Ok, so I managed to install amd-ucode with pacstrap. That got rid of the microcode error, but I'm still getting
    /dev/sdc1 contains a filesystem with errors. Forcing check
    And then it just repeats the error message
    [60.50342] ata5.00: failed command: READ FPDMA QUEUED
    [60.51345] ata5.00: cmd 60/<long number that's formatted similarly to a MAC address>/40 tag 0 ncq 131072 in
    [60.51743] res 40/<the same number>/40 Emask 0x10 (ATA bus error)
    [60.62421] ata5.00: status: { DRDY }
    The numbers on the left just keep counting up, but the repeating error message stays mostly the same. What's odd about this error is that the disc it says it has a problem with isn't even the disc with the OS on it. When I have time I'm going to try physically removing /dev/sdc from my computer to see if the error stops.
    Oh and there won't be any thread about my laptop issues. Turns out I filled my whole HDD, which was causing startx to fail.

  • Can't boot after glibc update (even after a fresh netinstall)

    My main system no longer booted after doing a pacman -Syu yesterday, following the instructions at https://www.archlinux.org/news/the-lib- … a-symlink/ .
    I booted a livecd, rsynced my /home to a storage drive and did a netinstall today. The system still doesn't boot.
    The screen goes black after "waiting for udev uevents to be processed" appears, together with expected microcode errors.
    I booted the system with a livecd again and mounted /dev/sda3. /var/log is empty, except for a pacman.log from the install, containing no errors.
    Photo from just before the screen goes blank: https://goput.it/9id.jpg
    inxi -v7 output from sometime before this happened: https://goput.it/rmh.png
    Last edited by ne (2012-07-15 12:43:58)

    Adding nomodeset to the grub kernel line made it boot fine, so I've narrowed it down to a framebuffer issue.

  • Imac won't boot after 10.6.8 update

    Not sure where to start with this...
    Just tried to boot after the latest 10.6.8 update and have the grey screen with the spinning disk.

    I would suggest that you do the following as a start:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    If the drive is OK then download the Mac OS X 10.6.8 Update Combo installer and reinstall the update. See if that resolves your problem.
    If the above does not fix the problem then you will need to reinstall Snow Leopard:
    Reinstall OS X without erasing the drive
    Do the following:
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

  • No BOOT after 10.8.3 UPDATE

    Hi after updating to 10.8.3 i'm stucked in the grey boot screen.
    Booting in verbose mode shows me
    disk0s2 : media is not present
    in single user mode if i launch fsck -yf it shows me:
    Failed to  issue COM RESET succesfully after 3 attempts. Failing..
    disk0s2: no suck device
    update/reload mount for / failed: Device not configured
    The only way to make the system active is to boot with TARGET option and select the disk.then it boots properly..
    any help how to fix that s°*T of update?
    Thank you

    Hold Command and R keys while your Mac is starting to start in Recovery HD. Then, open Disk Utility, select your OS X partition on the sidebar and verify the disk. Is it OK? If not, repair it.
    If it doesn't show any problem, the update damaged the operating system. Close Disk Utility and reinstall OS X. You won't lose anything you had stored before updating.
    Sometimes, problems like this happen after a OS X update, and we don't know exactly their reasons. Maybe a third-party extension, maybe a corrupted OS X package, maybe a hard disk failure. To prevent problems like yours, I recommend to install a maintenance update as OS X 10.8.3 downloading the Combo version from the Apple webpage. This version gives less problems than the version you download from the App Store and it can be used to update all your Macs downloading that update once

  • How long is an 'abnormally long' time to boot after 10.4.8 update?

    How long is too long to wait for my macBook Pro to take to boot up after installing the latest update?
    An hour?
    2 hours?
    A day?
    I installed from Automatic Updates and shutdown rather than restart. Came abck hours later turned on powerer and waited and waited. After about an hour I tunred it off booted from the install CD, ran the disk utility, fixed a few permission and rebooted...
    Should I take it in to the Apple Store tomorrow morning if this continues or reinstall the OS and start over?

    Hello dn:
    As an aside, comparing Windows to OS X is like
    comparing a plow horse ready for the glue factory to
    a thoroughbred race horse. I use both every day and
    have for years, so I have vivid daily comparisons.
    Now then, as I indicated above, you probably caused
    the problem by interrupting the software update
    process. At a guess, you have clobbered directories
    (you, not Apple). The first step would be to run
    repair disk from your software install DVD (boot it,
    holding down the "C" key). Repair disk is found in
    the disk utility. If that works, you should be back
    to the point where you can reinstall the combo
    updater. There is also an excellent third party
    program (mentioned above) called DiskWarrior (pricey
    at about $90, but worth it if it saves the day).
    If none of that works, you probably should do an
    archive and install:
    http://docs.info.apple.com/article.html?artnum=107120
    A good back up/retreat strategy is just good
    computing practice whether or not you are a computing
    professional. There are several approaches. I make
    bootable clones of all my iMacs on an external
    firewire drive using a little program called
    SuperDuper (&28 at www.shirt-pocket.com). The
    bootable clone gives me almost complete protection
    against hardware or software problems.
    By the by, these forums are user-to-user. Everyone
    is a volunteer - not an Apple employee. Apple
    monitors/moderates the forums and provides an
    excellent resource. If you are new to Macs (as your
    post seems to indicate), you should spend some time
    browsing the forums and using the tools available -
    including the excellent library of knowledge base
    articles.
    Barry
    OK, So I'm a cry baby.
    But I do not buy your argument that it was all my fault. After I inrterupted the hour ling gray screen and ran and fixed a few previlige problems and tried again over 2 hour went by with nothing but the gray screen.
    Archive and intall did get me back and running, but by now 4 -5 hours of my life are gone that I want back!
    And the tone on this whole board seems to be we MacBook owners, who unsupectingly trusted Apple and let the Automaitic Software Update have its way with a computer that was functioning just fine, the result of which is a computer that needs to have the OS reinstalled, are at fault for having poor prior knowledge?
    I bring up Microsoft because they are BAD. They have an OS that allows 3rd parties to install code to render your computer useless at best, a robot of evil at worst.
    Yet here we have the Apple, a trusted known entity and the manufacture of not only the hardware but the OS handing us an install that should have just WORKED.
    So al I can think is the Delta install is the culprit, since I had previously been on 10.4.7 and the Archive & Install put in 10.4.6. The Combined installer is ok.
    Again MacBook owners are victimized for keeping current?
    Some one at Apple deserves a dummy slap at least.
    MacBook owners represent the "Switchers". They bought on style and a promis of stability and reliability. Not the allure of becoming UNIX Geeks or even Uber User or browsers of forums. They came from that dull gray world out there where viruse roam but if you let automatic updates run and loaded up with antiv virus and spyware scanners, things pretty much worked.
    I'm not new to mac as I have been usinge them since I shelled out $3,500 for a Mac SE. (Don't laugh). I gave up however being a Uber User and I at least am tenaciouse enought to find this discussion board. I suspect there are going to be a lot of busy Mac "Geniouses" for the next few days as ordinary computer users stream in with MacBooks with gray screens.
    You know Sony support totally *****, but they are rated the best on the PC side for customer satisfaction. Why? You almost never have to seek support from Sony.
    Again I'm just ******** 'casue it happend to me on a new laptop that was bone stock. Its working now so problem solved.

  • Can't Boot After New HD + Time Machine Restore

    So a couple days ago my 27" iMac running Snow Leopard started making some weird noises and stalling out. Annoyed, I talked for a couple hours with apple tech support which eventually lead me to run an Apple Hardware Test. This test returned the error
    "Alert! Apple Hardware Test has detected an error.
    4HDD/11/40000000 SATA(0,0)"
    I scheduled an appointment at the Genius Bar, and they replaced the hard drive.
    After that I got it home and did a System restore from my time machine backup. It finished fine, but when I restarted it got stuck on the grey apple screen with the spinning dial thing.
    I called apple back and they had me do a couple things like repair disk, verify disk, and one person had me reboot into this command line mode and type some stuff in. Nothing worked. After that They had me try to reinstall the OS first from archive, and next by erasing the hard drive and doing it. Both times the install fails with a big yellow exclamation point saying that it couldn't install support files and the OS couldn't be installed.
    Any ideas how to fix this?
    I'm currently trying to restore from my time machine backup again, but I'm not hopeful.

    Here's what I got - apologies for any formatting peculiarities.
    The problem: 10.6.6 mac won't boot after time machine restore to disk.
    Further symptoms: Booting with Command-v shows several errors: usually blued and loginwindow collapse with errors from launchd. Errors will be of the style "dyld: Symbol not found: CSSMOID_APPLE_TP_MACAPPSTORERECEIPT" and other CommerceKit / CommerceCore framework errors.
    A solution: Your Framework Security library may be an older version (possible cause with Time Machine below). The easiest way to fix this is to find another, working 10.6.6 Mac, and update the Security library on the broken machine.
    Identifying if you're affected:
    1) Boot the broken machine into "target" mode - hold "Command-t" during boot until the [Firewire|http://itunesu.utah.edu/terms/images/Firewire_Icon.png] icon appears.
    2) Connect the broken machine to the working 10.6.6 machine with a firewire cable.
    3) On the working machine, the disk of the broken machine should mount.
    4) Open Terminal
    5) Run "ls /Volumes" - the name of disk you mounted should be there (in this example, we'll use "Macintosh HD".)
    6) Typing in the path of the broken machine, run:
    <pre>
    nm /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
    </pre>
    (this does a dump of the library, looking for the version value)
    If this comes back with the value 22457 (or less?), your Mac is not booting because it does not have the updated version of the Security library, which is required in 10.6.6 since Snow Leopard added the Appstore / Commerce framework.
    Fixing if you're affected:
    1) First, make sure the working 10.6.6 Mac has a correct version of the framework:
    <pre>
    nm /System/Library/Frameworks/Security.framework/Versions/A/Security | grep random_fd | cut -d. -f2
    </pre>
    For 10.6.6, this should be at least "22458"
    2) *Be extremely careful at this point* - Make sure on the mounted disk (not the machine you are working on!) run the following
    <pre></pre>
    2a) Make a backup of the broken library
    <pre>
    mkdir /Volumes/Macintosh HD/savedLibrary
    cp /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/savedLibrary
    </pre>
    2b) Copy the working version over the non-working version:
    <pre>
    cp /System/Library/Frameworks/Security.framework/Versions/A/Security /Volumes/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security
    </pre>
    3) Eject the mounted disk from the working Mac, disconnect the firewire cable, and reboot the "broken" Mac. It should come up.
    If it doesn't, you have problem(s) that are probably outside the scope of this. I'd also suggest restoring your original security library that you saved off.
    Suspected cause:
    It appears that Time Machine never recorded the change to the Security library after the update. If the library hadn't changed, the machine should have failed to boot like it did after restore the moment a 10.6.6 update was applied.
    Inspecting the contents of my Time Machine backups before and after updating shows that Time Machine never updated the Security Framework library - why is still not 100% determined, but restoring from it is definitely broken. Combing through the backup databases on my Time Machine disk:
    (I upgraded to 10.6.6 on January 6)
    <pre>
    for name in 2010-12-30-093337 2011*
    do
    echo -n "In backup on ${name}, version of Security library is: "
    nm "${name}/Macintosh HD/System/Library/Frameworks/Security.framework/Versions/A/Security" | grep random_fd | cut -d. -f2
    done
    </pre>
    In backup on 2010-12-30-093337, version of Security library is: 22457
    In backup on 2011-01-04-100707, version of Security library is: 22457
    In backup on 2011-01-05-082402, version of Security library is: 22457
    In backup on 2011-01-06-092846, version of Security library is: 22457
    In backup on 2011-01-07-094827, version of Security library is: 22457
    In backup on 2011-01-10-093559, version of Security library is: 22457
    In backup on 2011-01-11-110542, version of Security library is: 22457
    In backup on 2011-01-12-094137, version of Security library is: 22457
    In backup on 2011-01-13-103238, version of Security library is: 22457
    In backup on 2011-01-14-113145, version of Security library is: 22457
    In backup on 2011-01-18-112856, version of Security library is: 22457
    In backup on 2011-01-20-114953, version of Security library is: 22457
    In backup on 2011-01-21-103642, version of Security library is: 22457
    In backup on 2011-01-24-102321, version of Security library is: 22457
    In backup on 2011-01-27-002508, version of Security library is: 22457
    In backup on 2011-01-27-011931, version of Security library is: 22457
    In backup on 2011-01-27-104406, version of Security library is: 22457
    In backup on 2011-01-27-114322, version of Security library is: 22457
    In backup on 2011-01-27-123928, version of Security library is: 22457
    In backup on 2011-01-27-134523, version of Security library is: 22457

  • HT6114 MAC Air slow to boot after 10.9.2 update.

    I have a 2011 MAC Air. After the 10.9.2 upgrade my laptop takes about 20 minutes to boot from power off. Once started it works fine, it is just extremely slow to boot. Prior to the update I could boot in about 10 seconds. Any thoughts how to resolve this issue?

    Try these in order testing your system after each to see if it's back to normal:
    1. a. Resetting your Mac's PRAM and NVRAM
        b. Intel-based Macs: Resetting the System Management Controller (SMC)
    2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
         Boot to the Recovery HD: Restart the computer and after the chime press and hold down the
         COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the
         computer and after the chime press and hold down the OPTION key until the boot manager
         screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
         Reinstall the 10.9.2 update: OS X Mavericks 10.9.2 Update (Combo).
    4. Reinstall Lion/Mountain Lion, Mavericks: Reboot from the Recovery HD. Select Reinstall Lion/Mountain Lion, Mavericks from the Utilities menu, and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Reinstall the 10.9.2 update: OS X Mavericks 10.9.2 Update (Combo).

  • Mac Pro new update won't boot after 10.8.2 Update 1.0

    It just stays on the apple screen during boot after entering pw for account.
    Its been over 5 min that it just stays in that screen. Anyone else seeing this after doing 10.8.2 Supplemental Update 1.0?

    Reinstalling Lion/Mountain Lion Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

Maybe you are looking for

  • How to change the text mail of Workflow Notification?

    Hi all, I would like to change the text mail of workflow notification. I took a look at the Help Sap and saw how to customize the text mail notification. Unfortunately, I could not found the text for workflow Notification at “notificationTexts_<langu

  • My macbook pro went from startup screen to grey vertical stripes

    my macbook pro went from startup screen to grey vertical stripes with a bit of flashing.  Force quit twice and it is still doing it.  Had a bit of problem last time I started it with flashing screen, but it settled.  After leaving it on screen went b

  • I mix a sound with another one, how can I make the background sound larger

    in other words how to adjust the volume of the sound? one method is just time a number to every byte, I found if so the sound lose its original sound . any idea?

  • System Preferences UI Bug

    Before any groups have been added to a fresh system, there is no "Groups" group in the left-hand side column in the "Accounts" preferences area. When a group is added, the "Groups" group is displayed with the newly created group underneath it. When t

  • Unlimited plan changed without authorization

    >> Subject edited for brevity and duplicate post removed to comply with the Verizon Wireless Terms of Service   See My Unlimited Plan changed without my authorization! << Message was edited by: Verizon Moderator