Safe boot issue..?

Discussion in 'OS X Mavericks (10.9)' started by John Fridinger, Nov 22, 2013.

  1. John Fridinger macrumors newbie

    Joined:
    Jul 25, 2012
    #1
    I'm planning to go to Mavericks soon as 10.9.1 arrives, and this turns up...
    I did a safe boot for the first time ever, following Apple's directions exactly, many times, and this happens, either:

    1- Shift key pressed after gong- get a gray circle with a slash, then a little bit of a terminal like language, white letters on black, then a gray screen with several languages saying i restarted because i had a problem, hit the shift key and it goes into the finder and asks if I want to report a problem. .. there is an apple or two that comes up in the process as well, hard to get it all, goes pretty fast... There seems to be a problem..?!

    Or- 2- A safe boot with shift, command and V keys, i.e., verbose... it goes through a whole lot of terminal like language, then shifts straight on into the finder. when I shutdown/reboot again it gives some more terminal like language and then reboots as usual. Is this Safe Boot and is it working, and if so what is happening with 1, above..?

    3- And, in both cases my startup items still start up, is that supposed to happen in safe mode..?

    I'm totally perfect for a year, since new, all upgrades, etc., lots of complex use, software, and all still seems totally fine every way, all rebooting, everything even now, except that now in this first try at a safe boot this occures, something I've never been moved to do before... yikes..?

    AND now particularly, when I'm planning to go to Mavericks, and concerned how this might affect that..?

    2012 cMBP os x 10.8.5, 16 gig ram 512 gig ssd

    ----------

    Hoping someone who understands such things is looking in here is a copy of the report that comes up when I say yes to making a report, wondering if it is the same as a KP log, or, how does one get a KP log..?

    ---

    Interval Since Last Panic Report: 1002177 sec
    Panics Since Last Report: 9
    Anonymous UUID: C3829C5E-A45F-BE30-41FB-E5C42AE717DE


    Fri Nov 22 17:28:24 2013
    panic(cpu 3 caller 0xffffff8000555ef5): "Process 1 exec of /sbin/launchd failed, errno 2"@/SourceCache/xnu/xnu-2050.7.9/bsd/kern/kern_exec.c:3560
    Backtrace (CPU 3), Frame : Return Address
    0xffffff81b7113e10 : 0xffffff800021d5f6
    0xffffff81b7113e80 : 0xffffff8000555ef5
    0xffffff81b7113ef0 : 0xffffff80005390f7
    0xffffff81b7113f10 : 0xffffff8000568ee1
    0xffffff81b7113f50 : 0xffffff800021b6b1
    0xffffff81b7113f90 : 0xffffff80002b8123
    0xffffff81b7113fb0 : 0xffffff80002ce47c


    BSD process name corresponding to current thread: init
    Boot args: -x


    Mac OS version:
    Not yet set


    Kernel version:
    Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64
    Kernel UUID: 8D5F8EF3-9D12-384B-8070-EF2A49C45D24
    System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)


    System uptime in nanoseconds: 917658094
    last loaded kext at 648727133: com.apple.driver.AppleUSBMergeNub 5.1.5 (addr 0xffffff7f80b04000, size 28672)
    loaded kexts:
    com.apple.driver.AppleFileSystemDriver 3.0.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.BootCache 34
    com.apple.iokit.SCSITaskUserClient 3.5.1
    com.apple.driver.XsanFilter 404
    com.apple.iokit.IOAHCIBlockStorage 2.2.0
    com.apple.driver.AppleSDXC 1.2.2
    com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3
    com.apple.driver.AppleUSBHub 5.1.6
    com.apple.driver.AirPort.Brcm4331 600.15.20
    com.apple.driver.AppleFWOHCI 4.9.5
    com.apple.driver.AppleAHCIPort 2.4.0
    com.apple.driver.AppleUSBEHCI 5.1.5
    com.apple.driver.AppleUSBXHCI 1.1.0
    com.apple.driver.AppleEFINVRAM 1.6.1
    com.apple.driver.AppleSmartBatteryManager 161.0.0
    com.apple.driver.AppleRTC 1.5
    com.apple.driver.AppleACPIButtons 1.6
    com.apple.driver.AppleHPET 1.7
    com.apple.driver.AppleSMBIOS 1.9
    com.apple.driver.AppleACPIEC 1.6
    com.apple.driver.AppleAPIC 1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
    com.apple.nke.applicationfirewall 4.0.39
    com.apple.security.quarantine 2
    com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
    com.apple.driver.AppleUSBMergeNub 5.1.5
    com.apple.driver.AppleUSBComposite 5.0.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.5.1
    com.apple.iokit.IOBDStorageFamily 1.7
    com.apple.iokit.IODVDStorageFamily 1.7.1
    com.apple.iokit.IOCDStorageFamily 1.7.1
    com.apple.driver.AppleThunderboltNHI 1.6.0
    com.apple.iokit.IOThunderboltFamily 2.0.3
    com.apple.iokit.IOAHCISerialATAPI 2.5.0
    com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
    com.apple.iokit.IOEthernetAVBController 1.0.2b1
    com.apple.iokit.IO80211Family 500.15
    com.apple.iokit.IONetworkingFamily 3.0
    com.apple.iokit.IOFireWireFamily 4.5.5
    com.apple.iokit.IOUSBUserClient 5.0.0
    com.apple.iokit.IOAHCIFamily 2.2.0
    com.apple.iokit.IOUSBFamily 5.1.6
    com.apple.driver.AppleEFIRuntime 1.6.1
    com.apple.iokit.IOHIDFamily 1.8.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.security.sandbox 220
    com.apple.kext.AppleMatch 1.0.0d1
    com.apple.security.TMSafetyNet 7
    com.apple.driver.DiskImages 344
    com.apple.iokit.IOStorageFamily 1.8
    com.apple.driver.AppleKeyStore 28.18
    com.apple.driver.AppleACPIPlatform 1.6
    com.apple.iokit.IOPCIFamily 2.7
    com.apple.iokit.IOACPIFamily 1.4
    com.apple.kec.corecrypto 1.0
    Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f175
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.17)
    Bluetooth: Version 4.1.7f2 12718, 3 service, 21 devices, 3 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    Serial ATA Device: SAMSUNG SSD 830 Series, 512.11 GB
    Serial ATA Device: MATSHITADVD-R UJ-8A8
    USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3
    USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0x1d180000 / 3
    USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 6
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9
    USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 4
     
  2. John Fridinger thread starter macrumors newbie

    Joined:
    Jul 25, 2012
    #2
    Solution to problem found:

    Got to looking around, and found this: https://discussions.apple.com/thread/5425709?start=0&tstart=0

    The gist is this:

    The OS X 10.8.5 update, at least for a lot of folks, made the mach_kernel visible and relocated it to the Documents folder. It needs to be in the root folder, must be there same folder as system and applications, and it is usually invisible there.

    I remembered finding it in the Documents folder and tossing it in the trash. Fortunately I hadn't emptied the trash yet. I simply moved it to the root folder, rebooted as added insurance repaired permissions, rebooted again, and now all is well, perfect safe boot and everything. I never did a safe boot before so had no idea it loped the way it does. Pretty cool…

    As an added bonus, what got me to trying a safe boot was that the latest Office update wouldn't recognize mountain lion, it thought i was running something prior to 10.5.x, so it wouldn't install. It has now installed perfectly.

    Additionally, per the above link/forum thread, I hid the mach_kernel again, with this command in the terminal- sudo chflags hidden /mach_kernel which also worked perfectly.


    All is well, yea!
     

Share This Page