MBPr frozen after beta 6

The past few seeds all caused my MBPr (early 2012) to freeze at the black and white progress bar around 50-66%. After waiting each time about an hour, I forced it to reboot and it just went in, got the recovered from a crash screen, submitted logs to Apple and went on my merry way. Now last night it is refusing to get in. I tried holding Shift during boot, tried single user mode, but I really didn't know what I look for in why this is crashing/freezing. I see others having similar issues too but couldn't find any solutions so I apologise in advance if this is a duplicate.


Verbose boot log:


AirPort: RSN handshake completed on en0
Unexpected payload found for message 9, dataLen 0
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
VBoxFltDrv: version 4.3.28 r100309
Can't get kextd port.
VBoxFltDrv: version 4.3.28 r100309
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
AppleUSBMultitouchDriver::checkStatus - received Status Paclet, Payload 2: device was reinitialized
Can't get kextd port.
Can't get kextd port.
IOBluetoothUSBDFU::probe
IOBluetoothUSBDFU::probe ProductID - 0x8296 FirmwareVersion - 0x0151
Can't get kextd port.
Can't get kextd port.
Can't get kextd port.
**** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x2008 ****
**** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0x2000 ****
pci pause: SDXC
en1: promiscuous mode enable succeeded
en2: promiscuous mode enable succeeded
IO80211AWDPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from SUSPENDED to AUTO
IO80211AWDPeerManager::setAwdlAutoMode Resuming AWDL
IO80211AWDPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from AUTO to SUSPENDED
IO80211AWDPeerManager::setAwdlSuspendedMode() Suspending AWDL, enterQuietMode(true)
IO80211AWDPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from SUSPENDED to AUTO
IO80211AWDPeerManager::setAwdlAutoMode Resuming AWDL
Can't get kextd port.

Replies

I don't know if it will work, but it might help to disable SIP (a.k.a. rootless) from Internet Recovery Mode with the following command:


csrutil disable


Then try booting normally again.

had to run ./usr/bin/csrutil but got operation not permitted.

hmm.... maybe its time to go to timemachine and go back in time....and since i cannot execute it in recovery mode, i assume the terminal from within internet recovery, and since i cannot run in SUM...

but, i was able to rename NVDAStartup to kext.old so in theory it shouldnt be loading, right?


what are those watchdogd[pid] that says cannot connec6t, since it is constnatly respawning, i wonder if it is looping due to the respawn?

Okay.. I successfuly restore my MBPr timemachine. I am where I was before I installed the update 6 seed. I removed the vbox now fully from the script. Anything else you can think of I should do prior to updating the seed again? Should I just wait until the 7 seed comes out? I ran as root the disktuil cs list and i got no corestorage found. I like to get command r to do El Capitan, not Lion, so it doesnt do internet recovery. How can I accomplis this? At least this way, I can get that resolved, and do a full backup again incase it does fail I can easily go back and wait it out.


Also, the main reason as to why I updated and rebooted as mounting issues. Right now it says my last Time Machine update failed. It doesn't mount my flash drive, my external hard drive, nor my SD Card. I ran diagnostics prior to doing anything and that old-school carbon looking interface claimed I failed 4SNS/1/40000001:DOR-0.002. That can be DOR or D0R.. so not toally sure since the font was awful that distinguishing the letter/numeral.

A little bit of googling reveals that 4SNS/1/40000001:IDOR-0.002 - thats idor - is a sensor fault, but possibly not a serious one as someone mentioned that it went away after plugging their MBP into a power supply and running the full test again.


I can't account for the mounting issues.


What RecoveryHD volume(s) appear when you boot holding alt? If you don't see 10.11 RecoveryHD then it may be that it isn't mounting either. Run the following command to see if it is available on your drive:

diskutil list disk0


As to whether to try for 6 now or wait for 7, it's a gamble for the reasons you are now as aware of as I am. Up to you... I'd give you a 2/3 chance of a successful update if I had to guess.

Just see

0: GUID_partition_scheme disk0

1: EFI EFI disk0s1

2: Apple_HFS Macintosh HD disk0s2


So all I see if Macintosh HD when I press option. Are those tools safe that restore the parition?

Yep, you don't have a RecoveryHD partition there at all, which is relatively unusual.


You could try downloading the 10.11 Developer Preview (a.k.a. Beta 1) from the Purchases tab in your App Store and see if it is happy to reinstall over itself - that should give you your Recovery Mode back. You'll have to update through the betas again of course (or cross your fingers for beta 7 being a combo).

I might have to do that. I threw the dice, and well, it froze.

