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#11495 - cryptdevice in the grub kernel line is uneffective

Attached to Project: Arch Linux
Opened by Manuel C. (ekerazha) - Monday, 15 September 2008, 18:26 GMT
Last edited by Thomas Bächler (brain0) - Tuesday, 16 September 2008, 09:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

My setup is similar to the setup of Tonohono on this thread (LVM inside LUKS encrypted device): http://bbs.archlinux.org/viewtopic.php?id=53179

I have

/dev/sda1 -> NTFS partition

/dev/sda2 -> EXT2 /boot partition

/dev/sda3
-- /dev/mapper/crypt -> LUKS encrypted device
---- /dev/mapper/cryptvg -> LVM volume group (inside LUKS encrypted device)
------ /dev/mapper/cryptvg-swap
------ /dev/mapper/cryptvg-root

Inside /etc/mkinitcpio.conf I have hooks with this order "encrypt lvm2 filesystems"

Inside /boot/grub/menu.lst I have

kernel /vmlinuz26 root=/dev/mapper/cryptvg-root cryptdevice=/dev/sda3:cryptvg ro vga=792

(I've also tried several other lines, like "kernel /vmlinuz26 root=/dev/mapper/cryptvg-root cryptdevice=/dev/sda3:crypt ro vga=792")

but it doesn't work. When I boot the system I see the "encrypt" hook is called, but it doesn't prompt for any password, so /dev/mapper/cryptvg-root isn't created and the boot fails (I receive the recovery console).

/dev/sda3 *is* a LUKS device, because "cryptsetup luksUUID /dev/sda3" correctly returns the LUKS ID.

I feel very stupid because I'm trying to make this work from weeks but I can't understand why it doesn't work. Bug?

Thank you very much.
This task depends upon

Closed by  Thomas Bächler (brain0)
Tuesday, 16 September 2008, 09:26 GMT
Reason for closing:  Not a bug
Comment by Thomas Bächler (brain0) - Tuesday, 16 September 2008, 07:55 GMT
What does 'cryptsetup isLuks /dev/sda3; echo $?' return?
Comment by Thomas Bächler (brain0) - Tuesday, 16 September 2008, 08:05 GMT
Ah, and please attach your kernel26.img and menu.lst.
Comment by Manuel C. (ekerazha) - Tuesday, 16 September 2008, 08:37 GMT
'cryptsetup isLuks /dev/sda3; echo $?' returns '0', 'cryptsetup luksUUID /dev/sda3' correctly returns the LUKS ID.

Please note that directly using 'root=/dev/sda3' without 'cryptdevice=" it DOES prompt for the password when I boot the system (but it is wrong as the root is '/dev/mapper/cryptvg-root').

I attach my kernel26.img and menu.lst.
(application/octet-stream)    kernel26.img (1.88 MiB)
   menu.lst (1.4 KiB)
Comment by Manuel C. (ekerazha) - Tuesday, 16 September 2008, 08:39 GMT
I see 'nano' sent 'cryptdevice=' to a new line, could this be the issue? I try to remove the new line.
Comment by Manuel C. (ekerazha) - Tuesday, 16 September 2008, 08:43 GMT
Shit... it was that new line automatically added by 'nano' (I thought it was a screen-only, but it added a real new line).

You can close this report... nice too see I've wasted hours reinstalling the system and it was just a new line inside a text file :D
Comment by Thomas Bächler (brain0) - Tuesday, 16 September 2008, 09:26 GMT
Yeah, nano can be a bitch.

Loading...