You have been subscribed to a public bug:

[IMPACT]

Install and boot of the FIPS kernel packages
failed with disk not found errors on amd64.
This was also observed on standard Ubuntu 
kernels prior to 4.11.0. 

FIPS
------
1. linux-image-4.4.0-1002-fips <-- FAIL
2. linux-image-4.4.0-1006-fips <-- FAIL


UBUNTU
------------

1. Bionic kernels all WORK

2. Artful kernels:

   Ubuntu-4.11.0-1.6 <-- WORKS
   Ubuntu-4.10.0-26.30 <-- FAILS

3. Xenial kernels:
   
   Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS
   Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS
   
   Ubuntu-lts-* <--- ALL FAIL
   Ubuntu-4.4.0-* <--- ALL FAIL


We have narrowed down the window to be:

4.11.0-1.6 (custom build) <--- WORKS
4.10.0-43.47~16.04.1   <-- FAILS

Also works:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb


Symptoms
-------------
System cannot find the root disk and drops into
an initramfs shell:

mdadm script local-block "CREATE group disk not found"
"Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay=...
   - Check root= ...
 - Missing modules (cat /proc/modules; ls/dev)
ALERT! UUID=... does not exist. Dropping to a shell!

...
(initramfs)_

There does not appear to be any workaround so far. 
The disks are encrypted SSDs. 

Attaching commit list between the last known 
failing Artful kernel and earliest known 
working kernel (adjacent tags) and other info.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: artful fips xenial
-- 
FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not 
found
https://bugs.launchpad.net/bugs/1809168
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to