[Bug 2081256] Re: RISC-V Installation with encrypted LVM boots into emergency mode

[Olivier Gayot]

I think we've been using /dev/disk/by-uuid in curtin since at least 2020
when https://wiki.ubuntu.com/FSTAB was written.

https://git.launchpad.net/curtin/commit/?id=941c43ffff233e55f8338991f2eeaa9932db91d8

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2081256

Title:
  RISC-V Installation with encrypted LVM boots into emergency mode

Status in curtin:
  Fix Committed
Status in subiquity package in Ubuntu:
  Fix Committed

Bug description:
  I used http://cdimage.ubuntu.com/ubuntu-server/daily-
  live/20240919.4/oracular-live-server-riscv64.img.gz using for testing
  https://iso.qa.ubuntu.com/qatracker/milestones/462/builds/313551.

  /snap/subiquity/6154 of version 24.10-devel+git327.24b14804 was used.

  I chose LVM with encryption.

  After rebooting I entered my decryption password I ended up in
  emergency mode:

  You are in emergency mode. After logging in, type "journalctl -xb" to view
  system logs, "systemctl reboot" to reboot, or "exit"

  
  root at vm:~# cat /etc/fstab
  # /etc/fstab: static file system information.
  #
  # Use 'blkid' to print the universally unique identifier for a
  # device; this may be used with UUID= as a more robust way to name devices
  # that works even if disks are added and removed. See fstab(5).
  #
  # <file system> <mount point>   <type>  <options>       <dump>  <pass>
  # / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
  /dev/disk/by-id/dm-uuid-LVM-dJdTlb6J7p86GHEsY9A5bITYjPyNVjgfmn2DukuR6VWgNo9IkR4nhYkUW3cHLuhh / ext4 defaults 0 1
  # /boot was on /dev/vdb2 during curtin installation
  /dev/disk/by-uuid/454e81c6-8bc0-4512-9f51-0a1f3f09a2e6 /boot ext4 defaults 0 1
  # /boot/efi was on /dev/vdb1 during curtin installation
  /dev/disk/by-path/platform-30000000.pci-pci-0000:00:03.0-part/by-uuid/D1D6-F967 /boot/efi vfat defaults 0 1
  root at vm:~# lsblk -f
  NAME FSTYPE FSVER LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
  vda                                                                           
  ├─vda1
  │    vfat   FAT32       D1D6-F967                                             
  ├─vda2
  │    ext4   1.0         454e81c6-8bc0-4512-9f51-0a1f3f09a2e6      1.5G     6% /boot
  └─vda3
    │  crypto 2           da319153-ca62-4c59-94ec-e5d0c1100dca                  
    └─dm_crypt-0
      │  LVM2_m LVM2        I0wgUi-0OLr-eVTa-miWp-UJ6V-Aik1-WGAG7z                
      └─ubuntu--vg-ubuntu--lv
         ext4   1.0         7cfb284d-1833-4e68-b4f3-1d2e7140c45d      6.9G    24% /

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/2081256/+subscriptions