At startup, systemd tries to Resume from Hibernation (which is disabled)
Looking at the messages that come up during boot, I see a 30 second delay while systemd tries to Resume from Hibernation. Looking at the Services settings in YaST, I see that all services related to this are disabled. How do I tell systemd not to attempt this during boot? (Does this happen when initrd is active, or after switching to real /?) | From YaST => System => Services: | │systemd-hibernate │Manually │Inactive (Dead) │Hibernate │ | │systemd-hybrid-sleep │Manually │Inactive (Dead) │Hybrid Suspend+Hibernate │ | │systemd-suspend │Manually │Inactive (Dead) │Suspend │ | | From journalctl: | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | May 18 21:48:39 pinto systemd[1]: Timed out waiting for device dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device. | May 18 21:48:39 pinto systemd[1]: Dependency failed for Resume from hibernation using device /dev/mapper/cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3. | May 18 21:48:39 pinto systemd[1]: systemd-hibernate-resume@dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.service: Job systemd-hibernate-resume@de> | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | | From /etc/crypttab: | swap UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom | # cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3 UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom Leslie -- openSUSE Leap 15.2 x86_64
On 19/05/2021 06.52, J Leslie Turriff wrote:
Looking at the messages that come up during boot, I see a 30 second delay while systemd tries to Resume from Hibernation. Looking at the Services settings in YaST, I see that all services related to this are disabled. How do I tell systemd not to attempt this during boot? (Does this happen when initrd is active, or after switching to real /?)
Can't be. Resume from hibernation happens very early and is done by the kernel, not systemd. The kernel loads and at some point very early checks the swap partition to see if there is an hibernation image there. If not, it continues. It is controlled by the "resume=..." option in the kernel line.
| From YaST => System => Services: | │systemd-hibernate │Manually │Inactive (Dead) │Hibernate │ | │systemd-hybrid-sleep │Manually │Inactive (Dead) │Hybrid Suspend+Hibernate │ | │systemd-suspend │Manually │Inactive (Dead) │Suspend │ | | From journalctl: | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | May 18 21:48:39 pinto systemd[1]: Timed out waiting for device dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device. | May 18 21:48:39 pinto systemd[1]: Dependency failed for Resume from hibernation using device /dev/mapper/cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3. | May 18 21:48:39 pinto systemd[1]: systemd-hibernate-resume@dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.service: Job systemd-hibernate-resume@de> | May 18 21:48:39 pinto systemd[1]: dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> | | From /etc/crypttab: | swap UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom | # cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3 UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom
Despite the messages, systemd can not control resume from hibernation, has to be something else but related. I would check fstab. Whatever the partition is used for, it has to be opened. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
On 2021-05-19 04:19:24 Carlos E. R. wrote:
|On 19/05/2021 06.52, J Leslie Turriff wrote: |> Looking at the messages that come up during boot, I see a 30 second |> delay while systemd tries to Resume from Hibernation. Looking at the |> Services settings in YaST, I see that all services related to this are |> disabled. How do I tell systemd not to attempt this during boot? (Does |> this happen when initrd is active, or after switching to real /?) | |Can't be. | |Resume from hibernation happens very early and is done by the kernel, |not systemd. The kernel loads and at some point very early checks the |swap partition to see if there is an hibernation image there. If not, it |continues. It is controlled by the "resume=..." option in the kernel line.
Ah. Thank you. I have removed that option from /etc/default/grub.
| |> | From YaST => System => Services: |> | │systemd-hibernate │Manually │Inactive (Dead) │Hibernate |> | │ │systemd-hybrid-sleep │Manually │Inactive (Dead) │Hybrid |> | Suspend+Hibernate │ │systemd-suspend │Manually │Inactive (Dead) |> | │Suspend │ |> | |> | From journalctl: |> | May 18 21:48:39 pinto systemd[1]: |> |> dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job |> dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> |> |> | May 18 21:48:39 pinto systemd[1]: Timed out waiting for device |> |> dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device. |> |> | May 18 21:48:39 pinto systemd[1]: Dependency failed for Resume from |> | hibernation using |> |> device /dev/mapper/cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3. |> |> | May 18 21:48:39 pinto systemd[1]: |> |> systemd-hibernate-resume@dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AF |>BY9T\x2dpart3.service: Job systemd-hibernate-resume@de> |> |> | May 18 21:48:39 pinto systemd[1]: |> |> dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x2dpart3.device: Job |> dev-mapper-cr_ata\x2dST1000DM010\x2d2EP102_Z9AFBY9T\x> |> |> | From /etc/crypttab: |> | swap |> |> UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom |> |> | # cr_ata-ST1000DM010-2EP102_Z9AFBY9T-part3 |> |> UUID=618ca366-638c-4bf8-bd86-917f0eac83db /dev/urandom | |Despite the messages, systemd can not control resume from hibernation, |has to be something else but related. I would check fstab. Whatever the |partition is used for, it has to be opened.
Leslie -- openSUSE Leap 15.2 x86_64
J Leslie Turriff composed on 2021-05-19 04:42 (UTC-0500):
On 2021-05-19 04:19:24 Carlos E. R. wrote:
|Resume from hibernation happens very early and is done by the kernel, |not systemd. The kernel loads and at some point very early checks the |swap partition to see if there is an hibernation image there. If not, it |continues. It is controlled by the "resume=..." option in the kernel line.
Ah. Thank you. I have removed that option from /etc/default/grub.
I don't think that's enough. I've been changing it to noresume since forever, pending discovery of how to keep any resume image from becoming created in the first place. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2021-05-19 a las 19:07 -0400, Felix Miata escribió:
J Leslie Turriff composed on 2021-05-19 04:42 (UTC-0500):
On 2021-05-19 04:19:24 Carlos E. R. wrote:
|Resume from hibernation happens very early and is done by the kernel, |not systemd. The kernel loads and at some point very early checks the |swap partition to see if there is an hibernation image there. If not, it |continues. It is controlled by the "resume=..." option in the kernel line.
Ah. Thank you. I have removed that option from /etc/default/grub.
I don't think that's enough. I've been changing it to noresume since forever, pending discovery of how to keep any resume image from becoming created in the first place.
This option is used to tell the kernel to check for resume and do it if present. Creation of the hibernation image is done by another procedure at a different point in time. However, if you force somehow the system to create an hibernation image it can not be used to resume. For example, you could have several kernels installed on the same system, and some may be configured to not resume and others to do resume. And possibly one kernel could resume an image created by another. - -- Cheers Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYKWjcBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcgfcA+wUXa/PBrNy6aP/pSSd6 7gvUqWGEtdwCamjlIctZ0lVqAP9ZUblPC278HhmWY2TlyYpddhoNcH1iv2x6/t77 u8n4UQ== =0ssp -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R. -
Felix Miata -
J Leslie Turriff