Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62827 - [dracut] System doesn't boot from an image created by dracut

Attached to Project: Arch Linux
Opened by Mthw (jari_45) - Thursday, 06 June 2019, 07:15 GMT
Last edited by Giancarlo Razzolini (grazzolini) - Thursday, 21 November 2019, 09:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Giancarlo Razzolini (grazzolini)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I tried dracut using this command: "sudo dracut -H -f /boot/initramfs-linux-mainline.img" but the system won't boot.
Boot process gets stuck at "something like my Plymouth boot screen" meaning, my Plymouth boot screen consists of an image, a spinning circle animation, line of text and a passphrase prompt (Breeze theme with changed text string). It only shows the image and the spinning circle animation and gets stuck. I boot from systemd-boot and have a LVM-on-LUKS type of setup, root partition is XFS. I also tried linux-zen and linux-clear but with the same results. Is there something I am doing wrong? Also is this a good place for a report like this one?

Log: https://pastebin.com/pQPjgsPw
This task depends upon

Closed by  Giancarlo Razzolini (grazzolini)
Thursday, 21 November 2019, 09:35 GMT
Reason for closing:  Not a bug
Comment by Giancarlo Razzolini (grazzolini) - Tuesday, 12 November 2019, 22:28 GMT
Did you change your bootloader to load that new image? Because that's not the *default* image name.
Comment by Mthw (jari_45) - Sunday, 17 November 2019, 09:10 GMT
@grazzolini Not sure I understand your question correctly, but here is my config: https://pastebin.com/Hb0crVfU
Can you see an issue there?
Comment by Giancarlo Razzolini (grazzolini) - Monday, 18 November 2019, 12:25 GMT
Try passing --no-hostonly-cmdline as well. Also, I suggest you disable plymouth to make sure it's not the cause of your issue.
Comment by Mthw (jari_45) - Wednesday, 20 November 2019, 06:45 GMT
I did both, nothing changed, except now I can see it gets stuck at "Starting dracut initqueue hook..."
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 20 November 2019, 12:13 GMT
Ok. Paste your kernel cmdline, your dracut run output. Also, try disabling quiet, if you haven't done so already.
Comment by Mthw (jari_45) - Wednesday, 20 November 2019, 17:01 GMT
Command line: initrd=\intel-ucode.img initrd=\initramfs-linux-mainline.img cryptdevice=UUID=b86defe4-fa31-4c1b-99da-debd253094dd:volgroup0:allow-discards root=/dev/mapper/volgroup0-root rw resume=/dev/mapper/volgroup0-root resume_offset=4575507

dracut output: https://pastebin.com/KbDKjWqS

Is this what you wanted?
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 20 November 2019, 17:07 GMT
You need rd.luks, not cryptdevice to use dracut. It uses systemd. man kernel-command-line
Comment by Mthw (jari_45) - Wednesday, 20 November 2019, 17:44 GMT
I changed 'cryptdevice=UUID' to 'luks.uuid' but that didn't do anything. Am I missing something?
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 20 November 2019, 18:03 GMT
No, it's a different argument. I personally use rd.luks.uuid=<UUID>. But it doesn't get the mapper name there, like cryptdevice does. Please refer to the man page I've pointed you. There's a rd.luks argument that's different. Check man systemd-cryptsetup-generator for details.
Comment by Mthw (jari_45) - Wednesday, 20 November 2019, 18:38 GMT
I changed the config like this, and it works correctly with mkinitcpio, but still not with dracut:
initrd=\intel-ucode.img initrd=\initramfs-linux-mainline.img rd.luks.uuid=b86defe4-fa31-4c1b-99da-debd253094dd rd.luks.name=volgroup0 root=/dev/mapper/volgroup0-root rw resume=/dev/mapper/volgroup0-root resume_offset=4575507
Comment by Giancarlo Razzolini (grazzolini) - Wednesday, 20 November 2019, 19:44 GMT
That rd.luks.name argument is incorrect. You're using the same device mapper name as your lvm volume group. Use something else. At this point I'm quite confident this isn't a dracut issue, at all.
Comment by Mthw (jari_45) - Thursday, 21 November 2019, 08:38 GMT
Yes it might not be a dracut issue, my problem is most likely caused by lack of information/knowledge. Could you maybe write something to the Wiki page?
Comment by Giancarlo Razzolini (grazzolini) - Thursday, 21 November 2019, 09:35 GMT
I have already sent you all the documentation you need. Also, these parameters aren't dracut specific. You use them when booting using a systemd enabled mkinitcpio image. They are also explained in detail here: https://wiki.archlinux.org/index.php/Dm-crypt/System_configuration#Using_sd-encrypt_hook

Loading...