But when I did the verbose boot, right before the last kext message, I was able to press enter a few times, however, when the last kext came up, I was unable to press anything, so I guess it really did ***** something up. Now vbox is definitely out the question what else can possibly be causing it? It seems I am at square one again :-(

Aug 10 22:37:59 apollo kernel[0]: en1: promiscuous mode enable succeeded
Aug 10 22:37:59 apollo kernel[0]: IO80211AWDLPeerManager::setAwdlOperatingMode Setting the AWDL operation mode from SUSPENDED to AUTO
Aug 10 22:37:59 apollo UserEventAgent[47]: tcp_connection_destination_perform_socket_connect 1 connectx to 23.203.18.208:80@en0 failed: [64] Host is down
Aug 10 22:37:59 apollo UserEventAgent[47]: Captive: CNPluginHandler en0: Authenticated
Aug 10 22:37:59 apollo kernel[0]: IO80211AWDLPeerManager::setAwdlAutoMode Resuming AWDL
Aug 10 22:38:29 apollo warmd[68]: [warmctl_evt_timer_bc_activation_timeout:285] BC activation bcstop timer fired!
Aug 10 22:39:00 apollo apsd[87]: Failed to send activation record to service com.apple.ManagedClient.enroll
Aug 10 22:39:09 apollo WindowServer[195]: Server is starting up
Aug 10 22:39:14 apollo watchdogd[192]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
Aug 10 22:39:14 apollo spindump[196]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Aug 10 22:39:14 apollo spindump[196]: Untrusted apps are not allowed to connect to Window Server before login.
Aug 10 22:39:14 apollo spindump[196]: Set a breakpoint at CGSLogError to catch errors as they are logged.
Aug 10 22:39:14 apollo spindump[196]: On-demand launch of the Window Server is allowed for root user only.
Aug 10 22:39:14 apollo spindump[196]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Aug 10 22:39:14 apollo spindump[196]: On-demand launch of the Window Server is allowed for root user only.
Aug 10 22:39:14 apollo spindump[196]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Aug 10 22:39:14 apollo spindump[196]: This user is not allowed access to the window system right now.
Aug 10 22:39:16 apollo spindump[196]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-08-10-223916_apollo.userspace_watchdog_timeout.spin
Aug 10 22:39:16 apollo watchdogd[192]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-08-10-223916_apollo.userspace_watchdog_timeout.spin)
Aug 10 22:39:39 apollo watchdogd[192]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
Aug 10 22:39:41 apollo spindump[196]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-08-10-223941_apollo.userspace_watchdog_timeout.spin
Aug 10 22:39:41 apollo watchdogd[192]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-08-10-223941_apollo.userspace_watchdog_timeout.spin)
Aug 10 22:40:04 apollo watchdogd[192]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive
Aug 10 22:40:06 apollo spindump[196]: Saved userspace_watchdog_timeout.spin report for WindowServer version ??? (???) to /Library/Logs/DiagnosticReports/WindowServer_2015-08-10-224006_apollo.userspace_watchdog_timeout.spin
Aug 10 22:40:06 apollo watchdogd[192]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - spindump gathered for (com.apple.WindowServer) at (/Library/Logs/DiagnosticReports/WindowServer_2015-08-10-224006_apollo.userspace_watchdog_timeout.spin)
Aug 10 22:40:09 apollo WindowServer[195]: Set a breakpoint at CGSLogError to catch errors as they are logged.
Aug 10 22:40:09 apollo WindowServer[195]: IOKitWaitQuiet: (iokit/common) I/O Timeout
Aug 10 22:40:09 apollo WindowServer[195]: Session 257 retained (2 references)
Aug 10 22:40:09 apollo WindowServer[195]: Session 257 released (1 references)
Aug 10 22:40:09 apollo WindowServer[195]: Session 257 retained (2 references)
Aug 10 22:40:09 apollo WindowServer[195]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -AMBDuser
Aug 10 22:40:09 apollo WindowServer[195]: init_page_flip: page flip mode is on
Aug 10 22:40:09 apollo kernel[0]: Can't get kextd port.


Not as big as last time, but this is the log I received this time. Not too suire but seems different sort of errors this time.

Seemingly, yes. There's evidently a kext trying to load but which one isn't evident from the bootlog - and it's not one we know about yet... It may be worth looking through your Applications folder and thinking which of them are likely to need kexts to function.


I'm hoping that the next beta will be a combo so that restoring a system from a point such as yours isn't quite such a chore...

Though that might have been from the single user mode, this might been from before it died and a see a lot of errors listed.

