You are not logged in.

#1 2022-11-21 21:02:39

Tirigon
Member
Registered: 2020-07-03
Posts: 4

Stuck on emergency shell after kernel upgrade

Hey guys,

really need your help, because I read so many articles but cannot find the solution.

Base config

Running 5.19.13-arch1-1 on a Lenovo Thinkpad.
Unencrypted boot partition, fully encrypted root partition (LVM on LUKS).
Using systemd-boot for booting, secure boot is on.

Issue

When upgrading to latest 6.X kernel the upgrades runs through, initramfs gets generated, sbctl signs new kernel, but upon reboot I'm stuck in the emergency shell, stating that boot partition cannot be mounted due to unknown FS type vfat.

Detailed infos about system BEFORE upgrade

/etc/fstab

 
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/SG1-root
UUID=dc62db58-1f09-4a5e-a910-7ca03cc9a127	/         	ext4      	rw,relatime,stripe=32	0 1

# /dev/mapper/SG1-home
UUID=5c50f37b-730a-4e80-b418-b6764dc29a55	/home     	ext4      	rw,relatime,stripe=32	0 2

# /dev/nvme0n1p1
UUID=61C0-A1CA      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/mapper/SG1-swap
UUID=ed4ea7fc-6d30-45e1-99a6-a3e2db0eb176	none      	swap      	defaults  	0 0

lsblk

NAME           MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINTS
nvme0n1        259:0    0 465.8G  0 disk
├─nvme0n1p1    259:1    0   400M  0 part  /boot
└─nvme0n1p2    259:2    0 465.4G  0 part
  └─cryptlvm   254:0    0 465.4G  0 crypt
    ├─SG1-swap 254:1    0    32G  0 lvm   [SWAP]
    ├─SG1-root 254:2    0   128G  0 lvm   /
    └─SG1-home 254:3    0 290.1G  0 lvm   /home

ls -l /boot

total 85852
drwxr-xr-x 7 root root     4096 Oct 10 21:30 EFI
-rwxr-xr-x 1 root root 47518946 Nov 21 21:28 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root 23623825 Nov 21 21:28 initramfs-linux.img
-rwxr-xr-x 1 root root  5678080 Nov  8 20:02 intel-ucode.img
drwxr-xr-x 3 root root     4096 Nov 21 21:35 loader
-rwxr-xr-x 1 root root 11075504 Nov 21 21:28 vmlinuz-linux

ls -l /boot/EFI/Linux

-rwxr-xr-x 1 root root 39093808 Oct  9 21:38 d6391c01b56d4743a7b501f29ead1915-linux-arch.efi

sbctl verify

Verifying file database and EFI images in /boot...
✓ /boot/EFI/systemd/systemd-bootx64.efi is signed
✓ /boot/vmlinuz-linux is signed
✓ /boot/EFI/BOOT/BOOTX64.EFI is signed
✓ /boot/EFI/Linux/d6391c01b56d4743a7b501f29ead1915-linux-arch.efi is signed

/etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect keyboard keymap consolefont modconf block encrypt lvm2 filesystems resume fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
Errors AFTER upgrading

journalctl -b -1

