You are not logged in.
Pages: 1
So I have everything setup, it boots properly to a point that it asks for crypthome password then spits out a device uuid that no longer exists and drops me to a recovery shell.
My fstab points to the /dev/mapper/cryptroot, crypttab to the proper UUID, no excessive entries in either. Grub GRUB_CMDLINE_LINUX_DEFAULT has cryptdevice=/dev/sda2:cryptroot cryptkey=/dev/mapper/cryptroot:ext4:/ also tried it with root=/dev/mapper/cryptroot, should I switch cryptdevice to a uuid?
I have no clue where this UUID is coming from that it spits before the shell so that should be a big hint. I just cant figure out where it would be initializing this, let alone as root..
There also is a usb 2-4 string descriptor 0 read error before this, could it be looking for a usb?
I can open the drives with cryptsetup and mount them that way but that is such a hassle to do everytime, would be great to figure out the deal. Recommendations?
Sorry for lack of output or actual files this is on my laptop and I am typing this on my desktop.
Last edited by vuvffufg (2015-10-05 06:17:23)
Offline
So I think I've narrowed it down to a few things. Either mkinitcpio isnt loading root, or grub isn't.
I cant find anywhere on how your supposed to make mkinitcpio mount/open root. My /boot/grub/grub.cfg has a uuid for the root partition then my entry at /etc/default/grub/ I found that strange, but once I edited the file remove the uuid at boot and it did the same thing. Only prompts for home and throws me to recovery for root.
I've also discovered that I shouldnt have root being mounted in crypttab so removed it from there. I've messed with the entries on grub making them in every which order. Also ran mkinitcpio -p linux root=/dev/sda2.
I JUST CANT FIGURE OUT HOW TO GET ROOT TO MOUNT! I'll try to get more detailed entries tonight.
Offline
Indeed, the link to the wiki tells you how to do this. I've run into this problem myself but I figured it out in the end. The inclusion of LVM in the LUKS information only makes it more confusing for the inexperienced user who have no need for LVM.
The LUKS UUID isn't visible to the kernel because the initramfs doesn't hold the necessary hooks that expose LUKS partitions for the kernel to be able to see the LUKS UUIDs. The kernel doesn't see LUKS at boot unless you put the proper hooks into the initramfs.
You must edit /etc/mkinitcpio.conf and add the 'encrypt' hook before 'filesystems'.
If you have managed to get GRUB ask you for a password then all that's missing is the 'encrypt' hook in the initramfs.
I use GPT and no special tricks, no LVM either. I have encrypted the entire system except the the ESP (only holds standalone GRUB EFI file). Works like a charm!
Another good read is found here:
http://www.pavelkogan.com/2014/05/23/lu … ncryption/
Offline
Pages: 1