#3324 Issue `open`: Creating BMR ISO for Rubrik Recovery¶

Labels: support / question, external tool

RLDuckworth opened issue at 2024-09-30 18:42:¶

ReaR version ("/usr/sbin/rear -V"): Relax-and-Recover 2.7 / Git
If your ReaR version is not the current version, explain why you can't upgrade: N/A
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): RHEL7.9, planning on In Place upgrade to RHEL8
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=ISO
BACKUP=CDM
UEFI_BOOTLOADER=/boot/efi/EFI/redhat/grubx64.efi
SECURE_BOOT_BOOTLOADER=/boot/efi/EFI/redhat/shimx64.efi

Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR): Lenovo SR630
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): UEFI / GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): SSD
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):

-sh-4.2# lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT
NAME                              KNAME     PKNAME    TRAN   TYPE FSTYPE      LABEL         SIZE MOUNTPOINT
/dev/sda                          /dev/sda            sata   disk                         119.2G
|-/dev/sda1                       /dev/sda1 /dev/sda         part vfat                     1015M /boot/efi
|-/dev/sda2                       /dev/sda2 /dev/sda         part xfs                         1G /boot
`-/dev/sda3                       /dev/sda3 /dev/sda         part LVM2_member             117.2G
  |-/dev/mapper/vg0-root          /dev/dm-0 /dev/sda3        lvm  xfs                        20G /
  |-/dev/mapper/vg0-swap          /dev/dm-1 /dev/sda3        lvm  swap                        8G [SWAP]
  |-/dev/mapper/vg0-usr           /dev/dm-2 /dev/sda3        lvm  xfs                         5G /usr
  |-/dev/mapper/vg0-home          /dev/dm-3 /dev/sda3        lvm  xfs                         5G /home
  |-/dev/mapper/vg0-var           /dev/dm-4 /dev/sda3        lvm  xfs                        20G /var
  |-/dev/mapper/vg0-tmp           /dev/dm-5 /dev/sda3        lvm  xfs                        10G /tmp
  |-/dev/mapper/vg0-var_log       /dev/dm-6 /dev/sda3        lvm  xfs                         5G /var/log
  |-/dev/mapper/vg0-var_log_audit /dev/dm-7 /dev/sda3        lvm  xfs                         5G /var/log/audit
  |-/dev/mapper/vg0-var_tmp       /dev/dm-8 /dev/sda3        lvm  xfs                         5G /var/tmp
  `-/dev/mapper/vg0-opt           /dev/dm-9 /dev/sda3        lvm  xfs                         5G /opt
