Safe Boot issue..?

Question

Did a Safe Boot following these directions exactly:Shut down your Mac and wait 10 seconds.Press the power button.Immediately after you hear the startup tone, hold down the Shift key.You should press the Shift key as soon as possible after you hear the startup tone, but not before.Release the Shift key when you see the gray Apple logo and progress indicator (spinning gear).And this happened:1- An apple then gray circle with a slash (or maybe other way around), 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. ..  Is that safe boot, or a problem..?2- Did a safe boot with shift, command and V keys...  it went through a whole lot of terminal like language, then on into the finder.  when i rebooted it gives some more terminal like language and then reboots as usual.  Is that Safe Boot, and if so what is 1, above..?3- In both cases my startup items started up...  Is that supposed to happen..?2012 cMBP os x 10.8.5, 16 gig ram 512 gig ssd

Carolyn Samit · Answer

1-   That is referred to as a kernel panic.Help here &gt;  OS X: About kernel panics

Phil-CB · Answer

Hi John,what you describe in 1 is known as a "kernel panic". If this happens again on your system, I would suggest that you have a look to Apple document PH11045.The process you describe (holding shift during boot until you see a grey Apple logo, with a progress bar) is the correct one for Safe Boot (cf HT1564). You can check if Safe Boot is successful on the login window, when you should see a red "Safe Mode" in the top right corner.The process you describe in 2 is known as Verbose mode (booting OS X with Command - V). This will show you the os kernel loading steps instead of the usual Apple logo with spinning gear (HT1492).3. In fact, yes. If you wish to "mute" your login items, you should press SHIFT just after you entered your username and password on the login window, and keep SHIFT pressed during your user session login. This is knows as Safe Login.Best regards,Philippe

John Fridinger · Answer

This is only happening when I do a safe boot, which I originally felt called to do for something unrelated...  Thanks for your answers but all seems to be totally fine as always, except when i did and still do the safe boot. then either number 1 above happens, or number 2 with the verbose keys added...  And not understanding re log in, I don&#x27;t log out or in, just startup, being the only user...  Do startup items startup if safe boot happens...? if not then number two as described is in fact not a safe boot..?And number one above, i&#x27;m guessing it is a kernal panic maybe from what Carolyn pointed me to, but why just in safe boot..?  I&#x27;m totally perfect for a year, since new, all upgrades, etc., lots of complex use, software, and still seem totally fine, all rebooting, everything, except now trying to do a safe boot, something I&#x27;ve never been moved to do before now, and all this arrives...   yikes..?AND now particularly, when I&#x27;m planning to go to Mavericks, soon as 10.9.1 arrives, and concrned how this might affect that..?

Baby-Boomer-USofA · Answer

KP are usually caused by hardware problems.  From your posting, you are not experiencing any.  Anywho, post the KP log.  There are knowledgeable users here who can read the log.  I am NOT one of them.OS X: About kernel panics User Tip:  Kernel Panics? Don&#x27;t panic too! How to troubleshoot a kernel panichttp://support.apple.com/kb/PH11342 OS X Mountain Lion: Use Apple Hardware Test

John Fridinger · Answer

Here is a copy of the report that  comes up when I say yes to making a report, hoping it is the same as KP log you mention, otherwise how does one get a KP log..?Interval Since Last Panic Report:  1002177 secPanics Since Last Report:          9Anonymous UUID:                    C3829C5E-A45F-BE30-41FB-E5C42AE717DEFri Nov 22 17:28:24 2013panic(cpu 3 caller 0xffffff8000555ef5): "Process 1 exec of /sbin/launchd failed, errno 2"@/SourceCache/xnu/xnu-2050.7.9/bsd/kern/kern_exec.c:3560Backtrace (CPU 3), Frame : Return Address0xffffff81b7113e10 : 0xffffff800021d5f6 0xffffff81b7113e80 : 0xffffff8000555ef5 0xffffff81b7113ef0 : 0xffffff80005390f7 0xffffff81b7113f10 : 0xffffff8000568ee1 0xffffff81b7113f50 : 0xffffff800021b6b1 0xffffff81b7113f90 : 0xffffff80002b8123 0xffffff81b7113fb0 : 0xffffff80002ce47c BSD process name corresponding to current thread: initBoot args: -xMac OS version:Not yet setKernel version:Darwin Kernel Version 12.0.0: Sun Jun 24 23:00:16 PDT 2012; root:xnu-2050.7.9~1/RELEASE_X86_64Kernel UUID: 8D5F8EF3-9D12-384B-8070-EF2A49C45D24System model name: MacBookPro9,1 (Mac-4B7AC7E43945597E)System uptime in nanoseconds: 917658094last loaded kext at 648727133: com.apple.driver.AppleUSBMergeNub          5.1.5 (addr 0xffffff7f80b04000, size 28672)loaded kexts:com.apple.driver.AppleFileSystemDriver          3.0.1com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1com.apple.BootCache          34com.apple.iokit.SCSITaskUserClient          3.5.1com.apple.driver.XsanFilter          404com.apple.iokit.IOAHCIBlockStorage          2.2.0com.apple.driver.AppleSDXC          1.2.2com.apple.iokit.AppleBCM5701Ethernet          3.2.5b3com.apple.driver.AppleUSBHub          5.1.6com.apple.driver.AirPort.Brcm4331          600.15.20com.apple.driver.AppleFWOHCI          4.9.5com.apple.driver.AppleAHCIPort          2.4.0com.apple.driver.AppleUSBEHCI          5.1.5com.apple.driver.AppleUSBXHCI          1.1.0com.apple.driver.AppleEFINVRAM          1.6.1com.apple.driver.AppleSmartBatteryManager          161.0.0com.apple.driver.AppleRTC          1.5com.apple.driver.AppleACPIButtons          1.6com.apple.driver.AppleHPET          1.7com.apple.driver.AppleSMBIOS          1.9com.apple.driver.AppleACPIEC          1.6com.apple.driver.AppleAPIC          1.6com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0com.apple.nke.applicationfirewall          4.0.39com.apple.security.quarantine          2com.apple.driver.AppleIntelCPUPowerManagement          196.0.0com.apple.driver.AppleUSBMergeNub          5.1.5com.apple.driver.AppleUSBComposite          5.0.0com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.1com.apple.iokit.IOBDStorageFamily          1.7com.apple.iokit.IODVDStorageFamily          1.7.1com.apple.iokit.IOCDStorageFamily          1.7.1com.apple.driver.AppleThunderboltNHI          1.6.0com.apple.iokit.IOThunderboltFamily          2.0.3com.apple.iokit.IOAHCISerialATAPI          2.5.0com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.1com.apple.iokit.IOEthernetAVBController          1.0.2b1com.apple.iokit.IO80211Family          500.15com.apple.iokit.IONetworkingFamily          3.0com.apple.iokit.IOFireWireFamily          4.5.5com.apple.iokit.IOUSBUserClient          5.0.0com.apple.iokit.IOAHCIFamily          2.2.0com.apple.iokit.IOUSBFamily          5.1.6com.apple.driver.AppleEFIRuntime          1.6.1com.apple.iokit.IOHIDFamily          1.8.0com.apple.iokit.IOSMBusFamily          1.1com.apple.security.sandbox          220com.apple.kext.AppleMatch          1.0.0d1com.apple.security.TMSafetyNet          7com.apple.driver.DiskImages          344com.apple.iokit.IOStorageFamily          1.8com.apple.driver.AppleKeyStore          28.18com.apple.driver.AppleACPIPlatform          1.6com.apple.iokit.IOPCIFamily          2.7com.apple.iokit.IOACPIFamily          1.4com.apple.kec.corecrypto          1.0Model: MacBookPro9,1, BootROM MBP91.00D3.B08, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f175Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MBGraphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MBMemory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136AirPort: 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 portsNetwork Service: Wi-Fi, AirPort, en1Serial ATA Device: SAMSUNG SSD 830 Series, 512.11 GBSerial ATA Device: MATSHITADVD-R   UJ-8A8USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0x1d180000 / 3USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 6USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 5USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0252, 0x1d183000 / 4

John Fridinger · Answer

Solution to problem found:Got to looking around, and found this: https://discussions.apple.com/thread/5425709?start&#x3D;0&amp;tstart&#x3D;0The 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&#x27;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&#x27;t recognize mountain lion, it thought i was running something prior to 10.5.x, so it wouldn&#x27;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!