https://bugzilla.suse.com/show_bug.cgi?id=1219020 https://bugzilla.suse.com/show_bug.cgi?id=1219020#c12 Dmitry Markov <werwolf131313@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werwolf131313@gma | |il.com) | --- Comment #12 from Dmitry Markov <werwolf131313@gmail.com> --- (In reply to Antonio Feijoo from comment #11)
(In reply to Dmitry Markov from comment #9)
(In reply to Antonio Feijoo from comment #8)
Could you please `zypper dup` and check if this is still reproducible with the latest systemd version. If that's the case, please set `systemctl log-level debug`, issue `systemctl hibernate` and attach the output of `journalctl -b -o short-monotonic`. Thanks!
So. I again created luks encrypted swap, added a key file to it, registered it in fstab, crypttab and kernel cmdline as indicated in the manual, but I never got around to testing hibernation. Now the system simply does not boot with this resume in cmdline (to boot I manually erase this parameter by editing the menu item in grub), the system simply cannot start using swap with this uuid.
[werwolf@workbook] ~ ❯ sudo lsblk -o +UUID NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS UUID nvme0n1 259:0 0 476,9G 0 disk *********************************************************************************************** └─nvme0n1p4 259:4 0 16,9G 0 part 855f2aa2-2f74-4f5f-9197-825c406b84ab └─cr_swap 254:1 0 16,9G 0 crypt [SWAP] 5a0d6b5f-3c80-4778-ad50-0b157b67415c
[werwolf@workbook] ~ ❯ cat /etc/fstab | grep -i swap UUID=5a0d6b5f-3c80-4778-ad50-0b157b67415c swap swap defaults,discard 0 0
[werwolf@workbook] ~ ❯ sudo cat /etc/crypttab | grep swap cr_swap UUID=855f2aa2-2f74-4f5f-9197-825c406b84ab /etc/main.key key-slot=1,discard
[werwolf@workbook] ~ ❯ sudo cat /etc/default/grub | grep resume GRUB_CMDLINE_LINUX_DEFAULT="splash=silent resume=UUID=5a0d6b5f-3c80-4778-ad50-0b157b67415c quiet security=apparmor mitigations=off delayacct"
[werwolf@workbook] ~ ❯ cat /etc/dracut.conf.d/99-luks-key.conf install_items+=" /etc/main.key "
[werwolf@workbook] ~ ❯ cat /etc/dracut.conf.d/99-resume.conf add_device+=" UUID=855f2aa2-2f74-4f5f-9197-825c406b84ab " add_dracutmodules+=" resume "
in my opinion it can be called “it has become worse”. or I forgot to do something, but I don’t understand what.
The UUID in fstab and the resume kernel command line option (/etc/default/grub) is wrong, it should be `855f2aa2-2f74-4f5f-9197-825c406b84ab`.
ok, I checked when changing the resume parameter in cmdline from uuid swap partition to uuid luks partition with swap partition, the system boots correctly but if the same change is made in fstab, then after booting the system swap will be unused. which in my opinion is logical, because this uuid does not point to swap but to luks encrypted partition. I returned the uuid swap partition to swap, and left uuid luks with swap in cmdline, so the system booted correctly and swap worked. however, this did not lead to hibernation working:
[werwolf@workbook] ~ ❯ sudo systemctl hibernate Call to Hibernate failed: Not enough swap space for hibernation
[werwolf@workbook] ~ ❯ sudo journalctl -b -o short-monotonic -f
[ 306.396753] workbook.itrus.su sudo[6895]: werwolf : TTY=pts/3 ; PWD=/home/werwolf ; USER=root ; COMMAND=/usr/bin/systemctl hibernate [ 306.397215] workbook.itrus.su sudo[6895]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred [ 306.397803] workbook.itrus.su sudo[6895]: pam_unix(sudo:session): session opened for user root(uid=0) by werwolf(uid=1000) [ 306.397998] workbook.itrus.su sudo[6895]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_open_session [ 306.398070] workbook.itrus.su sudo[6895]: pam_kwallet5(sudo:session): pam_kwallet5: we were already executed [ 306.408035] workbook.itrus.su sudo[6895]: pam_unix(sudo:session): session closed for user root [ 306.408146] workbook.itrus.su sudo[6895]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session [ 306.408213] workbook.itrus.su sudo[6895]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred
(In reply to Dmitry Markov from comment #10)
Created attachment 872955 [details] boot fail
photo of the boot log with an error
Please next time attach common formats, like jpg or png. Thanks.
sorry, I'll take this into account in the future -- You are receiving this mail because: You are on the CC list for the bug.