New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IBM Power8 BareMetal rescue USB boot kernel panic: VFS Unable to mount root fs on unknown-block(1,0) #2243
Comments
@leonardottl I notice that in your
without the expected log messsage
that should normally come from usr/share/rear/output/default/950_copy_result_files.sh I am also missing
lines in your log file when running So I was wondering if before you did run But the log messages about
indicate that you had formatted your USB device for use with ReaR. Therefore I think the root cause is that scripts like
have the system architecture @schabrolles |
@jsmeix I currently never done any changes or test on OUTPUT=USB on Power. SO I think you point where the problem is ;-) |
Thank you both, @jsmeix and @schabrolles , I think you have identified the issue, thanks. Would you recommend I try to build the ISO output and try with that? |
Let me update that using the ISO OUTPUT allowed us to make bootable media and we are now performing the backup, I will update if all goes well. So til now it seems that the issue was the fact that for Power USB OUTPUT seems to not be supported. |
@leonardottl, just for a test, if you really want to boot on USB, you can try to copy the iso into a USB device with dd
WARNING, it will destroy all the data you have on the USB device. Tell le if it works |
in general regarding The USB specific parts in ReaR behave somewhat different In particular when you have your backup on USB things are different For some examples of USB specific issues that I found right now see But the most dangerous generic issue when using a USB disk By the way: If you like to try out if
|
Thank you @jsmeix for the detailed response, I think making the USB directly may be doable then. However, we decided to generate the ISO and burn it on the USB directly using dd as you also suggested, this worked fine! We have now made the backup successfully, but have one last question. Is it normal for mkbackup to not consider some files or directories, for instance we noticed that the home directory was not included in the tar backup file, is this correct? can we add a flag to also include it and others? Thank you for your time and help. |
ReaR runs the When you use btrfs subvolumes they behave like separated filesystems, see To specify explicitly what and only what is included in the backup you may use Another hint regarding architecture specific scripts:
For |
Dear @jsmeix and @schabrolles , we are still unable to get rear to backup the entire system, if you can comment on our issue it would be most appreciated, believe us that we are working on our side to solve it but just cannot find what we are doing wrong. To define which directories to include we are using: should these options force rear to backup the entire file system, or is something else required? |
Here is one example where we are using the EXCLUDE option instead, but still not getting all the directories, such as /home and others. I attach the local.conf and the log file from rear -Dv mkbackup OUTPUT=ISO |
@leonardottl
and
to get an overview of your block devices and filesystems structure In general when you use |
First, thanks again or the continued support. Here are the outputs and the disklayout file. |
Sorry, disklayout was missing
|
Ugh - looks somewhat complicated what is mounted there, I see nothing about Currently I have no idea why it is not included in the backup Is perhaps what appears as |
In fact home is just an example of a directory that is missing, in fact home is basically empty in our setup, because most of the work is done on containers, and stored on a data disk, so home is basically configuration stuff for each user, not much else. But other directories are also missing. Some other points to consider:
|
@leonardottl Perhaps it might even help you a bit nevertheless. Regarding huge files on a ISO i.e. with With current ReaR GitHub master code If you like to try that out see the section |
@leonardottl Please have a look there if I described the issue correctly. |
@jsmeix |
It is strange though because according to #2344 a PreP partition is missing, so the system should not even start booting, while here it starts booting and can not mount root. |
@pcahyna, the reason why the system can boot is because it is using petitboot (https://github.com/open-power/petitboot) used on Power BareMetal system (like LC models). |
@schabrolles thanks for the explanation. So it looks that this and #2344 are two different issues. |
Stale issue message |
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.5-git.3428.dbdfb5f.master.changed / 2019-09-17
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=USB
AUTOEXCLUDE_MULTIPATH=n
USB_DEVICE_PARTED_LABEL=mbrar'
BACKUP=NETFS
BACKUP_URL=usb:///dev/disk/by-label/REAR-000
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
IBM Power 8, Bear Metal: IBM Power System S822LC (8335-GTB)
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
ppc64el
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
OP820.30 - PNOR OP8_v1.12_2.96 / BMC 2.13.104548 and Petitboot
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local Disk SSD/Docker
Description of the issue (ideally so that others can reproduce it):
After building the mkrescue on a USB, booting from the USB, the boot up process crashes with the following information, which states a kernel panic error VFS Unable to mount root fs on unknown-block(1,0):
Workaround, if any: None
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
here are the output from the mkrescue :
Here is the log file:
rear-koza.log
The text was updated successfully, but these errors were encountered: