"Gave up waiting for root file system device" after fresh installation of Ubuntu 22.04

[Floris Luiten]

After running the 22.04 installer, my laptop would restart and after seeing the initial loading screen I'm dropped to a busybox shell. It makes no difference what boot option I use from my UEFI or installing with or without disk encrpytion.

The installer finds my disk without problems, but afer rebooting the Ubuntu screen hangs for around a minute before dropping me into a busybox shell.

In this shell I do the following:

```
# ls /dev/mapper
control isw_behfgagcfc_ASUS_OS

# kpartx -av /dev/mapper/isw_behfgagcfc_ASUS_OS
add map isw_behfgagcfc_ASUS_OS1 (253:1): 0 1048576 linear 253:0 2048
add map isw_behfgagcfc_ASUS_OS2 (253:2): 0 3500032 linear 253:0 1050624
add map isw_behfgagcfc_ASUS_OS3 (253:3): 0 495579136 linear 253:0 4550656

# cryptsetup luksOpen /dev/mapper/isw_behfgagcfc_ASUS_OS3 WHYEVER
Enter passphrase for /dev/mapper/isw_behfgagcfc_ASUS_OS3: ***

# exit
```

After which the Ubuntu loading screen re-appears and I have to enter the disk decrypt key again. Then my system boots fine, but I think it's a bug to have these commands to manually every time.

If I install without disk-encryption, I still have to run "kpartx -av /dev/mapper/isw_behfgagfc_ASUS_OS" in the busybox shell before I'm able to continue.

Attached the log from apport inside the finally booted Ubuntu installation with disk-encryption on.

PS: The same error occurs when upgrading from from 21.10 to 22.04.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2008892/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Langasek (vorlon)]

plymouth is only responsible for the splash screen, it has nothing to do with why you've ended up at a shell. Reassigning to mdadm as a starting point.

What is /dev/mapper/isw_behfgagcfc_ASUS_OS? I don't recognize this as a standard name and don't know what package is supposed to configure it at boot time.

[Floris Luiten (florisluiten)]

Thanks for the the reassignment of the package, I had a hard time guessing which one to pick :-)

My laptop (Asus Zenbook UX301) has 2 256 GB SSD disks in a RAID setup. Once booted and running `lsblk` I see isw_behfgagcfc_ASUS_OS as a type "dmraid"; with isw_behfgagcfc_ASUS_OS1, isw_behfgagcfc_ASUS_OS2 and isw_behfgagcfc_ASUS_OS1 as children with type "part".

[Steve Langasek (vorlon)]

Ok, reassigning to dmraid, thanks.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[TQ (nothinrandom)]

I also see the same after migration from 20.04.4/20.04.5 to 22.04.1 via dist-upgrade, or even on a fresh installation of 22.04.2. Even changed some settings in BIOS (e.g. Intel RST to AHCI), but no dice.

[Panagiotis Keramitzis (pkera)]

It hit me as well.

[TQ (nothinrandom)]

Hello ubuntu-dmraid team,

Any updates on this issue? It seems to manifest in both upgrading (e.g. 20.04.2 -> 22.04.2) and a fresh install (22.04.2). I'm not sure why the importance of this ticket is still undecided. Is there at least a workaround other than the aformentioned approach of mapping partitions via kpart?

Thanks