#3550 Issue closed: UEFI Boot: Kernel panic with previous "No file system could mount root, tried:"¶
Labels: bug
hpannenb opened issue at 2026-01-09 12:41:¶
ReaR version¶
Relax-and-Recover 2.8 / 2024-12-19
Describe the ReaR bug in detail¶
Booting the rescue image ISO as virtual media on a Dell R640 with iDRAC9
will lead to a kernel panic.
Platform¶
Linux x64
OS version¶
Red Hat Enterprise Linux 8.10 (Ootpa)
Backup¶
AVA
Storage layout¶
NAME KNAME PKNAME TRAN TYPE FSTYPE LABEL SIZE MOUNTPOINT
/dev/sda /dev/sda disk 2.2T
|-/dev/sda1 /dev/sda1 /dev/sda part vfat 200M /boot/efi
|-/dev/sda2 /dev/sda2 /dev/sda part ext2 800M /boot
|-/dev/sda3 /dev/sda3 /dev/sda part LVM2_member 2.2T
| |-/dev/mapper/lvm01-root.vol /dev/dm-0 /dev/sda3 lvm xfs 6G /
| |-/dev/mapper/lvm01-swap.vol /dev/dm-1 /dev/sda3 lvm swap 16G [SWAP]
| |-/dev/mapper/lvm01-usr.vol /dev/dm-2 /dev/sda3 lvm xfs 6.9G /usr
| |-/dev/mapper/lvm01-reserved--snapshot /dev/dm-4 /dev/sda3 lvm ext4 3.9G
| |-/dev/mapper/lvm01-tmp.vol /dev/dm-5 /dev/sda3 lvm xfs 2G /tmp
| |-/dev/mapper/lvm01-opt.vol /dev/dm-6 /dev/sda3 lvm xfs 4G /opt
| |-/dev/mapper/lvm01-varlogaudit.vol /dev/dm-7 /dev/sda3 lvm xfs 1000M /var/log/audit
| |-/dev/mapper/lvm01-varlog.vol /dev/dm-8 /dev/sda3 lvm xfs 1000M /var/log
| |-/dev/mapper/lvm01-vartmp.vol /dev/dm-9 /dev/sda3 lvm xfs 3G /var/tmp
| |-/dev/mapper/lvm01-var.vol /dev/dm-10 /dev/sda3 lvm xfs 40G /var
| |-/dev/mapper/lvm01-home.vol /dev/dm-11 /dev/sda3 lvm xfs 5G /home
| |-/dev/mapper/lvm01-vmts2smssv202--lc2--root /dev/dm-12 /dev/sda3 lvm 60G
| |-/dev/mapper/lvm01-vmts2smssv202--fc3--root-real /dev/dm-13 /dev/sda3 lvm 60G
| | |-/dev/mapper/lvm01-vmts2smssv202--fc3--root /dev/dm-15 /dev/dm-13 lvm 60G
| | `-/dev/mapper/lvm01-vmts2smssv202--fc3--root_snap /dev/dm-20 /dev/dm-13 lvm 60G
| |-/dev/mapper/lvm01-vmts2smssv202--fc3--root_snap-cow /dev/dm-18 /dev/sda3 lvm 60G
| | `-/dev/mapper/lvm01-vmts2smssv202--fc3--root_snap /dev/dm-20 /dev/dm-18 lvm 60G
| |-/dev/mapper/lvm01-vmts2smssv202--fc4--root /dev/dm-24 /dev/sda3 lvm 60G
| |-/dev/mapper/lvm01-backup.vol /dev/dm-25 /dev/sda3 lvm xfs 30G /backup
| |-/dev/mapper/lvm01-vmts2smssv202--ay2--root /dev/dm-26 /dev/sda3 lvm 60G
| `-/dev/mapper/lvm01-vmts2smssv202--ay4--root /dev/dm-27 /dev/sda3 lvm 60G
`-/dev/sda4 /dev/sda4 /dev/sda part 512B
/dev/sdb /dev/sdb disk 4.4T
`-/dev/sdb1 /dev/sdb1 /dev/sdb part LVM2_member 4.4T
|-/dev/mapper/lvm02-vmts2smssv202--lc2_disk01 /dev/dm-3 /dev/sdb1 lvm 86G
|-/dev/mapper/lvm02-vmts2smssv202--fc3_disk01-real /dev/dm-14 /dev/sdb1 lvm 88G
| |-/dev/mapper/lvm02-vmts2smssv202--fc3_disk01 /dev/dm-16 /dev/dm-14 lvm 88G
| `-/dev/mapper/lvm02-vmts2smssv202--fc3_disk01_snap /dev/dm-19 /dev/dm-14 lvm 88G
|-/dev/mapper/lvm02-vmts2smssv202--fc3_disk01_snap-cow /dev/dm-17 /dev/sdb1 lvm 88G
| `-/dev/mapper/lvm02-vmts2smssv202--fc3_disk01_snap /dev/dm-19 /dev/dm-17 lvm 88G
|-/dev/mapper/lvm02-vmts2smssv202--fc4_disk01 /dev/dm-21 /dev/sdb1 lvm 88G
|-/dev/mapper/lvm02-ts2smssv202_ay2_disk1 /dev/dm-22 /dev/sdb1 lvm 1.4T
`-/dev/mapper/lvm02-ts2smssv202_ay4_disk1 /dev/dm-23 /dev/sdb1 lvm 1.4T
What steps will reproduce the bug?¶
- Create a rescue image ISO
- Boot ISO via iDRAC and Virtual Media => kernel panic.
(- Boot ISO e.g. in a Virtual Box VM with EFI => No issue.)
Workaround, if any¶
Not known.
Additional information¶
The site.confin use is
## Avamar agent installation for your system
#
# export TMPDIR="/var/ReaR" # Required to be mounted EXEC (!!!)
AVAMAR_ROOTDIR=/usr/local/avamar
AVAMAR_VARDIR=/var/avamar
AVAMAR_ETCDIR=/etc/avamar
# rear staff
ISO_DIR=/var/ReaR
OUTPUT=ISO
BACKUP=AVA00
# Static IP (no DHCP!)
USE_DHCLIENT=
USE_STATIC_NETWORK=yes
USE_RESOLV_CONF=( 'no' )
# Include the loaded kernel modules only
MODULES=( 'all_modules' )
# Set ROOT Password (optional)
SSH_ROOT_PASSWORD='root'
# Clone all current users
CLONE_ALL_USERS_GROUPS=no
# On the host do *NOT* exclude disks for the guests
AUTOEXCLUDE_DISKS=no
# UEFI required - Ref.to. https://access.redhat.com/solutions/7054402
UEFI_BOOTLOADER=/boot/efi/EFI/redhat/grubx64.efi
SECURE_BOOT_BOOTLOADER=/boot/efi/EFI/redhat/shimx64.efi
###
# Avamar specific extensions
COPY_AS_IS_AVA00=( "$AVAMAR_ROOTDIR" "$AVAMAR_VARDIR" "$AVAMAR_ETCDIR" )
COPY_AS_IS_EXCLUDE_AVA00=( "$AVAMAR_VARDIR/*.log" "$AVAMAR_VARDIR/*.dat" "$AVAMAR_VARDIR/clientlogs/*" )
PROGS_AVA00=( avtar avregister avagent.bin avscc avupdate detect_firewall avtar.bin )
# End Avamar specific extensions
The AVA00 is a slightly different AVA workflow with us.
pcahyna commented at 2026-01-09 12:49:¶
I am afraid the problem is outside ReaR, see #3186 for ideas and possible workarounds.
hpannenb commented at 2026-01-09 13:05:¶
Happy New Year @pcahyna Thanks for the fast response. I need to take a look at it.
hpannenb commented at 2026-01-09 14:30:¶
Looking at the references given I applied a minor config change in our
site.conf which makes the boot working for us:
MODULES=( 'loaded_modules' )
...
REAR_INITRD_COMPRESSION="lzma"
Edit: It is also working with just the compression change in our case. I will close the issue. Thanks.
[Export of Github issue for rear/rear.]