Dear Sam,
Thank you for looking into this.
>
> So, I don't really know what to look for, but I tried:
>
> journalctl | grep hibernate
>
> and got:
>
> Jun 22 06:06:49 localhost.localdomain systemd[1]: Created slice
system-systemd\x2dhibernate\x2dresume.slice - Slice /system/systemd-hibernate-resume.
> Jun 22 06:06:50 localhost.localdomain systemd[1]: Starting
systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service
- Resume from hibernation using device
/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605...
> Jun 22 06:06:50 localhost.localdomain systemd-hibernate-resume[390]: Could not
resume from '/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605' (259:4).
> Jun 22 06:06:50 localhost.localdomain systemd[1]:
systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service:
Deactivated successfully.
> Jun 22 06:06:50 localhost.localdomain systemd[1]: Finished
systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605.service
- Resume from hibernation using device
/dev/disk/by-uuid/a83ac239-cc10-43a6-be54-de4ce7050605.
> Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
> Jun 22 06:06:50 localhost.localdomain audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-hibernate-resume@dev-disk-by\x2duuid-a83ac239\x2dcc10\x2d43a6\x2dbe54\x2dde4ce7050605
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
>
>
> Note however, that this is after the machine was asked to reboot since the system
never came back from hibernate so I am not completely sure it has the information from not
coming back.
What do you mean "doesn't come back up"? Usually the problem is that you
get a normal boot instead of a resume.
Yes, that is right, I get a normal boot instead of a resume, since last Thursday's
updates.
That would correspond to the logs
that you're showing there. The other thing to check is the last bit of the
logs from the previous boot.
I also suggest looking at some lines in that area that might not have been
caught by the grep. Maybe there is a reason listed for why the resume
failed.
Here is the complete journalctl output (after a new boot, since I think that journalctl
restarts?). Perhaps I should be looking at other messages?
https://paste.centos.org/view/3519f018
Here is the output of:
sudo cat /var/log/messages | grep hibernate
https://paste.centos.org/view/b1f418a0
sudo cat /var/log/messages | grep resume
https://paste.centos.org/view/e7807a58
Thank you again for your help, and suggestions.
Best wishes,
Ranjan