if anyone could tell me where in COnsole logs I could find the precise record of what's happening on these uncalled for restarts, I'd be happy to post
I observed the same problem on my iMac Retina 27. The console logs
06:41:46.036209 +0200 powerd Sleep Failure [code:0x11105000400001F]:
Disable FileVault is a working und for this bug on my system.
There is also a thread about this issue on the public Apple forum
Nothing really interesting in this discussion.
Some silly pieces of advice: "upgrade to 10.13.4" when the problem seems typical of 10.13.4..
ls -alt *.asl
to get the appropriate log file
open it with:
I have the same problem on a newly installed MacBookPro:
MacBook Pro (Retina, 15-inch, Mid 2015)
FileVault is on
contains the typical error code:
21:24:55.692880 +0200 powerd Sleep Failure [code:0x11105000400001F]:
after the following entering into sleep mode on a low level battery:
17:54:35.439839 +0200 powerd Entering Sleep state due to 'Low Power Sleep':TCPKeepAlive=inactive
This bug is fixed with an update to MacOS 10.13.5: https://support.apple.com/kb/DL1965.
I tested it with the following power management settings:
pmset standby 1 pmset autopoweroff 1
pmset hibernatemode 3 pmset hibernatemode 25
All these tests were run with:
battery level low
battery level low to a level were the OS decides to sleep on its own.
On all these tests I never saw the typical error:
powerd Sleep Failure [code:0x11105000400001F]:
and the exit from sleep, through any key or with the power on button were successfull.
My conclusion is:
MacOS 10.13.4 sleep bug fixed with 10.13.5,
This version is good for work!