Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Customer make the backup into single one iso file without problem. With /etc/rear/local.conf like this:
***********
$ more 0120-local.conf.txt
OUTPUT=ISO
OUTPUT_URL=file:///u03/
BACKUP=NETFS
BACKUP_URL=iso:///backup/
BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash' '/u01' '/u02' '/u03')
NETFS_KEEP_OLD_BACKUP_COPY=
PRE_RECOVERY_SCRIPT=("modprobe usb-storage ; sleep 35")
MODULES+=("usb-storage")
AUTOEXCLUDE_MULTIPATH=n
*************
The "rear mkbackup" completed with a success, But found error below when “rear recover”
*******
Error ‘Cannot mount ISO because there is no ‘\’ ‘/dev/disk/by-label/RELAXRECOVER’ , the recover log can be found in capture file in c#15 (file “SST-Recover-debug.docx”)
*******
Version-Release number of selected component (if applicable):
rear-2.6-4.el8.x86_64 Mon May 23 10:39:20 2022
How reproducible:
Steps to Reproduce:
1. "rear mkbakcup" success (backup files to single iso file)
2. "rear recover" to another HP identical physical server.
3. see "‘Cannot mount ISO because there is no ‘\’ ‘/dev/disk/by-label/RELAXRECOVER’
Actual results:
Expected results:
Additional info:
test the same in vmware platform (between two vmware virtual server) with the same /etc/rear/local.conf , it worked.
attached recover log, thanks.
one point here, since the single iso file is more than 4G size, he seem boot this iso file from HPE proliant server with ""virtual CDROM option", does it a problem ? should customer burn it to DVD and retry the "rear recover"? thanks.
> one point here, since the single iso file is more than 4G size, he seem boot this iso file from HPE proliant server with ""virtual CDROM option", does it a problem ?
I am not sure, because this is something that depends on the server firmware, not the OS or ReaR. I would try a physical DVD indeed if it is easy.
I also recommend examining the system before ReaR starts to check if the rescue DVD is visible to the system (using commands like lsblk and blkid).
Here's how it looks when the DVD is found properly:
RESCUE localhost:~ # blkid
...
/dev/sr0: UUID="2021-06-21-13-07-28-00" LABEL="REAR-ISO" TYPE="iso9660"
RESCUE localhost:~ # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
(...)
sr0 11:0 1 201.3M 0 rom
RESCUE localhost:~ # blkid -L REAR-ISO
/dev/sr0
RESCUE localhost:~ # ls -l /dev/disk/by-label/REAR-ISO
lrwxrwxrwx 1 root root 9 May 31 09:20 /dev/disk/by-label/REAR-ISO -> ../../sr0
(Replace REAR-ISO by RELAXRECOVER, my example is from a newer version of ReaR where the label got changed from RELAXRECOVER to REAR-ISO, but otherwise it should behave the same.)
Note that the lsblk commands shows the size of the virtual DVD (ISO image) in sr0.
Description of problem: Customer make the backup into single one iso file without problem. With /etc/rear/local.conf like this: *********** $ more 0120-local.conf.txt OUTPUT=ISO OUTPUT_URL=file:///u03/ BACKUP=NETFS BACKUP_URL=iso:///backup/ BACKUP_PROG_EXCLUDE=("${BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash' '/u01' '/u02' '/u03') NETFS_KEEP_OLD_BACKUP_COPY= PRE_RECOVERY_SCRIPT=("modprobe usb-storage ; sleep 35") MODULES+=("usb-storage") AUTOEXCLUDE_MULTIPATH=n ************* The "rear mkbackup" completed with a success, But found error below when “rear recover” ******* Error ‘Cannot mount ISO because there is no ‘\’ ‘/dev/disk/by-label/RELAXRECOVER’ , the recover log can be found in capture file in c#15 (file “SST-Recover-debug.docx”) ******* Version-Release number of selected component (if applicable): rear-2.6-4.el8.x86_64 Mon May 23 10:39:20 2022 How reproducible: Steps to Reproduce: 1. "rear mkbakcup" success (backup files to single iso file) 2. "rear recover" to another HP identical physical server. 3. see "‘Cannot mount ISO because there is no ‘\’ ‘/dev/disk/by-label/RELAXRECOVER’ Actual results: Expected results: Additional info: test the same in vmware platform (between two vmware virtual server) with the same /etc/rear/local.conf , it worked.