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.

** Changed in: plymouth (Ubuntu)
       Status: New => Incomplete

** Package changed: plymouth (Ubuntu) => mdadm (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2008892

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

Status in mdadm package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/2008892/+subscriptions


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

Reply via email to