Aug 10 22:37:06 apollo UserEventAgent[47]: Captive: en0: Probing 'weinet-5G'
Aug 10 22:37:07 apollo kernel[0]: Can't get kextd port.
Aug 10 22:37:08 --- last message repeated 4 times ---
Aug 10 22:37:08 apollo kernel[0]: IOBluetoothUSBDFU::probe
Aug 10 22:37:08 apollo kernel[0]: IOBluetoothUSBDFU::probe ProductID - 0x8286 FirmwareVersion - 0x0151
Aug 10 22:37:08 apollo kernel[0]: Can't get kextd port.
Aug 10 22:37:08 --- last message repeated 2 times ---
Aug 10 22:37:08 apollo kernel[0]: **** [IOBluetoothHostControllerUSBTransport][start] -- completed -- result = TRUE -- 0x5000 ****
Aug 10 22:37:08 apollo kernel[0]: **** [BroadcomBluetoothHostControllerUSBTransport][start] -- Completed (matched on Device) -- 0x5000 ****
Aug 10 22:37:08 apollo kernel[0]: Can't get kextd port.
Aug 10 22:37:08 apollo kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
Aug 10 22:37:08 apollo kernel[0]: Can't get kextd port.
Aug 10 22:37:08 apollo hidd[109]: [HID] [MT] MTSimpleHIDManager::deviceDidBootload device bootloaded
Aug 10 22:37:09 apollo apsd[87]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Aug 10 22:37:10 apollo mtmfs[82]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:10 apollo mtmfs[82]: Metadata.framework [Error]: mdsFetchFilterRulesAndProbePoints failed: (268435459) (ipc/send) invalid destination port
Aug 10 22:37:10 apollo sandboxd[141]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:10 apollo sandboxd[141]: Metadata.framework [Error]: _MDAccessCopyClientPort failed retrying
Aug 10 22:37:17 apollo networkd[176]: -[NETProxyLookup url] invalid URL scheme '5223'
Aug 10 22:37:20 apollo mtmfs[82]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:20 apollo mtmfs[82]: Metadata.framework [Error]: mdsCopyStoreInformation failed: (268435459) (ipc/send) invalid destination port
Aug 10 22:37:20 apollo sandboxd[141]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:20 apollo sandboxd[141]: Metadata.framework [Error]: _MDAccessCopyClientPort failed retrying
Aug 10 22:37:21 apollo kernel[0]: pci pause: SDXC
Aug 10 22:37:30 apollo mtmfs[82]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:30 apollo mtmfs[82]: Metadata.framework [Error]: mdsCopyStoreAttributes failed: (268435459) (ipc/send) invalid destination port
Aug 10 22:37:30 apollo sandboxd[141]: Metadata.framework [Error]: client check-in failed: (268451843) (ipc/rcv) timed out
Aug 10 22:37:30 apollo sandboxd[141]: Metadata.framework [Error]: _MDAccessCopyClientPort failed retrying
Aug 10 22:37:40 apollo mtmfs[82]: Metadata.framework [Error]: client check-in failed: (268435460) (ipc/send) timed out
Aug 10 22:37:40 apollo mtmfs[82]: Metadata.framework [Error]: couldn't get the client port
Aug 10 22:37:40 apollo sandboxd[141]: Metadata.framework [Error]: client check-in failed: (268435460) (ipc/send) timed out
Aug 10 22:37:40 apollo sandboxd[141]: Metadata.framework [Error]: couldn't get the client port
Aug 10 22:37:40 apollo sandboxd[141]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
Aug 10 22:37:46 apollo UserEventAgent[47]: Captive: [CaptiveHandleRedirect:1659] Timed out on en0 (weinet-5G), assuming online
Aug 10 22:37:59 apollo configd[57]: timed out waiting for IOKit to quiesce
Aug 10 22:37:59 apollo configd[57]: Busy services :
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1 [2, 67553 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert [2, 64815 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/CPU0@0 [1, 59532 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU [1, 59506 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/X86PlatformPlugin [!registered, !matched, 1, 59328 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0 [1, 64767 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [3, 64749 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/MCHC@0 [1, 59508 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P2@1 [1, 59518 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P2@1/IOPP [1, 59513 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P2@1/IOPP/GFX0@0 [1, 59513 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/P0P2@1/IOPP/GFX0@0/NVDAgl [!matched, 1, 59476 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2 [1, 59515 ms]
Aug 10 22:37:59 apollo configd[57]:   MacBookPro10,1/IOResources [1, 64587 ms]

Yes, there do seem to be some differences, but that's not so unusual. The relevant entries are those beginning kernel[0] as it is this process crashing that is causing the boot to fail. Also nothing is named in the log that isn't related to Apple software, so it doesn't yield any further clues.

Same story as above.

ah well, i guess i will restore the timemachine. and maybe reinstall 10.11 from the appstore and hope it gets better from there? it is very odd that it failed again... so frustrating. since you said you had been helping others, have they been solved? are you seeing more reports of this elsewhere?

About 70% have had the issue resolved after removing the kexts known to cause the hang. About 30%, like you, don't have an cause I can identify and the hope is that the next beta will help. If it doesn't, then the only way to continue with the beta might be a clean install followed by restoring just user data (documents etc.) from a backup. I'd recommend this anyway, if it's viable for people, because a clean install is almost invariably a smoother ride.

I installed an app that got rid of rootless that wasnt nvram as well. My boss used the same tool and he is on the latest dev seed, plus he has little snitch as well, but never had vbox.


You think I should install over it from AppStore now? Would that at least give me the parition again?

I recently replaced the SSD drive but that was veyr recent and i did have hanging issues with the previous two seeds, yet vbosx was on both and after a cold reboot it came right up, this was the only time it didnt.


If I do a clean install, how can I get just the user data (and apps) back from time machine so it wont overwrite the OS? Would all of my activated software come back too (Office, Adobe Suite, etc)