#2694 Issue closed: ReaR v2.6 not generating ISO, no explicit ERROR in debug log sections.

Labels: support / question, no-issue-activity

cervantevo opened issue at 2021-10-08 19:11:

  • ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6
  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description:    CentOS Linux release 7.9.2009 (Core)
Release:        7.9.2009
Codename:       Core
  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
OUTPUT=ISO
BACKUP=CDM
BOOTLOADER="GRUB2-EFI"
REAL_MACHINE=x86_64
ARCH=Linux-x86_64
OS_MASTER_VENDOR="CentOS"
OS_MASTER_VERSION="7"
OS_MASTER_VENDOR_ARCH="CentOS/x86_64"
OS_MASTER_VENDOR_VERSION="CentOS/7"
OS_MASTER_VENDOR_VERSION_ARCH="CentOS/7/x86_64"
OS_VENDOR=CentOS
OS_VERSION=7.9.2009
OS_VENDOR_ARCH="CentOS/x86_64"
OS_VENDOR_VERSION="CentOS/7"
OS_VENDOR_VERSION_ARCH="CentOS/7/x86_64
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/usr/lib64/bind9-export:/usr/lib64/eog:/usr/lib64/python3.6/site-packages:/usr/lib64/samba"
MODULES=( 'loaded_modules' )
TRUSTED_FILE_OWNERS=( 'root' 'bin' 'daemon' 'sync' 'shutdown' 'halt' 'operator' 'queen711' )
USE_DHCLIENT=no
COPY_AS_IS_CDM=( /etc/rubrik /usr/bin/rubrik /var/log/rubrik /etc/pki /usr/lib64/*)
COPY_AS_IS_EXCLUDE=(/var/log/lastlog)
KEEP_OLD_OUTPUT_COPY=yes
  • Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
VMWare 6.7 VM
  • 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
GRUB2

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
    local disk

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT"):

NAME                     KNAME     PKNAME    TRAN   TYPE FSTYPE       SIZE MOUNTPOINT
/dev/sda                 /dev/sda                   disk               20G
|-/dev/sda1              /dev/sda1 /dev/sda         part vfat         200M /boot/efi
|-/dev/sda2              /dev/sda2 /dev/sda         part ext4           1G /boot
`-/dev/sda3              /dev/sda3 /dev/sda         part LVM2_member 18.8G
  |-/dev/mapper/vg0-root /dev/dm-0 /dev/sda3        lvm  ext4        16.8G /
  `-/dev/mapper/vg0-swap /dev/dm-1 /dev/sda3        lvm  swap           2G [SWAP]
/dev/sr0                 /dev/sr0            sata   rom              1024M
  • Description of the issue (ideally so that others can reproduce it):
    Running the ~../rear -d -v -D mkrescue with this local.conf, is not generating an ISO image.
    The output also is not capturing that the process is erroring.
    In the debug log, it is self referencing to review the log for further details.
    Not entirely sure if some, all, or none of the "returns 1" lines are where the focus should go.
    I have tried to resolve some of the sections that have "returns 1" in the line,
    but nothing seems to be resolving the true issue.
    I would like assistance in understanding which section in the ISO generation is actually needing resolution.
sudo rear/usr/sbin/rear -d -v -D mkrescue
Relax-and-Recover 2.6 / Git
Running rear mkrescue (PID 109330 date 2021-10-08 13:50:13)
Command line options: rear/usr/sbin/rear -d -v -D mkrescue
Using log file: /nfshome/queen711/rear/var/log/rear/rear-mjgtest-03-l30.log
Using build area: /var/tmp/rear.zbohpomQvQL5IBk
Running workflow mkrescue on the normal/original system
Found EFI system partition /dev/sda1 on /boot/efi type vfat
Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
Using '/bin/mkisofs' to create ISO filesystem images
Using autodetected kernel '/boot/vmlinuz-3.10.0-1160.el7.x86_64' as kernel in the recovery system
Creating disk layout
Overwriting existing disk layout file /nfshome/queen711/rear/var/lib/rear/layout/disklayout.conf
Disabling excluded components in /nfshome/queen711/rear/var/lib/rear/layout/disklayout.conf
Using specified bootloader 'GRUB2-EFI' for 'rear recover'
Verifying that the entries in /nfshome/queen711/rear/var/lib/rear/layout/disklayout.conf are correct
Created disk layout (check the results in /nfshome/queen711/rear/var/lib/rear/layout/disklayout.conf)
Creating recovery system root filesystem skeleton layout
Handling network interface 'ens192'
ens192 is a physical device
Handled network interface 'ens192'
Included current keyboard mapping (via 'dumpkeys -f')
Included default US keyboard mapping /lib/kbd/keymaps/legacy/i386/qwerty/defkeymap.map.gz
Included other keyboard mappings in /lib/kbd/keymaps
To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD
Trying to find what to use as UEFI bootloader...
Trying to find a 'well known file' to be used as UEFI bootloader...
Using '/boot/efi/EFI/centos/grubx64.efi' as UEFI bootloader file
Copying logfile /nfshome/queen711/rear/var/log/rear/rear-mjgtest-03-l30.log into initramfs as '/tmp/rear-mjgtest-03-l30-partial-2021-10-08T13:50:31-0400.log'
Copying files and directories
Copying binaries and libraries
Copying only currently loaded kernel modules (MODULES contains 'loaded_modules') and those in MODULES_LOAD
Copying all files in /lib*/firmware/
Skip copying broken symlink '/etc/mtab' target '/proc/8210/mounts' on /proc/ /sys/ /dev/ or /run/
Testing that the recovery system in /var/tmp/rear.zbohpomQvQL5IBk/rootfs contains a usable system
Testing each binary with 'ldd' and look for 'not found' libraries within the recovery system
Testing that the existing programs in the PROGS array can be found as executable command within the recovery system
Testing that each program in the REQUIRED_PROGS array can be found as executable command within the recovery system
Creating recovery/rescue system initramfs/initrd initrd.cgz with gzip default compression
Created initrd.cgz with gzip default compression (411667214 bytes) in 50 seconds
Exiting rear mkrescue (PID 109330) and its descendant processes ...
Running exit tasks
To remove the build area use (with caution): rm -Rf --one-file-system /var/tmp/rear.zbohpomQvQL5IBk

TIA

  • Workaround, if any:

  • Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
    rear-mjgtest-03-l30.log

jsmeix commented at 2021-10-11 07:28:

I am not a BACKUP=CDM user
so I can neither really reproduce issues with BACKUP=CDM
nor do I know how things should actually behave with BACKUP=CDM.

Perhaps the reason could be that you have
neither OUTPUT_URL nor BACKUP_URL
specified in your etc/rear/local.conf
but
https://github.com/rear/rear/blob/master/doc/user-guide/16-Rubrik-CDM.adoc
reads

3. Edit /etc/rear/local.conf and enter:

OUTPUT=ISO
BACKUP=CDM

so perhaps BACKUP=CDM could work even without a OUTPUT_URL?

See also
https://github.com/rear/rear/issues/2667#issuecomment-914368204

cervantevo commented at 2021-10-18 20:21:

Thank you for that suggestion. I have added OUTPUT_URL=null as well as USE_DHCLIENT="no". It did produce an ISO. We are currently testing the restored ISO for any issues.

We are glad that an ISO was produced, but viewing the actual ReaR debug log shows the process should have failed, or at least produced some error output. The log still doesn't describe which part encountered error. Am I reading too far into this?

rear-mjgtest-03-l30.log

TIA

github-actions commented at 2021-12-18 02:22:

Stale issue message

[Export of Github issue for rear/rear.]