/dev/sdb                          /dev/sdb            usb    disk                          14.9G
`-/dev/sdb1                       /dev/sdb1 /dev/sdb         part vfat        RHEL-7_9 SE  14.9G

Description of the issue (ideally so that others can reproduce it):

This is my first time working with ReaR. I'm working with a "test" system and running through the "rear -v mkrescue" and it appears the iso is being written but I'm getting three errors or "warning" messages. It looks like It'd be safe to delete the symlinks in message 1, but I'd like to verify that it's safe to delete the symlink for message 2, or does it need to link to a valid grub.cfg file? Does the warning in message 3 need to be or can it be corrected?

Message 1) Failed to copy all contents of /lib/modules/3.10.0-1160.119.1.el7.x86_64 (dangling symlinks could be a reason)
Since there the symbolic link point to non-existent files (there are 4 of them).

Message 2) Broken symlink '/etc/grub2.cfg' in recovery system because 'readlink' cannot determine its link target
lrwxrwxrwx. 1 root root 22 Sep 26 08:37 /etc/grub2.cfg -> ../boot/grub2/grub.cfg
The target link does not exist, the only thing in /etc/grub2 is grubenv.

Message 3) Did not find /boot/grub2/locale files (minor issue for UEFI ISO boot)

Workaround, if any:
Have not tried the recovery yet.
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:

[root@rhel7-8-test rear]# !239
rear -v mkrescue
Relax-and-Recover 2.7 / Git
Running rear mkrescue (PID 99452 date 2024-09-30 09:16:48)
Using log file: /var/log/rear/rear-rhel7-8-test.log
Running workflow mkrescue on the normal/original system
Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
Using autodetected kernel '/boot/vmlinuz-3.10.0-1160.119.1.el7.x86_64' as kernel in the recovery system
Creating disk layout
Overwriting existing disk layout file /var/lib/rear/layout/disklayout.conf
Disabling component 'disk /dev/sdb' in /var/lib/rear/layout/disklayout.conf
Disabling component 'part /dev/sdb' in /var/lib/rear/layout/disklayout.conf
Verifying that the entries in /var/lib/rear/layout/disklayout.conf are correct
Created disk layout (check the results in /var/lib/rear/layout/disklayout.conf)
Creating recovery system root filesystem skeleton layout
Skipping 'lo': not bound to any physical interface.
To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD
Using '/boot/efi/EFI/redhat/shimx64.efi' as UEFI Secure Boot bootloader file
Copying logfile /var/log/rear/rear-rhel7-8-test.log into initramfs as '/tmp/rear-rhel7-8-test-partial-2024-09-30T09:17:00-05                               00.log'
Copying files and directories
Copying binaries and libraries
Copying all kernel modules in /lib/modules/3.10.0-1160.119.1.el7.x86_64 (MODULES contains 'all_modules')

Failed to copy all contents of /lib/modules/3.10.0-1160.119.1.el7.x86_64 (dangling symlinks could be a reason)

Copying all files in /lib*/firmware/

Broken symlink '/etc/grub2.cfg' in recovery system because 'readlink' cannot determine its link target

Testing that the ReaR recovery system in '/var/tmp/rear.rmxc1GBgSiWQa1a/rootfs' contains a usable system
Creating recovery/rescue system initramfs/initrd initrd.cgz with gzip default compression
Created initrd.cgz with gzip default compression (447 MiB) in 41 seconds

Did not find /boot/grub2/locale files (minor issue for UEFI ISO boot)

Making ISO image
Wrote ISO image: /var/lib/rear/output/rear-rhel7-8-test.iso (557M)
Exiting rear mkrescue (PID 99452) and its descendant processes ...
Running exit tasks
[root@rhel7-8-test rear]#

Thanks very much!
rear-rhel7-8-test.log

gdha commented at 2024-10-03 09:44:¶

@RLDuckworth Did you already try to boot from the ISO image as a test? I think it should work.

RLDuckworth commented at 2024-10-03 13:57:¶

Good morning,

I was able to boot the ISO image, select Relax-and-Recover (UEFI and Secure Boot) and it looks like it’s ready to run rear recover. Before I had been selecting the Relax-and-Recover (BIOS or UEFI without Secure Boot) and it would not boot.
Should I be able to boot either one?

I will go ahead and run a rear recover and see what happens. This is all trial and error right now. Is there a way to determine exactly what backup will be restored from Rubrik?

We’re making progress. Thanks very much!

Randall L. Duckworth III
Linux Systems Administrator III | Information Technology
O (940) 321-7800 x.7502
7701 S Stemmons, Corinth, TX 76210

***@***.***

“CoServ's Mission is to deliver excellent service to our Members
and Customers by providing safe and reliable energy solutions."

From: gdha ***@***.***>
Sent: Thursday, October 3, 2024 4:45 AM
To: rear/rear ***@***.***>
Cc: Randall Duckworth III ***@***.***>; Mention ***@***.***>
Subject: Re: [rear/rear] Creating BMR ISO for Rubrik Recovery (Issue #3324)
Recover
EXTERNAL: This email originated outside of CoServ.

@RLDuckworthhttps://github.com/RLDuckworth Did you already try to boot from the ISO image as a test? I think it should work.

—
Reply to this email directly, view it on GitHubhttps://github.com/rear/rear/issues/3324#issuecomment-2390977084, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH2A23OCGAGPMY66NUL5ZWLZZUGZPAVCNFSM6AAAAABPD7PFMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJQHE3TOMBYGQ.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

gdha commented at 2024-10-03 14:23:¶

Good morning, I was able to boot the ISO image, select Relax-and-Recover (UEFI and Secure Boot) and it looks like it’s ready to run rear recover. Before I had been selecting the Relax-and-Recover (BIOS or UEFI without Secure Boot) and it would not boot. Should I be able to boot either one? I will go ahead and run a rear recover and see what happens. This is all trial and error right now. Is there a way to determine exactly what backup will be restored from Rubrik?

Rubrik is an external backup program where I do not have any knowledge of - sorry.

RLDuckworth commented at 2024-10-03 15:14:¶

But should we be able to boot from either menu item - Relax-and-Recover (UEFI and Secure Boot) or Relax-and-Recover (BIOS or UEFI without Secure Boot)? I noticed in the ISO creation output, it said Using '/boot/efi/EFI/redhat/shimx64.efi' as UEFI Secure Boot bootloader file but didn’t say anything about without Secure Boot bootloader file.

Thanks,

Randall L. Duckworth III
Linux Systems Administrator III | Information Technology
O (940) 321-7800 x.7502
7701 S Stemmons, Corinth, TX 76210

***@***.***

“CoServ's Mission is to deliver excellent service to our Members
and Customers by providing safe and reliable energy solutions."

From: gdha ***@***.***>
Sent: Thursday, October 3, 2024 9:24 AM
To: rear/rear ***@***.***>
Cc: Randall Duckworth III ***@***.***>; Mention ***@***.***>
Subject: Re: [rear/rear] Creating BMR ISO for Rubrik Recovery (Issue #3324)

EXTERNAL: This email originated outside of CoServ.

Good morning, I was able to boot the ISO image, select Relax-and-Recover (UEFI and Secure Boot) and it looks like it’s ready to run rear recover. Before I had been selecting the Relax-and-Recover (BIOS or UEFI without Secure Boot) and it would not boot. Should I be able to boot either one? I will go ahead and run a rear recover and see what happens. This is all trial and error right now. Is there a way to determine exactly what backup will be restored from Rubrik?

Rubrik is an external backup program where I do not have any knowledge of - sorry.

—
Reply to this email directly, view it on GitHubhttps://github.com/rear/rear/issues/3324#issuecomment-2391555689, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH2A23LGQJWKTFAGEQTIAXDZZVHO5AVCNFSM6AAAAABPD7PFMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJRGU2TKNRYHE.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

gdha commented at 2024-10-04 06:48:¶

UEFI_BOOTLOADER=/boot/efi/EFI/redhat/grubx64.efi
SECURE_BOOT_BOOTLOADER=/boot/efi/EFI/redhat/shimx64.efi

You configured it to use Relax-and-Recover (UEFI and Secure Boot), therefore, that's the way to boot from then.

However, you have a point as well and the ReaR team is aware of it and it is on our to-do list for improvements. The ISO booting architecture is 20 years old and need a proper rewrite! However, as always there is a but, lack of sponsoring, which forces us to lower its priority.

End users always forget that Open Source contributors need food as well and that is not free. This is a general remark and is not meant for you.

[Export of Github issue for rear/rear.]

#3324 Issue open: Creating BMR ISO for Rubrik Recovery¶