...
Nov 21 21:29:41 earth systemd-modules-load[495]: Failed to find module 'crypto_user'
Nov 21 21:29:41 earth systemd-modules-load[495]: Failed to find module 'i2c-dev'
...
Nov 21 21:29:41 earth systemd[1]: Found device /dev/disk/by-uuid/5c50f37b-730a-4e80-b418-b6764dc29a55.
Nov 21 21:29:41 earth systemd[1]: Found device /dev/disk/by-uuid/ed4ea7fc-6d30-45e1-99a6-a3e2db0eb176.
Nov 21 21:29:41 earth systemd[1]: Activating swap /dev/disk/by-uuid/ed4ea7fc-6d30-45e1-99a6-a3e2db0eb1>
Nov 21 21:29:41 earth systemd[1]: Starting File System Check on /dev/disk/by-uuid/5c50f37b-730a-4e80-b>
Nov 21 21:29:41 earth systemd[1]: Activated swap /dev/disk/by-uuid/ed4ea7fc-6d30-45e1-99a6-a3e2db0eb17>
Nov 21 21:29:41 earth systemd[1]: Reached target Swaps.
Nov 21 21:29:41 earth kernel: Adding 33554428k swap on /dev/mapper/SG1-swap.  Priority:-2 extents:1 ac>
Nov 21 21:29:41 earth systemd[1]: Found device Samsung SSD 980 500GB EFI.
Nov 21 21:29:41 earth systemd[1]: Starting File System Check on /dev/disk/by-uuid/61C0-A1CA...
Nov 21 21:29:41 earth systemd-fsck[557]: /dev/mapper/SG1-home: clean, 18454/19013632 files, 1989412/76>
Nov 21 21:29:41 earth systemd[1]: Finished File System Check on /dev/disk/by-uuid/5c50f37b-730a-4e80-b>
Nov 21 21:29:41 earth audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sys>
Nov 21 21:29:41 earth systemd-fsck[560]: fsck.fat 4.2 (2021-01-31)
Nov 21 21:29:41 earth systemd-fsck[560]: /dev/nvme0n1p1: 21 files, 31073/102196 clusters
Nov 21 21:29:41 earth systemd[1]: Finished File System Check on /dev/disk/by-uuid/61C0-A1CA.
Nov 21 21:29:41 earth audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=sys>
Nov 21 21:29:42 earth systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting any>
Nov 21 21:29:42 earth systemd[1]: Mounting /boot...
Nov 21 21:29:42 earth systemd[1]: Mounting /home...
Nov 21 21:29:42 earth mount[578]: mount: /boot: unknown filesystem type 'vfat'.
Nov 21 21:29:42 earth mount[578]:        dmesg(1) may have more information after failed mount system >
Nov 21 21:29:42 earth systemd[1]: Mounting Temporary Directory /tmp...
Nov 21 21:29:42 earth systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped be>
Nov 21 21:29:42 earth systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Nov 21 21:29:42 earth systemd[1]: boot.mount: Failed with result 'exit-code'.
Nov 21 21:29:42 earth systemd[1]: Failed to mount /boot.
Nov 21 21:29:42 earth systemd[1]: Dependency failed for Local File Systems.
My findings/What I checked
  1. Checking that boot partition is actually mounted when performing the upgrade : done

  2. Checking that fstab has the correct entries : done

  3. Checking that all files are correctly signed for secure boot : done

  4. Making sure to use the same version of kernel, headers, modules : done

Can someone please help me find the cause of this annoying issue?
Thanks a lot!

Offline

#2 2022-11-21 21:18:57

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 17,728

Re: Stuck on emergency shell after kernel upgrade

Look at your systemd-boot entries, this kind of error usually means you aren't starting the kernel you installed but instead booted an older variant.

 Directory /boot to mount over is not empty, mounting any

is usually a good indicator, you likely experimented something and are now actually booting off of whatever is on there/potentially not even using systemd-boot. Output of

efibootmgr -uv

?

Last edited by V1del (2022-11-21 21:22:19)

Offline

#3 2022-11-22 07:51:38

Tirigon
Member
Registered: 2020-07-03
Posts: 4

Re: Stuck on emergency shell after kernel upgrade

Thanks for your fast answer!

---

efibootmgr -uv

