Currently Being ModeratedDec 30, 2012 9:57 PM (in response to composerguy78)
I've noticed the same problem my MacBook Pro (Retina Mid 2012), after several hours of it sleeping, I have to restart it.
The logs show an error "mdworker(1091) deny mach-lookup com.apple.ls.boxd" I'm running OS X 10.8.2 (12C3006).
Have you found a resolution to the cause of the problem?
Currently Being ModeratedDec 31, 2012 8:41 AM (in response to mad-kiwi)
I have not yet no. It seems that there is some problem in Mtn Lion causing this to happen. It's very helpful to know that this is happening on a new machine like yours, not just 3 year old mac Pros like mine.
Please post here if you discover any fixes, I'll do the same.
Currently Being ModeratedDec 31, 2012 8:47 AM (in response to Linc Davis)
Firstly, sorry for being such a PITA!
I have booted from my 10.7 Lion partition and this issue does not happen. Everything is running fine.
(I also did a clean install (with no migration of any data) of 10.8 and this unresponsive issue DOES still happen. The only additional apps I installed where dropbox, launchbar & 1password).
I am assuming that this means that it is probably NOT a hardware issue.
Do you think you would be able to review any of my console logs in the 10.8 system or suggest what I should look for in the logs?
I would very much appreciate as I would love to get Mtn Lion running on this machine.
Currently Being ModeratedDec 31, 2012 1:32 PM (in response to composerguy78)
Out-of-date versions of 1password have been known to cause some issues in previous systems.
You should take a careful look at the support sites for all of those add-ons, or simply not install them.
"The vast majority of wounds from software updates are self-inflicted."Mac Pro (Early 2009), Mac OS X (10.6.8), & Server, PPC, & AppleTalk Printers
Currently Being ModeratedDec 31, 2012 2:05 PM (in response to composerguy78)
Outside of the core OS the only apps we have in common is Dropbox. I don't use launchbar or 1password.
I'll uninstall drop box and see if things improve.
Currently Being ModeratedJan 3, 2013 3:20 PM (in response to composerguy78)
I've had the same model Mac Pro and the same problem really since I've purchased it back in 2009. I have gone through 4 OS iterations (Leopard, Snow Leopard, Lion, Mountain Lion) and even did a clean install at one point. I've done all as listed in this post and much beyond this and I've have never been able to resovle. The other issue is that I've always had trouble even getting the machine to sleep on it's own and use a program called "Please Sleep" to even force into sleep mode on a regular basis..... Not the answer you were looking for, but if you ever find a solution please post....
Currently Being ModeratedJan 3, 2013 8:41 PM (in response to dcoughlin)
This was really helpful. I really appreciate this. I DID have a similar issue to this when I was on Snow Leopard but it turned out to be the firewire card that caused weird sleep problems - at least when I removed it they stopped. I eneded up using 'Please Sleep' to force it to sleep which worked perfectly.
I haven't had these issues whilst running my Lion partition however. Everything seems to work fine in Lion. It's just started being fussy again with this strange -no response issue after sleep etc. I'm now trying a few things. I wish I knew how to understand the console better as I'm sure
I was listening to my fave mac fixit podcast (MacGeekGab) and on the latest episode entering the terminal command below cleared up a similar problem for a user. Worth a try for you perhaps?
sudo shutdown -h now
Currently Being ModeratedJan 4, 2013 9:25 AM (in response to dcoughlin)
I am getting some advice from experts that this may be from a bad drive. Have you tried installing the OS on a clean (zeroed out) drive?
I am going to test, currently wiping drives to test a clone.
Currently Being ModeratedJan 4, 2013 9:36 AM (in response to composerguy78)
Yes, I did a clean install of SL and one point and did it with a newly installed drive and then switched that to my default startup disk. The old primary boot drive is now a secondary "backup" boot disk that I clone once a week with SuperDuper. Problem remained the same.
Currently Being ModeratedJan 4, 2013 10:31 PM (in response to dcoughlin)
Okay, currently testing a clone with a clean install now.
In the mean time I thought this might other people who have posted with this problem. This is from a podcast I listen to called the Mac Geek Gab. I emailed in my problem, I got this back as a reply.
"I think the first thing to try would be to install Mountain Lion on an external disk (and/or Lion on the internal disk). We're assuming the issue is ML (and it may be), but … it's possible it's simply a bad drive. In fact, it sounds exactly like it's a bad drive and the system can't recover from it.
Another way to test would be a surface scan of the disk to see if you find any bad sectors. But I would only use that as positive confirmation: if it comes back negative I still wouldn't rule out some drive-related issue until you confirm that this happens with ML without the internal drive involved (like you have with Lion).
Also, has your clean install been on a freshly-formatted internal drive? I just want to make sure it's *truly* clean and that you're not doing a clean install over the top of existing data. THat, too, could be a factor here."
Currently Being ModeratedJan 7, 2013 7:46 AM (in response to composerguy78)
I just wanted to report that since following the above directions, I am NO LONGER experiencing this issue!!
I am about to copy the system back to the SSD drive.
I don't know of the best way to wipe clean an SSD drive so I am currently researching that.
Keep you posted. To all that that have had this issue, I would recommend giving this a try!
Currently Being ModeratedJan 7, 2013 7:56 AM (in response to dcoughlin)
A bad drive.
The drive was not properly erased before I installed to it.
When I installed the (non-clean install) to a new clean partition, I had no problems. I did try a clean install on the bad drive, but without success. I copied the non-clean install to the new partition and it's been fine.