Currently Being ModeratedSep 26, 2012 9:27 AM (in response to jacooper11)
I had the same issue. Place the retina to sleep and closed the lid. Came back next morning to find the Retina fans running. Opened it up to a black screen and unresponsive. Had to reboot it holding the power button down. The Retina had been running all night with console messages every 2-5 minutes stating:
mdworker: Unable to talk to lsboxd
sandboxd: () mdworker(18520) deny mach-lookup com.apple.ls.boxd
kernel: Sandbox: sandboxd(20128) deny mach-lookup com.apple.coresymbolicationd
Currently Being ModeratedSep 26, 2012 11:25 AM (in response to Pedro Gelabert)
I'm seeing the same issue and I think it started after the 10.8.2 update on my 2012 MBP (not retina). I usually do a command-option-eject to put the machine to sleep when I leave work at night but the last three mornings when I get back to work the MBP will not wake up and I have to hold the power button to force it off. The console is full of the following messages, even during the time when it should have been sleeping:
Sep 25 00:18:55 kernel: Sandbox: sandboxd(3819) deny mach-lookup com.apple.coresymbolicationd
Sep 25 00:20:56 mdworker: Unable to talk to lsboxd
Sep 25 00:20:56 mdworker: Unable to talk to lsboxd
Sep 25 00:20:56 kernel: Sandbox: sandboxd(3824) deny mach-lookup com.apple.coresymbolicationd
Sep 25 00:20:56 sandboxd (): mdworker(3822) deny mach-lookup com.apple.ls.boxd
Sep 25 00:20:56 sandboxd (): mdworker(3823) deny mach-lookup com.apple.ls.boxd
Also, when re-start it indexes my external Time Machine hard drive for what seems like hours - never used to do that.
Currently Being ModeratedSep 26, 2012 1:58 PM (in response to jacooper11)
I was also seeing the those messages in the console after installing 10.8.2. Following the advice at the end of this thread, I did a "Safe Boot" (hold <shift> while booting), restarted normally, and those messages went away. Worth a shot. Good luck!
Message was edited by: merkin3k
Currently Being ModeratedSep 26, 2012 8:16 PM (in response to merkin3k)
Well, I am not able to boot in safe mode. I reset PRAM, SMC, and turned off File Vault. Yet, when booting into safe mode, the progress bar reaches 1/4 of the way and stay there for hours...
Currently Being ModeratedSep 27, 2012 6:14 AM (in response to jacooper11)
When I got to work this morning, my MBP was not locked up and came to life as soon as I opened the lid. I also checked the system.log and there was no activity from the time I did the command-option-eject last night until I opened the lid this morning - just like it should be.
I'm afraid I wasn't very scientific on my troubleshooting. I did all of the following based on different discussions:
1. set hibernate mode to 0 (sudo pmset -a hibernatemode 0)
2. shut off WiFi (I've got a direct wired connection)
3. turned off "Wake for network access"
4. removed /System/Library/LaunchAgents/com.apple.afpstat.plist
5. removed directory /Library/Caches/com.apple.coresymbolicationd
6. booted into safe mode, then re-booted
I'm not sure if it was any one thing or some combination, but it seemed to fix the problem. At least for one day.
Currently Being ModeratedOct 1, 2012 4:33 PM (in response to jacooper11)
Hey all, I've got a Late 2010 MBA and I've been having the same problems (leaving at night, coming back to a blank screen and needing to force reboot) for a couple months now. I had a thought, from my end it only seems to happen if I have my 27" Cinema Display attached (via DisplayPort).
Does anyone else have anything attached externally?
Currently Being ModeratedOct 1, 2012 4:49 PM (in response to rmitchell2301)
I see the same issue. If I sleep my Retina MacBook with an external display connected, the console shows that it waked-up every two hours, and eventually hang. When I open up the Retina, the screen is blank, the fans are running, and the case is hot. If disconnect the external monitor, then sleep. I have no problem waking up the Retina.
I also turned off the Energy Saver -> Wake for Network Access. This seems to take care of the problem of waking up every couple of hours. Maybe that will also fixed the failure to wake up from sleep. I will test it again tonight.
Currently Being ModeratedOct 2, 2012 4:47 AM (in response to Pedro Gelabert)
The other piece I think I've nailed down (had a couple nights of testing) is that I have to have engaged my dashboard during the session. I'm wondering if that constant access is something on the dashboard?
Currently Being ModeratedOct 6, 2012 3:31 AM (in response to Pedro Gelabert)
Had same issue for some weeks now (MBP not sleeping, then crashing, in my case a mid-2009 model), with external (Dell) display and keyboard connected. Burned out one of the fans, since replaced. I thought it was the Microsoft wireless keyboard, so upgraded to Apple Keyboard and Magic Mouse, but no difference. Will try disabling Wake for Network Access and Safe Reboot.
This message is in the system log:
Oct 4 08:00:14 localhost kernel: Sleep failure code 0x00008000 0x27006900
This was logged around the time I forced a restart with the power button.
Currently Being ModeratedOct 12, 2012 8:30 AM (in response to jacooper11)
Well, I have been able to safe boot my computer. The messages stop for a while then return. Even without a monitor connected, the computer will not sleep when the messages are generated. If I have a monitor connected and sleep the computer through the menu command, then I when woken up, the display is dark and need to do a force reboot.
Currently Being ModeratedOct 12, 2012 9:43 AM (in response to Pedro Gelabert)
I ended up going to my local Genius Bar, where they figured my MacBook Pro was overheating. The Genius wisked the machine away, and came back a little later saying he had removed the logic board and reapplied thermal paste. The machine appears now to be working, so I think it is likely it was overheating when left on overnight (performing backups and maintenance), hence crashed by morning.
Currently Being ModeratedNov 1, 2012 11:35 PM (in response to jacooper11)
Same issue and Pages,Preview, TextEdit, and Numbers (possibily more) all go to "Not Responding" when trying to open files.
I got further when I hit new document but as soon as it tried to open the template it hangs.