BootCurrent: 0003
Timeout: 0 seconds
BootOrder: 0003,0002,0001,0000,001A,001B,001C,001D,001E,001F,0020,0021,0022
Boot0000* Windows Boot Manager	HD(2,MBR,0x801254ad,0x185800,0x7800)/File(\EFI\Microsoft\Boot\bootmgfw.efi)䥗䑎坏S
      dp: 04 01 2a 00 02 00 00 00 00 58 18 00 00 00 00 00 00 78 00 00 00 00 00 00 ad 54 12 80 00 00 00 00 00 00 00 00 00 00 00 00 01 01 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 73 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot0001* rEFInd Boot Manager	HD(1,GPT,18b2a515-480d-0346-acad-5463a27c49f7,0x800,0xfa000)/File(\EFI\refind\refind_x64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 a0 0f 00 00 00 00 00 15 a5 b2 18 0d 48 46 03 ac ad 54 63 a2 7c 49 f7 02 02 / 04 04 3a 00 5c 00 45 00 46 00 49 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5f 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0002* rEFInd Boot Manager	HD(1,GPT,c9988c84-6533-42b3-a095-eb0625db3ef4,0x800,0xc8000)/File(\EFI\refind\refind_x64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 80 0c 00 00 00 00 00 84 8c 98 c9 33 65 b3 42 a0 95 eb 06 25 db 3e f4 02 02 / 04 04 3a 00 5c 00 45 00 46 00 49 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5c 00 72 00 65 00 66 00 69 00 6e 00 64 00 5f 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0003* Linux Boot Manager	HD(1,GPT,c9988c84-6533-42b3-a095-eb0625db3ef4,0x800,0xc8000)/File(\EFI\systemd\systemd-bootx64.efi)
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 80 0c 00 00 00 00 00 84 8c 98 c9 33 65 b3 42 a0 95 eb 06 25 db 3e f4 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 5c 00 73 00 79 00 73 00 74 00 65 00 6d 00 64 00 2d 00 62 00 6f 00 6f 00 74 00 78 00 36 00 34 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
      dp: 04 06 14 00 66 8b 1c 72 6c 42 86 4e 8e 99 34 57 c4 6a b0 b9 / 7f ff 04 00
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
      dp: 04 06 14 00 2d 76 6a 12 58 57 ca 4f 85 31 20 1a 7f 57 f8 50 / 7f ff 04 00
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
      dp: 04 06 14 00 a6 d9 d8 a7 b0 6a eb 4a ad 9d 16 3e 59 a7 a3 80 / 7f ff 04 00
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
      dp: 04 06 14 00 5b 61 7e 3f 45 0d 80 4f 88 dc 26 b2 34 95 85 60 / 7f ff 04 00
Boot0014  Asset Information	FvFile(da465b87-a26f-4c12-b78a-0361428fa026)
      dp: 04 06 14 00 87 5b 46 da 6f a2 12 4c b7 8a 03 61 42 8f a0 26 / 7f ff 04 00
Boot0015  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
      dp: 04 06 14 00 a0 92 8c 47 22 26 b7 42 a6 5d 58 94 16 9e 4d 24 / 7f ff 04 00
Boot0016  ThinkShield secure wipe	FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
      dp: 04 06 14 00 d5 a0 93 35 52 bd a0 43 80 8e cb ff 5e ce 24 77 / 7f ff 04 00
Boot0017  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
      dp: 04 06 14 00 f4 e6 6e f4 85 47 a3 43 92 3d 7f 78 6c 3c 84 79 / 7f ff 04 00
Boot0018  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
      dp: 04 06 14 00 60 3f 5d 66 3e ad ad 4c 8e 26 db 46 ee e9 f1 b5 / 7f ff 04 00
Boot0019  MEBx Hot Key	FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
      dp: 04 06 14 00 6a d5 6f ac 41 3d fd 4e a1 b9 87 02 93 81 1a 28 / 7f ff 04 00
Boot001A* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 86 70 12 96 aa 5a 78 48 b6 6c d4 9d d3 ba 6a 55 / 7f ff 04 00
Boot001B* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 6f f0 15 a2 88 30 b5 43 a8 b8 64 10 09 46 1e 49 / 7f ff 04 00
Boot001C* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 00 1c 19 99 32 d9 4c 4e ae 9a a0 b6 e9 8e b8 a4 00 / 7f ff 04 00
Boot001D* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 33 e8 21 aa af 33 bc 47 89 bd 41 9f 88 c5 08 03 / 7f ff 04 00
Boot001E* PXE BOOT	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 78 a8 4a af 2b 2a fc 4e a7 9c f5 cc 8f 3d 38 03 / 7f ff 04 00
Boot001F* LENOVO CLOUD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ad 38 cc bb f7 ed f0 4d 95 9c f4 2a a7 4d 36 50 / 03 18 3b 00 68 74 74 70 73 3a 2f 2f 64 6f 77 6e 6c 6f 61 64 2e 6c 65 6e 6f 76 6f 2e 63 6f 6d 2f 70 63 63 62 62 73 2f 63 64 65 70 6c 6f 79 2f 65 66 69 2f 62 6f 6f 74 2e 65 66 69 / 7f ff 04 00
Boot0020* ON-PREMISE	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri()
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ad 38 cc bb f7 ed f0 4d 95 9c f4 2a a7 4d 36 50 / 03 18 04 00 / 7f ff 04 00
Boot0021  Other CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a35400)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 00 / 7f ff 04 00
Boot0022  Other HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
      dp: 03 0a 25 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 00 / 7f ff 04 00
Boot0023* IDER BOOT CDROM	PciRoot(0x0)/Pci(0x14,0x0)/USB(11,1)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 0b 01 / 7f ff 04 00
Boot0024* IDER BOOT Floppy	PciRoot(0x0)/Pci(0x14,0x0)/USB(11,0)
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 0b 00 / 7f ff 04 00
Boot0025* ATA HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b 91 af 62 59 56 44 9f 41 a7 b9 1f 4f 89 2a b0 f6 / 7f ff 04 00
Boot0026* ATAPI CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
      dp: 03 0a 24 00 d2 38 78 bc 82 0f 60 4d 83 16 c0 68 ee 79 d2 5b ae a2 09 0a df de 21 4e 8b 3a 5e 47 18 56 a3 54 / 7f ff 04 00

/boot/EFI/loader/loader.conf

default arch.conf
timeout 4
console-mode max
editor no

/boot/EFI/loader/entries/arch.conf

title   Arch Linux
linux   /vmlinuz-linux
initrd  /intel-ucode.img
initrd  /initramfs-linux.img
options root=UUID=dc62db58-1f09-4a5e-a910-7ca03cc9a127 ro cryptdevice=UUID=be1601d3-80b5-4e07-a977-2bd1ec206c7a:cryptlvm
options resume=UUID=ed4ea7fc-6d30-45e1-99a6-a3e2db0eb176

---

From the first output I see that there are still old bootloader entries in efivars, but they are not installed anymore (removed rEFInd).
According to sbctl the efi file is signed and didn't change with the current upgrade.

Offline

#4 2022-11-23 00:58:01

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 6,851

Re: Stuck on emergency shell after kernel upgrade

Compare the version of the kernel in /boot with the kernel installed on the system.

file /boot/vmlinuz-linux
pacman -Qi linux

Modify as appropriate if you're using a different kernel.

If the versions differ, you need to reinstall linux (or other kernel package).

pacman -S linux

Make sure that /boot is mounted correctly first. You can do this by arch-chrooting from the live ISO.


CLI Paste | How To Ask Questions

Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L

Offline

#5 2022-11-23 17:02:58

Tirigon
Member
Registered: 2020-07-03
Posts: 4

Re: Stuck on emergency shell after kernel upgrade

Reinstalling the kernel from arch-iso didn't help at all, leads to the same issue (I did smile )

However, what I've found... After the upgrade, there are 2 kernals. One is located at nvme0n1p1 (the new one, 6.x, because when executing the upgrade, this partition is mounted as /boot) and the other is located at /dev/mapper/SG1-root/boot (this is the old one from my initial install).

When booting after the upgrade, the cryptdevice gets correctly unlocked, /dev/mapper/SG1-root is mounted as root, but /dev/nvme0n1p1 is never mounted as /boot. Therefore it seems to me the older kernel residing at /dev/mapper/SG1-root/boot is used.

So I am really out of ideas. How do I get my system to mount the right partition?? (Remember, it IS mounted correctly during upgrade).

Offline

#6 2022-11-23 17:06:05

Scimmia
Fellow
Registered: 2012-09-01
Posts: 9,828

Re: Stuck on emergency shell after kernel upgrade

If it's mounted correctly, then the problem is that the bootloader is loading it from the wrong location. Reinstall/reconfigure it.

Offline

Board footer

Powered by FluxBB