Sleep Wake Failure: Reboots only after upgrading to High Sierra

I do thank you for your analysis and recommendation.

Per the poster earlier in the thread, I have tried the "sudo pmset -a hibernatemode 3 standbydelay 10800 standby 0" command to see if that helps.

Whatever additional insight you might glean I'd be glad to hear it.

many thanks

So much for my desperate hopes the SWF saga would be finally over. After a month with the .5 beta without any problems, the dreaded double-chime of the SWF reboot returned. This is only a quick recap for the sake of continuity.

My hopes were quietly propped up by the lack of the usual daily notifications from the two SWF threads. Since people generally write more about problems than they do about the absence of such, it seemed there is a faint chance the solution might have been found, at last. Looks like it hasn't.

It should be pointed out that there definitely is a difference after the .5beta update in my case, at least. It has been a great relief that for a month my work was free of the daily SWF reboots, which I had mercilessly experienced for months before that. However, as I already mentioned in my first post .5beta update comment, it did not seem very convincing that a complete solution has been found, because the sleep state appeared different and not going to a hibernate-like mode.

For the sake of completeness, it has to be clarified that during all this time I always left the iMac to follow through the power management set period of display and computer sleep (5/10 min). Yesterday for the first time I used the 'apple menu' sleep command, which I used to do in the long distant past, before the SWF plague. It could have been coincidental, but having used the 'sleep' command combined with the passing of the arriving of 'autopoweroff' state, which most certainly invokes hibernation, appears to have caused this horrible SWF again, after otherwise uneventful and so much hopeful month.

Such a disappointment!

Looks like we have arrived. Considering the comments drought of recent, my conclusion is that SWF appears to have been resolved for most affected here. Most likely with the 10.13.5 update of HS. Well, it looked frustratingly remote and unclear as to how we get here but here we are.

My iMac has not experienced a single SWF since the 10.13.5 update, which can cautiously be accepted as resolved. It remains unknown what approach has been taken to provide the solution. In particular, whether any compromises have been made to power management and the system 'sleep' state.

Although I have no proof (as I had not been able to predict the months of SWF suffering, before it happened), it seems to me that before the dreaded 10.13.2 HS update there were two different states of 'sleep' - one, the 'hibernate' on 'autopoweroff' and another, intermediate one, where the computer will still wake up from a memory image saved to the persistent storage, going through the 'grey-screen-with-a-progress-bar' resume process, but somewhat quicker than the wake from an 'autopoweroff' state. Now it is not possible to be certain and will remain unknown, unless a good-natured apple source, confirms or denies it.

Nevertheless, it is undoubtly a huge relief and I can only be grateful to anyone at Apple who has contributed to resolving this problem, although I am not yet ready to forgive all those who refused to acknowledge the existence of the SWF issue for such a long time, even with at least a hint of an official statement, if they did not want to admit it publicly.

PS

It still remains to be seen, if there would not be any residual trouble for users, who might wish to change their 'standby' and 'hibernate' settings, which should not happen, for as long as these are perfectly normal options to set.

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.

The solution you linked is quite interesting, but require a certain skill.

Moreover sounds a little bit risky if you don't know exactly what you're doing.

The author seems to have a proper knowledge of electronics and even found how to modify the cable, mounting an additional resistor.
What I think is that OWC should not declare this device compatible with later 2013+ models, because it is not.

I'm packing the hard drive and sending it back, because for me it's not a replacement to the original.

It seems there's not a solution on the market to make it happen. I mean: should I really send it to Apple or buy a new PoweBook? that's crazy, but absolutely in line with Apple policy.

Amen.

Sorry, I did not realize I needed to take you literally because it seemed so unlikely. So thinking about it another way, it might be possible that if the computer is woken out of sleep often enough i.e. doing backup it will not crash as often. It often took 8 or more hours of sleep for my computer to show the problem.

The computer should be smart enough to realize the backup drive is not available but then anything is possible although not probable.

If you are using a desktop, I fixed this by not using sleep (sleep never) in the preferences. You can still make the screen turn off and you can manually sleep using the right hand pulldown menu which in my case guarantees that the disk drive shuts down so the current draw is what ever it takes to keep the dram alive, this is virtually nothing.

While this is not ideal, I felt like I had spent too much time trying to make it work correctly, if you have a portable that needs to use batteries this is not a good solution.

I had the same problems since I moved to a new Macbook Pro 2017 mid-June. I could have several crashes a day. It seemed to have appeared once I turned on hard disk encryption two weeks after using the computer. I tried many things without great success, except preventing the computer from sleeping. I then decided to do a clean install of my computer 2 weeks ago and my computer did not crash since that time. Note that this is the first clean install since 5-6 years. Probably some old files were causing problems.

I realise that sleep wake failure does not happen any more on my IMAC end 2012...

I am now on High Sierra 10.13.6. Finally, after almost one year, it looks like Apple did fix this bug in new OS that affected only older Macs.

I cannot say that my opinion towards apple has not been much degraded during this year, but at least I'm happy that the bug seems to be fixed.

Sadly for me, I have just been forced to upgrade from El Cap to H Sierra 10.13.6 and now I have all the same sleep/wake problems that you all talk about. Never happened before. Waiting for a call back from the Apple engineer who had told me that they would not be very helpful about troubleshooting various issues if I would not run the latest OS.

You can downgrade to normal Sierra here:

https://support.apple.com/en-us/HT208202

Hopefully that will fix it for now

Same story with a MacBook 12 (2015)

😠

Also, if you wanted to re-enable standby mode, run:

sudo pmset standby 1

Not sure, but you should probably reboot after both, just for fun.

I have the same problem with my iMAC 21.5 after upgrade . 😕