boot, missing module, and luks issues, please help
I'm playing around with creating some example configurations in a VM,
and I'm having some issues.
I have a Debian sid amd64 installation in a VM, which uses a combination
of GPT, EFI, btrfs, and LUKS, with two HDDs.
I laid out the partitioning during installation as follows (forgetting
to create a swap partition):
sda1: ESP
sda2: /boot (btrfs)
sda3: [LUKS] / (btrfs)
sdb1: [LUKS] /home (btrfs)
Issue #1
------------------
Loading this VM, I initially get dumped at an EFI shell prompt. Why?
Note for below, just in case it is at all relevant, the device I load
the efi file from here is:
[PciRoot (0x0) /Pci (0xD, 0x0) / Sata (0x0, 0x0, 0x0)
/HD(1,GPT,06f22f0a<etc>,0x800,0xF3800)]
EFI/debian/grubx64.efi
Issue #2
------------------
Having gotten past the EFI shell prompt, the grub bootloader is
displayed. Trying to load the OS, I get dumped at an initramfs prompt,
after the following output:
[ 0.000000] tsc: Fast TSC calibration failed
loading, please wait...
modprobe: module ehci-orion not found in modules.dep
Gave up waiting for root device. Common problems:
<blah>
ALERT! /dev/mapper/sda3_crypt does not exist. Dropping to a shell!
modprobe: module ehci-orion not found in modules.dep
(initramfs)
dmesg | grep ehci:
[ 0.360008] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.360380] ehci_pci: EHCI PCI platform driver
dmesg | grep sda3:
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64
root=/dev/mapper/sda3_crypt ro quiet
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64
root=/dev/mapper/sda3_crypt ro quiet
[ 1.832700] sda: sda1 sda2 sda3
I need to figure out how to fix this, but I would also like to
understand the cause, partly just to know, but also in regards to filing
a bug report about it.
As an attempt at a possible fix, I used a live-cd to access the
installation via a chroot, with the intention of running
update-initramfs -u after adding ehci-orion to
/etc/initramfs-tools/modules. This leads me to the next issue.
Issue #3
------------------
I am getting the following trying to run update-initramfs -u (from
within chroot from a live-cd):
update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
cryptsetup: WARNING: could not determine root device from /etc/fstab
Warning: /sbin/fsck.btrfs doesn't exist, can't install to initramfs,
ignoring.
>From within the live-cd, I issued the following commands:
sudo cryptsetup open --type luks /dev/sda3 sda3_crypt
sudo mkdir /mnt/deb
sudo mount /dev/mapper/sda3_crypt /mnt/deb
cd /mnt/deb
sudo mount -t proc proc proc/
sudo mount -t sysfs sys sys/
sudo mount -o bind /dev dev/
sudo mount /dev/sda2 boot/
sudo chroot .
>From this point I can run apt-get fine. Running update-initramfs -u
gives the above though.
Searching for information on this only led to unhelpful info suggesting
that /etc/crypttab isn't configured correctly, but I've had no luck
trying to figure out what exactly could be wrong.
Contents of /etc/fstab:
/dev/mapper/sda3_crypt / btrfs 0 1
UUID=323eaa<etc> /boot btrfs defaults 0 2
UUID=E1FA-32B6 /boot/efi vfat umask=0077 0 1
/dev/mapper/sdb1_crypt /home btrfs defaults 0 2
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
Contents of /etc/crypttab:
sda3_crypt UUID=7c022832<etc> none luks
sdb1_crypt UUID=b9088bef<etc> none luks
blkid output:
/dev/sr0: <ignoring, not important here>
/dev/sdb1: UUID="b9088bef<etc>" TYPE="crypto_LUKS" PARTUUID="fa6c1206<etc>"
/dev/sda1: UUID="E1FA-32B6" TYPE="vfat" PARTUUID="06f22f0a<etc>"
/dev/sda2: UUID="323eaaf0<etc>" UUID_SUB="d1683a3a<etc>" TYPE="btrfs"
PARTUUID="c7d63ae6<etc>"
/dev/sda3: UUID="7c022832<etc>" TYPE="crypto_LUKS" PARTUUID="46c5d6fd<etc>"
/dev/loop0: TYPe="squashfs"
/dev/mapper/sda3_crypt: UUID="82aaf0a6<etc>" UUID_SUB="4cb2889d<etc>"
TYPE="btrfs"
/dev/sdc: PTUUIT="aa6a5ccb<etc>" PTTYPE="gpt"
Reply to: