On 2016-10-06 22:12, Guilhem Moulin wrote: > On Thu, 06 Oct 2016 at 19:42:55 +0200, Paride Legovini wrote: >> cryptsetup: WARNING: failed to detect canonical device of /dev/sda2 > > For the record, the hook script gives this warning as it doesn't know > whether the device is to be unlocked at initramfs stage or not. > (Depending on what's on the device, not unlocking it initramfs stage can > render the system unbootable.) Identifying the device by its LABEL or > UUID (or for dm devices, using the the dm name prefixed with > /dev/mapper) should be enough to take it away.
Thanks for the explanation. It's still strange that I'm getting this warning as /dev/sda2 is identified by its UUID (in /etc/fstab, /etc/crypttab is empty). >> cryptsetup: WARNING: could not determine root device from /etc/fstab > > Hmm. This, on the other hand, should not happen if you have an entry in > fstab(5) for the root mountpoint, regardless of whether the device is > encrypted or not. Looking at the hook script's diff since 1.7.0-2 it's > unclear to me what now causes the warning to appear. Could you share > your /etc/fstab? > Here is it (long lines, sorry): # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda2 during installation UUID=5651d651-5c48-425f-9fc9-56f2a9ad004f / btrfs ssd,noatime,compress=lzo 0 1 # /boot/efi was on /dev/sda1 during installation UUID=4791-AD68 /boot/efi vfat umask=0077 0 1 /dev/sdb1 /mnt/16GB ext4 defaults 0 2 The output of blkid /dev/sda2 is: /dev/sda2: UUID="5651d651-5c48-425f-9fc9-56f2a9ad004f" UUID_SUB="2b8d065b-1f69-4770-a9ba-c3f8dde65425" TYPE="btrfs" PARTUUID="729a63f7-aef7-4310-8512-e2d2d761dbe7" so the UUID is correct. Thank you, Paride
signature.asc
Description: OpenPGP digital signature
