MacOS – Weird Yosemite Sleep Behavior

displaymacossleep-wake

Since upgrading to Yosemite, I am having weird issues with sleep mode on my MacBook (mid-2011). Whenever my MacBook goes to sleep, it begins beeping (similar to POST codes on PCs) every 1-2 seconds, and I am forced to do a hard reset. This does not seem to happen when I am not connected to a peripheral monitor (Dell 21" monitor, and DVI adapter), however. Is this a known issue with Yosemite?

EDIT: Sometimes, this happens even without being connected to the monitor. The MacBook just goes into sleep mode, and begins beeping. Only a hard reset remediates the issue. Can someone provide me with a documented cause of this issue, and a fix?

EDIT 2: I've been fiddling with this for weeks, and I still do not know what the root cause is. I've used alternate profiles, eliminated the sleep image (per suggestion below), removed items from startup, and I still get this persistent behavior. Sometimes, after I do the hard reset, the Mac will not start back up after several attempts, but usually does after some time. I have done a hardware test, had it bench tested at a local Apple repair store, and tested the SSD for issues. None seem to be present. None of this happened until I upgraded to Yosemite. I'm out of ideas on this one. Hopefully, someone else has had this experience and can point me in the right direction.

Best Answer

I had a similar issue with mine (mid-2011 MBP running Yosemite), where not only would it go to sleep and not wake up, but it would reboot and freeze midway through the startup process. It would take several hard restarts to get back to a login screen. After awhile, I came across a thread on the JAMF Forums with users having similar issues. I found that this fixed it for me (keep in mind that I am also):

 1. Open System Preferences and select Users & Groups
 2. Select Login Options
 3. Select Edit on the network account server button/section
 4. Select Open Directory Utility
 5. Select Active Directory
 6. Select small gray arrow pointing to the right on the left side to collapse
 7. Uncheck "Force local home directory on startup disk" 
 8. Select the OK button.

I also deleted the sleep image and hibernate mode as per the above poster's suggestion. Since doing both these steps, this issue has gone away.