#2052 Issue closed: kernel panic "VFS: Unable to mount root fs on unknown-block(0,0)" on HPE ProLiant DL380 Gen10 UEFI with backup on ISO

Labels: support / question, fixed / solved / done, special hardware or VM

jfucanada opened issue at 2019-02-22 21:40:

Relax-and-Recover (ReaR) Issue Template

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

  • ReaR version ("/usr/sbin/rear -V"):
    Relax-and-Recover 2.4 / Git

  • OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
    OS_VENDOR=RedHatEnterpriseServer
    OS_VERSION=7
    RHEL 7.6

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

MODULES=( 'all_modules' )
FIRMWARE_FILES=( 'yes' )
OUTPUT=ISO
OUTPUT_URL=file:///ReaR
BACKUP=NETFS
BACKUP_URL=iso:///ReaR
SSH_ROOT_PASSWORD="redhat"
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/ReaR' '/var/tmp' '/var/crash') #NETFS_KEEP_OLD_BACKUP_COPY=
  • Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):

BareMetal-HP DL380 UEFI

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
    x86
  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
    UEFI
  • Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
    SSD
  • Description of the issue (ideally so that others can reproduce it):
    We booted from ReaR ISO image and select Relax-and-Recover (no Secure Boot) the we got Kernel got panic
  • Workaround, if any:
    No
  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

gozora commented at 2019-02-22 22:14:

https://github.com/rear/rear/issues/2035 || please correctly fill the issue template ...

V.

jfucanada commented at 2019-02-23 00:10:

Where can I find beta version if it already included the fix?

jfucanada commented at 2019-02-23 00:30:

rear-screen-shot rear-screen-shot1

jsmeix commented at 2019-02-25 08:03:

@jfucanada
we need a "rear -D mkrescue/mkbackup" debug log file, cf.
https://github.com/rear/rear/blob/master/.github/ISSUE_TEMPLATE.md

https://github.com/rear/rear/issues/2035#issuecomment-465987439
describes how you can try out our current ReaR GitHub master code.

A kernel panic while the kernel of the ReaR recovery system starts up
is not related to https://github.com/rear/rear/issues/2035

I guess your kernel panic happens when the recovery system starts up
and not after "rear recover" finished and you rebooted and the kernel
of the recreated system starts up.

You did not describe your issue so that others (i.e. we) understand it, cf.
https://github.com/rear/rear/blob/master/.github/ISSUE_TEMPLATE.md

I do not have your hardware so that if your issue is specific on your
hardware there is nothing what I could do - but perhaps others might
be able to help you - provided your description is helpful for them.

When you have a Red Hat support contract you may also ask
the Red Hat support.

jfucanada commented at 2019-02-25 20:11:

rear-lnxcstsdsgg01.log

jfucanada commented at 2019-04-04 10:16:

This problem is fixed after we upgraded the firmware.

[Export of Github issue for rear/rear.]