Sleep Wake Failure: Reboots only after upgrading to High Sierra

Is yours with the stock SSD?

After discussions with OWC and others, it does seem like Apple has seriously mis-calculated their power management capabilities.

We resolved the issue by opening up terminal and running:

sudo pmset standby 0

This disables standby which, in most cases, kicks in at about 3 hours into sleep. This will cut a lot more power to more of the system. And this is why it has issues coming back alive after a long (+3h) sleep. You actually might still have long-boot issues when rebooting or cold booting, but at least you can not have these ridiculous wake issues.

You should be good ... Try it and see.

Apple has yet to acknowledge any of the issues anyone has with their 2012-2015 MacBook and MacBook Pros. I know multiple people that Apple has charged for replacement SSD when it is obviously an engineering flaw.

Same problem here with an iMac 21.5'', Late 2012 with macOS High Sierra 10.13.1 installed on an SSD OWC Mercury Extreme Pro 6G of 1 TB. I solve this issue making the downgrade to macOS Sierra 10.12.6. Now everything is OK. I don't know if it a macOS High Sierra 10.13.1 problem or a compatibility issue between APFS and OWC firmware!

Hi,

macOS High Sierra is until now the Apple OS that gave me more problems.

To make the downgrade to macOS Sierra is easy if you know what you are doing. What I did was:

- Create a bootable macOS Sierra USB pendrive using the command:

sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume --applicationpath /Applications/Install\ macOS\ Sierra.app (See: https://support.apple.com/en-us/HT201372)

Replace MyVolume with the name of your volume.

- After boot from the USB pendrive with macOS Sierra, using command line I deleted the APFS partition using this two commands:

To see the partitions:

diskutil list

To delete the Apple_APFS partition:

diskutil apfs deleteContainer diskXsY

Please change X and Y to the correct numbers.

After delete the APFS partition format the disk with HFS+ and install macOS Sierra.

Note: I recommend you to wait for the release of the 10.13.2 update. Maybe they will solve this issue!

Regards,

I found that having "power nap" set on seemed to be the heart of my sleep-reboot issue. I didn't have the problem under HS until I turned power nap on and the problem ended when I turned power nap back off.

I had never had any issues like this until I upgraded to High Sierra and then it was persistent.

Somewhere, I saw a reference to the possibility that it could be related to VPN software, which struck a chord because I had just recently installed Cisco's AnyConnect Secure Mobility Client. So I uninstalled that app, and the issue went away. Then I reinstalled the app, expecting the issue to return, but it has not returned and it's been 2 or 3 weeks.

I suspect that won't help the majority of users, but I thought I'd share it in case it helps a few.

I've spoken to OWC support for the Aura X Pro, mounted on a Late 2013 MacBookPro.

They stated that the issue regards hibernation and not standby and it is actually in discussion between SDD producers and Apple. They say they're working on a solution.

Timing? not revealed.

The temporary solution is disabling hibernation, with:

pmset -a standby 0

But keep an eye on the battery level, because when the mac runs out of charge it will switch off without hibernating.

Hi to all,

Just a little information : the sleep/wake problem is inherent to all NVMe drives, not only OWC.

All Macs from 2013 and up had their BootRom updated with High Sierra, in order to provide boot on APFS drives.

2015 and up macs (like MacBookPro11,4 and MacBookPro11,5) do incorporate a full NVMe DXE driver in their BootRom.

late 2013 and 2014 do incorporate a less complete NVMe DXE driver in their BootRom, and so, they have the ability to boot on NVMe drives (which are recognize as external while pressing "alt" at cold boot), but they fail at resuming from hibernation file after being put in standby mode (which occurs after 10800 seconds by default).

-> Every 2013-2014 Mac (rMBP 13" and 15", MacBook Air, etc.) do have the ability to boot on NVMe drives but fails at wake up from hibernation with every NVMe drive in the market (I have tested with an Apple SM2048L from an iMac 17,1, with other NVMe drives like Samsung 960 Pro and Evo, Kingston, etc.)

A working workaround involve replacing the incomplete NVMe DXE drive in BootRom by a NVMe DXE driver from any BootRom of any 2015 Mac, see here :

Upgrading 2013/2014 Macbook Pro SSD to M.2 NVMe | Page 52 | MacRumors Forums

Of course, disabling standby get you rid of panic/reboot after hibernation : "sudo pmset standby 0"

But this involve never having proper hibernation (with RAM shut off), and, thus, having a high battery drain on sleep.

Hi again,

I did one thing and this issue stops until now 🙂

I normally use a Standard account instead of an Admin account. I reinstalled macOS High Sierra, create a Admin account and then a Standard account. Now I use the standard account on a daily basis and, until now, this error stops.

Crossed fingers 🙂

Hi guys . disable the wifi function in your computer. Connect via ethernet and you will see that it will not make you reboot anymore. The same thing happened to me. After I did this I have not had that problem anymore. Greetings .🙂

My mid-2014 MacBook Pro recently started doing this a couple of times a day. I have a Sphero BB-8, and had plugged the charging base into one of the USB ports on my Thunderbolt Display. That was the only thing that changed recently, so I unplugged it. Problem solved.

I use Parallels Desktop and I found out, that it's function "check for update" is causing "sleep wake failure".

yes. disabling it in Parallels preferences pane, eliminated sleep wakeup failure in my case.

Tried the "sudo pmset standby 0" fix mentioned in this thread.

Worked Flawlessly! Its been a couple weeks with no more crashes!

Update - turned off bluetooth and now it works!?!?!?

also tried to reset bluetooth via SMC reset and Bluetooth debug - but did not help????

Anyone who experienced the same after upgrading to High Sierra?

Hi guys . I had this same problem with my Imac. But after I disable the wireless function and connect my Imac through ethernet, I have not had the reboots again as I did days ago. Try to see if that works for them. Greetings and Happy Holidays!