#3013 Issue open: rear backup recover error

Labels: waiting for info, support / question

ChickenTim99 opened issue at 2023-06-12 04:03:

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"):
"SUSE Linux Enterprise Server 12 SP4"

It got error when I try to restore the LPAR by command "rear -D -d recover " .

Error message:

RESCUE tsm:~ # rear -D -d recover
Relax-and-Recover 2.6 / 2020-06-17
Running rear recover (PID 6435)
Using log file: /var/log/rear/rear-tsm.log
Running workflow recover within the ReaR rescue/recovery system
Will do driver migration (recreating initramfs/initrd)
Comparing disks
Device sda has expected (same) size 182536110080 bytes (will be used for 'recover')
Disk configuration looks identical
UserInput -I DISK_LAYOUT_PROCEED_RECOVERY needed in /usr/share/rear/layout/prepare/default/250_compare_disks.sh line 148
Proceed with 'recover' (yes) otherwise manual disk layout configuration is enforced
(default 'yes' timeout 30 seconds)
UserInput: No choices - result is 'yes'
User confirmed to proceed with 'recover'
Doing SLES-like btrfs subvolumes setup for /dev/sda3 on / (BTRFS_SUBVOLUME_SLES_SETUP contains /dev/sda3)
SLES12-SP1 (and later) btrfs subvolumes setup needed for /dev/sda3 (default subvolume path contains '@/.snapshots/')
Start system layout restoration.
Disk '/dev/sda': creating 'msdos' partition table
UserInput -I LAYOUT_CODE_RUN needed in /usr/share/rear/layout/recreate/default/200_run_layout_code.sh line 127
The disk layout recreation script failed
1) Rerun disk recreation script (/var/lib/rear/layout/diskrestore.sh)
2) View 'rear recover' log file (/var/log/rear/rear-tsm.log)
3) Edit disk recreation script (/var/lib/rear/layout/diskrestore.sh)
4) View original disk space usage (/var/lib/rear/layout/config/df.txt)
5) Use Relax-and-Recover shell and return back to here
6) Abort 'rear recover'
(default '1' timeout 300 seconds)

jsmeix commented at 2023-06-12 09:55:

in general see
the section
"Disaster recovery with Relax-and-Recover (ReaR)"
and therein in particular the sub-section
"Debugging issues with Relax-and-Recover"
and therein in particular the part
"To analyze and debug a 'rear recover' failure
the following information is mandatory"

[Export of Github issue for rear/rear.]