Help with my Wake Sleep Error? (iMac)

[kennerguy66]

Hey everyone.

A few days ago I upgraded to High Sierra (really regret that move, and no I didn't time machine)...

Anyway, I set my iMac (21.5" 3.1, late 2013 model purchased in spring 2015, running 10.13.1) to sleep at about 3am, and when I turned it back on I was prompted with 'the computer restarted because of a wake sleep error'.

I was digging around in the logs and it seemed like things tried to install while sleeping, notably 'googlesoftwareupdatemanager' / 'ticketstore'... I have no idea what that even is. I removed chrome, which was the only google app on my computer, and restarted.
In the power management log, I have this error:

2017-11-15 04:04:34 -0500 Failure Sleep Failure [code0P2()]:



A few days go by, no other issues. Then today, I got another 'computer was restarted because of a wake sleep error'.

I looked at the logs again and noticed this in the 'Filesystem repair log'. It happened on both days, at the times of the restart.

1st issue:

fsck_hfs started at Wed Nov 15 04:03:26 2017
** /dev/rdisk0s2 (NO WRITE)
** Root file system
Executing fsck_hfs (version hfs-407.1.3).
fsck_hfs completed at Wed Nov 15 04:03:26 2017


/dev/rdisk0s2: fsck_hfs started at Wed Nov 15 04:04:34 2017
/dev/rdisk0s2: /dev/rdisk0s2: ERROR: volume / is mounted with write access. Re-run with (-l) to freeze volume.
/dev/rdisk0s2: fsck_hfs completed at Wed Nov 15 04:04:34 2017


/dev/rdisk0s3: fsck_hfs started at Wed Nov 15 04:04:35 2017
/dev/rdisk0s3: /dev/rdisk0s3: ** /dev/rdisk0s3 (NO WRITE)
/dev/rdisk0s3: Executing fsck_hfs (version hfs-407.1.3).
QUICKCHECK ONLY; FILESYSTEM CLEAN
/dev/rdisk0s3: fsck_hfs completed at Wed Nov 15 04:04:35 2017



2nd issue:

fsck_hfs started at Sat Nov 18 11:51:30 2017
** /dev/rdisk0s2 (NO WRITE)
** Root file system
Executing fsck_hfs (version hfs-407.1.3).
fsck_hfs completed at Sat Nov 18 11:51:30 2017


/dev/rdisk0s2: fsck_hfs started at Sat Nov 18 11:52:17 2017
/dev/rdisk0s2: /dev/rdisk0s2: ERROR: volume / is mounted with write access. Re-run with (-l) to freeze volume.
/dev/rdisk0s2: fsck_hfs completed at Sat Nov 18 11:52:17 2017


/dev/rdisk0s3: fsck_hfs started at Sat Nov 18 11:52:17 2017
/dev/rdisk0s3: /dev/rdisk0s3: ** /dev/rdisk0s3 (NO WRITE)
/dev/rdisk0s3: Executing fsck_hfs (version hfs-407.1.3).
QUICKCHECK ONLY; FILESYSTEM CLEAN
/dev/rdisk0s3: fsck_hfs completed at Sat Nov 18 11:52:18 2017



I'm also seeing this every few minutes in the 'Apple System Log'

Nov 18, 2017 at 1:37:02 PM com.apple.xpc.launchd[1]: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Nov 18, 2017 at 1:41:13 PM com.apple.xpc.launchd[1]: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Nov 18, 2017 at 1:45:24 PM com.apple.xpc.launchd[1]: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
Nov 18, 2017 at 1:45:24 PM syslogd[57]: ASL Sender Statistics




Any ideas as to what is going on? I reported the issue to apple the second time it happened.

Again, nothing different other than High Sierra.

I turn off wifi before sleeping.
I use nothing in the USB slots.
I have a wireless mouse and keyboard. I switch the mouse off while sleeping, because it's sensitive and a bump can wake it.

 

[lclev]

Have you tried doing an SMC reset and a NVRAM reset?

SMC reset is supposed to help with sleep issues. I would try that first: https://support.apple.com/en-us/HT201295

It won't hurt to reset the NVRAM: https://support.apple.com/en-us/HT204063

Lisa

 

[ferrarr]

Why do you feel the need to sleep your iMac? I haven’t set any of our PC’s (macOS or winOS) to sleep in ate least 6 years, maybe longer.

 

[lclev]

Bob is correct - you do not need to let your iMac sleep. I leave my Mac Pro on and just set the monitors to shut off after an hour of inactivity. They use more power - I have two, a 27" and a 24".

BUT - if you live in an area where the power goes out frequently - and I do - a good UPS is essential. Actually, I believe a good UPS is essential for all electronics. They even out power spikes, can be set to do controlled shutdowns, provide power so documents can be saved, etc.

I still recommend trying the resets I listed above. If you google problems with High Sierra you will find many were fixed after resetting the SMC and NVRAM.

Lisa

 

[chscag]

Not sure I agree with Lisa or Bob. I sleep my iMac every evening when I'm through for the day. Total sleep is more than just shutting off the display on the monitor; it also spins the hard drives down and it puts the machine (through the firmware logic) into low power mode until it wakes. That's how Apple has designed it so I really don't know why you would advise someone not to put their Mac to sleep?

The sleep wake error experienced by "kennerguy66" has occurred more often since "High Sierra" was released. (do some googling) The only way I have been able to resolve it and get my iMac back to normal was to do a SMC long reset. In other words, power off completely and leave it that way overnight. You also need to remove the AC plug from the receptacle.

BTW... I do agree with Lisa about using an UPS. I wouldn't be without one.

 

[lclev]

I guess I should clarify - I don't use sleep on my Mac Pro because I have two server share drives attached. I have found if the MP sleeps then connection is lost and I have to re-mount the drives. So I either leave it on - which allows me to remote access it, or power it off as I have setup the server drives to mount on startup. Since I tend to forget to check to see if they are mounted after letting it sleep, this works best for me.

I use sleep on my MB Air and MB Pro all the time. The MB Air is running High Sierra and the sleep feature works fine.

Lisa

 

[MacInWin]

Charlie, I don't fully sleep my Mac either. I sleep the screen, but given that I have an SSD, there is no reason to sleep the CPU. I originally started leaving the CPU awake because my router was dropping the Mac from the network when it didn't respond to the periodic acknowledgement queries. Then when the Mac woke up, it found no network connection and promptly reported the error, which left my networked backup drive disconnected. Keeping the CPU awake sorted all of that out for me.

 

[chscag]

I have read where some users on various forums have remarked about experiencing network problems when waking from sleep. If leaving the CPU in an insommia mode takes care of the problem, then by all means keep that baby awake. However for most folks, normal sleep should be implemented. It does make a bit more sense when flash memory is installed since there is no spin up or spin down to be concerned with.

 

[kennerguy66]

The sleep wake error experienced by "kennerguy66" has occurred more often since "High Sierra" was released. (do some googling) The only way I have been able to resolve it and get my iMac back to normal was to do a SMC long reset. In other words, power off completely and leave it that way overnight. You also need to remove the AC plug from the receptacle.

BTW... I do agree with Lisa about using an UPS. I wouldn't be without one.

Hey again. Thanks for the ideas. I have reset the PRAM and SMC. Literally left the computer off and unplugged for a couple of days over Thanksgiving.

I have put the computer to sleep three more times since I posted the thread.

Two short ones, under 4 hours, and a longer 6 hour one. I had the same sleep wake error today with the longer sleep session. Sent another error report to Apple.

I guess I'll start leaving it awake, which seems unnecessary, unless someone can give me another idea to try.