$ lsinitramfs /boot/initrd.img-5.4.0-9-generic | grep dm-crypt
usr/lib/modules/5.4.0-9-generic/kernel/drivers/md/dm-crypt.ko
Confirmed it is there for -9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
$ lsinitramfs /boot/initrd.img-5.4.0-14-generic | grep dm-crypt
1 $
https://paste.ubuntu.com/p/bDq66dMjYM/ for the full list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Failure to
Interesting. If you list the contents of the initramfs in /boot
(lsinitramfs /boot/initrd.img-5.4.0-14-generic) do you see dm-crypt.ko
in the list of files?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Running cat /proc/modules gives:
i915
i2c_algo_bit
crc32_pclmul
drm_kms_helper
syscopyarea
sysfillrect
sysimgblt
fb_sys_fops
psmouse
sdhci_pci
cqhci
sdhci
lpc_ich
i2c_i801
ahci
drm
libahci
e1000e
wmi
video
(There may be a transcription error or 2 in there, so photo is at
http://ovh.themcphails.uk/
That's certainly a possibility. Can you check from the busybox shell
what modules are loaded when you see the boot failure (cat
/proc/modules)? Or unpack the initramfs and see what modules are
included? Seems like dm-crypt would be the critical one here.
There are likely userspace components that
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-5.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Oddly, I've just had this on 5.4.0-14, whereas 5.4.0-12 works perfectly.
Maybe something is messed up in initramfs generation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Failure to
I tried doing a fresh focal install with lvm/encrypted root and that is
working fine. I'll try starting from eoan and upgrading to focal to see
if that behaves differently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Same behaviour of 5.4.0-14.17
** Changed in: linux-5.4 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Failure to boot with LVM + encrypted ro
Partial transcription from the attached photo:
"Gave up waiting for root file system device"...
"ALERT! /dev/mapper/ubuntu--vg-root does not exist"
** Attachment added: "Photo of screen"
https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+attachment/5327385/+files/photo_2020-0
What is printed on the screen when this happens? Are you able to collect
dmesg, or at least look at it for errors?
We have a newer version in -proposed with numerous updates from upstream
stable, could you give that a try? We have a ppa (ppa:canonical-kernel-
team/proposed) that you can use to get
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Failure to boot with LVM + encrypted root disk
To manage notifications about this bug go to:
https://bugs.launc
** Package changed: linux-meta-5.4 (Ubuntu) => linux-5.4 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862215
Title:
Failure to boot with LVM + encrypted root disk
To manage notifications
13 matches
Mail list logo
