#2805 Issue closed: rear-backup is failing with "... recovery system ... is broken: 'bash -c true' failed"¶
Labels: waiting for info, support / question,
no-issue-activity
rudyvirus opened issue at 2022-05-12 13:41:¶
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.3 / 2017-12-20
-
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): SLE12SP15
-
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
#Bookable disk will be format of ISO
OUTPUT=ISO
#Including only the OS disk
ONLY_INCLUDE_VG=("vgroot")
#NFS method of backup
BACKUP=NETFS
#configuring as NFS server
BACKUP_URL=nfs://IPADDRESS/data/REAR
#Adding Multipath
AUTOEXCLUDE_MULTIPATH=n
#Boot disk is from SAN
BOOT_OVER_SAN=y
#Exclude all disks except rootvg
## SLES12
REQUIRED_PROGS=( "${REQUIRED_PROGS[@]}" snapper chattr lsattr )
COPY_AS_IS=( "${COPY_AS_IS[@]}" /usr/lib/snapper/installation-helper /etc/snapper/config-templates/default )
for subvol in $(findmnt -n -r -t btrfs | cut -d ' ' -f 1 | grep -v '^/$' | egrep -v 'snapshots|crash') ; do
BACKUP_PROG_INCLUDE=( "${BACKUP_PROG_INCLUDE[@]}" "$subvol" )
done
POST_RECOVERY_SCRIPT=( 'if snapper --no-dbus -r $TARGET_FS_ROOT get-config | grep -q "^QGROUP.*[0-9]/[0-9]" ; then snapper --no-dbus -r $TARGET_FS_ROOT set-config QGROUP= ; snapper --no-dbus -r $TARGET_FS_ROOT setup-quota && echo snapper setup-quota done || echo snapper setup-quota failed ; else echo snapper setup-quota not used ; fi' )
-
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
IBM Power Frame -
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
PPC64 -
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Firmware -
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN -
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
-
Description of the issue (ideally so that others can reproduce it):
while running the rear-backup getting failed with below error
To log into the recovery system via ssh set up /root/.ssh/authorized_keys or specify SSH_ROOT_PASSWORD
ERROR:
====================
BUG in /usr/share/rear/build/default/980_verify_rootfs.sh line 20:
'ReaR recovery system in '/tmp/rear.pjWl527DHjXqFeG/rootfs' is broken: 'bash -c true' failed'
--------------------
Please report this issue at https://github.com/rear/rear/issues
and include the relevant parts from /var/log/rear/rear-hostname.log
preferably with full debug information via 'rear -d -D mkbackup'
====================
Aborting due to an error, check /var/log/rear/rear-xmpsl020qhan0.log for details
Terminated
-
Workaround, if any:
-
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
```
verbatim content
```
jsmeix commented at 2022-05-13 09:02:¶
@rudyvirus
see
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files)
and
... include the relevant parts from /var/log/rear/rear-hostname.log
preferably with full debug information via 'rear -d -D mkbackup'
Without a ReaR debug log file we have no chance
to find out what the root cause could be.
Here a "rear -d -D mkrescue" debug log file
should be sufficient to find out what the root cause could be
why the ReaR recovery system got broken
in your specific case.
In general:
Relax-and-Recover 2.3 is rather old.
Please test if it works for you when you use
our current ReaR GitHub master code.
See the section
"Testing current ReaR upstream GitHub master code" in
https://en.opensuse.org/SDB:Disaster_Recovery
how you can try out our current ReaR GitHub master code
without conflicts with your already installed ReaR version.
In general I recommend to try out our latest GitHub master code
because the GitHub master code is the only place where we fix things
and if there are issues it helps when you use exactly the code
where we could fix things.
In general we at ReaR upstream do not support older ReaR versions.
We at ReaR upstream do not plain reject issues with older ReaR
versions
(e.g. we may answer easy to solve questions also for older ReaR
versions)
but we do not spend much time on issues with older ReaR versions
because
we do not (and cannot) fix issues in released ReaR versions.
Issues in released ReaR versions are not fixed by us (by ReaR
upstream).
Issues in released ReaR versions that got fixed in current ReaR
upstream
GitHub master code might be fixed (if the fix can be backported with
reasonable effort) by the Linux distributor wherefrom you got ReaR.
In case of SUSE Linux Enterprise you may contact SUSE directly
provided you have an appropriate SUSE support contract.
In particular see the section
"SUSE support for Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery
rudyvirus commented at 2022-05-18 12:50:¶
Hello All,
Please find the log details:
xmpsl020qhan0:~ # /usr/sbin/rear mkbackup > /usr/local/mkbakupstatus.out
tac: /tmp/tackeM2et: write error: No space left on device
tac: /tmp/tac6rMfpr: write error: No space left on device
Script 'default/010_set_drlm_env.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/030_update_recovery_system.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/050_check_rear_recover_mode.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/005_remove_workflow_conf.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/020_translate_url.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/030_translate_tape.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/040_check_backup_and_output_scheme.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/040_inspect_configuration_files.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/050_check_NETFS_requirements.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/050_check_keep_old_output_copy_var.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/060_mount_NETFS_path.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/070_set_backup_archive.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/090_check_encrypted_backup.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/100_check_nfs_version.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/100_init_workflow_conf.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/150_save_rsync_version.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/200_include_getty.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/200_include_serial_console.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/GNU/Linux/200_selinux_in_use.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/GNU/Linux/205_inspect_tar_capabilities.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/210_include_dhclient.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/220_include_lvm_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/230_include_md_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/240_include_multipath_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/280_include_systemd.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/280_include_virtualbox.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/280_include_vmware_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/290_include_drbd.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/300_check_backup_and_output_url.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'ISO/default/300_check_iso_dir.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/300_include_grub_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/310_include_cap_utils.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'ISO/default/320_check_cdrom_size.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/320_include_uefi_env.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'ISO/GNU/Linux/320_verify_mkisofs.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/330_include_uefi_tools.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'ISO/GNU/Linux/340_add_isofs_module.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/400_automatic_exclude_recreate.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/400_save_directories.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'default/950_check_missing_programs.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'NETFS/default/980_umount_NETFS_dir.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/100_create_layout_file.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
Script 'GNU/Linux/150_save_diskbyid_mappings.sh' without leading 3-digit number 'NNN_' is likely run in wrong order
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
ERROR: Empty string passed to UdevQueryName()
ERROR: Empty string passed to UdevSymlinkName()
Aborting due to an error, check /var/log/rear/rear-xmpsl020qhan0.log for details
Terminated
github-actions commented at 2022-09-06 04:08:¶
Stale issue message
[Export of Github issue for rear/rear.]