Proxmox Kernel Panic: Unable to mount root fs ("Cannot open root device")

Anodin67

Member
May 25, 2023
3
0
6
Hello,

I updated my PVE node, and after rebooting, I can't boot. Booting no longer works.
I tried rescue mode, but I get to
Bash:
root@proxmox:/#
on the USB drive; I'm limited.


On usb key rescue :
Bash:
root@proxmox:/# view /boot/
System.map-6.14.8-2-pve config-6.14.8-2-pve vmlinuz-6.14.8-2-pve
root@proxmox:/# proxmox-boot-tool kernel list
Manually selected kernels:
None.

Automatically selected kernels:
6.14.8-2-pve
root@proxmox:/# lsblk
NAME                    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                     7:0    0 108.7M  1 loop
loop1                     7:1    0 521.8M  1 loop
sda                       8:0    1  57.7G  0 disk /cdrom
|-sda1                    8:1    1   282K  0 part
|-sda2                    8:2    1     8M  0 part
|-sda3                    8:3    1   1.5G  0 part
`-sda4                    8:4    1   300K  0 part
nvme0n1                 259:0    0 953.9G  0 disk
|-nvme0n1p1             259:1    0  1007K  0 part
|-nvme0n1p2             259:2    0     1G  0 part
|-nvme0n1p3             259:3    0    59G  0 part
| |-pve-swap            252:1    0   7.3G  0 lvm
| |-pve-root            252:3    0  24.9G  0 lvm
| |-pve-data_tmeta      252:17   0    1G  0 lvm
| |-pve-data_tdata      252:18   0  17.6G  0 lvm
| `-pve-data             252:19   0  17.6G  0 lvm
`-nvme0n1p4             259:4    0 893.9G  0 part
  |-fast1-vm--100--disk--0 252:0  0    4M  0 lvm
  |-fast1-vm--100--disk--1 252:2  0  250G  0 lvm
  ... (et autres volumes logiques pour VMs) ...
root@proxmox:/#


On grub :
Bash:
                                GNU GRUB version 2.06-13+pmx7

setparams 'Proxmox VE GNU/Linux'

        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_gpt
        insmod lvm
        insmod ext2
        set root='lvmid/MNlzfj-MX3m-hOa9-STe6-Xv19-4NsO-MXFxfi/rESs99c-vpkR-2BEz-tmNT-DXmL-aGtC-vXFYr9'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint='lvmid/MNlzfj-MX3m-hOa9-STe6-Xv19-4NsO-MXFxfi/rESs99c-vpkR-2BEz-tmNT-DXmL-aGtC-vXFYr9' 9be63bbf-19ea-4b63-a342-28147829b75d
        else
          search --no-floppy --fs-uuid --set=root 9be63bbf-19ea-4b63-a342-28147829b75d
        fi
        echo    'Loading Linux 6.8.12-15-pve ...'
        linux   /boot/vmlinuz-6.8.12-15-pve root=/dev/mapper/pve-root ro intel_iommu=on iommu=pt i915.enable_guc=3 i915.max_vfs=7

This is the kernel boot :
Bash:
[ 0.725293] Loading compiled-in X.509 certificates
[ 0.725678] Loaded X.509 cert 'Build time autogenerated kernel key: 40a53614f45e22115e3612fc8dd4dfc41d60a9d3d'
[ 0.727376] Key type .fscrypt registered
[ 0.727429] Key type fscrypt-provisioning registered
[ 0.727512] Key type trusted registered
[ 0.728936] Key type encrypted registered
[ 0.728951] AppArmor: AppArmor sha256 policy hashing enabled
[ 0.729225] integrity: Loading X.509 certificate: UEFI:db
[ 0.729267] integrity: Loaded X.509 cert 'MINISFORUM OWN CA: 815a459eeaeb7a9e42fabf9897858520'
[ 0.729287] integrity: Loading X.509 certificate: UEFI:db
[ 0.729312] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd'
[ 0.730576] integrity: Loading X.509 certificate: UEFI:db
[ 0.733631] Loaded X.509 cert 'Build time autogenerated kernel key: 40a53614f45e22115e3612fc8dd4dfc41d60a9d3d'
[ 0.734261] ima: Allocated hash algorithm: sha256
[ 0.752088] ima: No architecture policies found
[ 0.752525] evm: Initialising EVM extended attributes:
[ 0.752963] evm: security.selinux
[ 0.753548] evm: security.SMACK64
[ 0.753960] evm: security.SMACK64EXEC
[ 0.754557] evm: security.SMACK64TRANSMUTE
[ 0.754966] evm: security.SMACK64MMAP
[ 0.755571] evm: security.apparmor
[ 0.755984] evm: security.ima
[ 0.756585] evm: security.capability
[ 0.757002] evm: HMAC attrs: 0x1
[ 0.758132] PM: Magic number: 13:13:827
[ 0.758803] misc hw_random: hash matches
[ 0.763120] RAS: Correctable Errors collector initialized.
[ 0.763856] clk: Disabling unused clocks
[ 0.764579] md: Waiting for all devices to be available before autodetect
[ 0.765212] md: if you don't use raid, use raid=noautodetect
[ 0.765812] md: Autodetecting RAID arrays.
[ 0.766451] md: autorun ...
[ 0.767013] md: ... autorun DONE.
[ 0.768001] /dev/root: Can't open blockdev
[ 0.768641] VFS: Cannot open root device "/dev/mapper/pve-root" or unknown-block(0,0): error -6
[ 0.769241] Please append a correct "root=" boot option; here are the available partitions:
[ 0.769813] List of all bdev filesystems:
[ 0.770506] ext3
[ 0.770507] ext2
[ 0.771086] ext4
[ 0.771658] squashfs
[ 0.772254] vfat
[ 0.772787] fuseblk
[ 0.773377]
[ 0.774514] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.775035] CPU: 7 PID: 1 Comm: swapper/0 Not tainted 6.8.12-15-pve #1
[ 0.775653] Hardware name: Micro Computer(HK) Tech Limited Venus series/AHBNB, BIOS 1.00 01/03/2024
[ 0.776283] Call Trace:

Can you help me please
 
Last edited: