REAR 2.9 + rpi5-killer DR howto

Debian 12 hiba és patkolása:

root@rpi5-killer:/etc/rear#  ldd /usr/lib/x86_64-linux-gnu/systemd/libsystemd-core-252.so
    linux-vdso.so.1 (0x00007efcccdca000)
    libsystemd-shared-252.so => not found
    libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007efcccba4000)
    libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007efcccb92000)
    libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007efcccb61000)
    libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007efcccb44000)
    libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1 (0x00007efcccb2d000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007efcccaff000)
    libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007efccca9c000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007efccc8bb000)
    libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007efccc8b3000)
    libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007efccc7f7000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007efccc7c6000)
    libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007efccc200000)
    libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007efccc72c000)
    /lib64/ld-linux-x86-64.so.2 (0x00007efcccdcc000)
    libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007efccc6d5000)

root@rpi5-killer:/etc/rear# echo "/usr/lib/x86_64-linux-gnu/systemd" > /etc/ld.so.conf.d/libsystemd-core.conf && ldconfig

root@rpi5-killer:/etc/rear#  ldd /usr/lib/x86_64-linux-gnu/systemd/libsystemd-core-252.so
    linux-vdso.so.1 (0x00007fa2a492d000)
    libsystemd-shared-252.so => /usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-252.so (0x00007fa2a4200000)
    libseccomp.so.2 => /lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007fa2a4707000)
    libpam.so.0 => /lib/x86_64-linux-gnu/libpam.so.0 (0x00007fa2a46f5000)
    libaudit.so.1 => /lib/x86_64-linux-gnu/libaudit.so.1 (0x00007fa2a46c4000)
    libkmod.so.2 => /lib/x86_64-linux-gnu/libkmod.so.2 (0x00007fa2a46a7000)
    libapparmor.so.1 => /lib/x86_64-linux-gnu/libapparmor.so.1 (0x00007fa2a4690000)
    libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fa2a4662000)
    libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 (0x00007fa2a45ff000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa2a401f000)
    libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x00007fa2a45f4000)
    libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 (0x00007fa2a459d000)
    libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007fa2a458f000)
    libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007fa2a4553000)
    libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fa2a3ed8000)
    libip4tc.so.2 => /lib/x86_64-linux-gnu/libip4tc.so.2 (0x00007fa2a4549000)
    liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fa2a3eb2000)
    libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x00007fa2a3a00000)
    libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007fa2a3944000)
    liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fa2a3915000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa2a3835000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fa2a492f000)
    libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007fa2a453f000)
    libpcre2-8.so.0 => /lib/x86_64-linux-gnu/libpcre2-8.so.0 (0x00007fa2a379b000)
    libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fa2a3e8a000)

rpi5-killer Debian12 DR for the OS with REAR 2.9 on the 3rd disk ... Sok szívás, van benne Debian 12-es hiba is, pl. hibás REAR 2.9, kisebb NVME SSD méret, után siker 1 Ventoy-os pendriveval ... Multi DR egy pendriveval ... Nagyon király lett ...
Sikerült a teszt szerveremen a DR. :)

root@rpi5-killer:/etc/rear# cat os.conf 
OS_VENDOR=Debian
OS_VERSION=12

root@rpi5-killer:/etc/rear#  cat local.conf
OUTPUT=ISO
BACKUP=NETFS
AUTOEXCLUDE_DISKS=no
ONLY_INCLUDE_VG=( "vg" )
BACKUP_URL=file:///media/rear
BACKUP_PROG_EXCLUDE=( '/tmp/*' )
FIRMWARE_FILES=( 'yes' )
COPY_AS_IS=( '/usr/share/file/magic' '/usr/share/rear/*' '/var/lib/rear/*' )
AUTOEXCLUDE_MULTIPATH=yes
MIGRATION_MODE='true'
AUTORESIZE_PARTITIONS=( /dev/nvme0n1p3 )
AUTOSHRINK_DISK_SIZE_LIMIT_PERCENTAGE=90

innetől kezdve REAR 2.9 mentés hiba nélkül fut.

root@rpi5-killer:/etc/rear# rear -v mkbackup
Relax-and-Recover 2.9 / 2025-01-31
Running rear mkbackup (PID 1147989 date 2025-08-07 17:05:43)
Using log file: /var/log/rear/rear-rpi5-killer.log
Running workflow mkbackup on the normal/original system
Using backup archive '/media/rear/rpi5-killer/backup.tar.gz'
Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
Using autodetected kernel '/boot/vmlinuz-6.12.22+bpo-amd64' as kernel in the recovery system
Creating disk layout
Overwriting existing disk layout file /var/lib/rear/layout/disklayout.conf
Excluding component fs:/media/rear in EXCLUDE_RECREATE
Disabling component 'fs ... /media/hdd' in /var/lib/rear/layout/disklayout.conf
Disabling component 'fs ... /media/backup' in /var/lib/rear/layout/disklayout.conf
Disabling component 'fs ... /media/rear' 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
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/debian/grubx64.efi' as UEFI bootloader file (non Secure Boot)
Copying logfile /var/log/rear/rear-rpi5-killer.log into initramfs as '/tmp/rear-rpi5-killer-partial-2025-08-07T17:05:56+02:00.log'
Copying files and directories
Copying binaries and libraries
Copying all kernel modules in /lib/modules/6.12.22+bpo-amd64 (MODULES contains 'all_modules')
Copying all files in /lib*/firmware/
Testing that the ReaR recovery system in '/var/tmp/rear.ShUE7UGszT145aN/rootfs' contains a usable system
Creating recovery/rescue system initramfs/initrd initrd.cgz with gzip default compression
Created initrd.cgz with gzip default compression (200 MiB) in 17 seconds
GRUB2 modules to load: ext2 fat part_gpt part_msdos
Making ISO image
Wrote ISO image: /var/lib/rear/output/rear-rpi5-killer.iso (325M)
Copying resulting files to file location
Saving /var/log/rear/rear-rpi5-killer.log as rear-rpi5-killer.log to file location
Copying result files '/var/lib/rear/output/rear-rpi5-killer.iso /var/tmp/rear.ShUE7UGszT145aN/tmp/VERSION /var/tmp/rear.ShUE7UGszT145aN/tmp/README /var/tmp/rear.ShUE7UGszT145aN/tmp/rear-rpi5-killer.log' to /media/rear/rpi5-killer at file location
Making backup (using backup method NETFS)
Creating tar archive '/media/rear/rpi5-killer/backup.tar.gz'
Archived 1767 MiB [avg 14367 KiB/sec] OK
WARNING: tar ended with return code 1 and below output (last 5 lines):
  ---snip---
  tar: /var/tmp/rear.ShUE7UGszT145aN/tmp/backup.log: file changed as we read it
  ----------
This means that files have been modified during the archiving
process. As a result the backup may not be completely consistent
or may not be a perfect copy of the system. Relax-and-Recover
will continue, however it is highly advisable to verify the
backup in order to be sure to safely recover this system.

Archived 1767 MiB in 127 seconds [avg 14254 KiB/sec]
Exiting rear mkbackup (PID 1147989) and its descendant processes ...
Running exit tasks

ice@debian:/media/ice/Ventoy/rpi5-killer/recover$ cat rear-rpi5-killer.log
2025-08-07 19:30:16.733620315 Relax-and-Recover 2.9 / 2025-01-31
2025-08-07 19:30:16.736801487 Running rear recover (PID 568 date 2025-08-07 19:30:16)
2025-08-07 19:30:16.740464323 Using log file: /var/log/rear/rear-rpi5-killer.log
2025-08-07 19:30:16.744611526 Including /etc/rear/os.conf
2025-08-07 19:30:16.750551505 Including conf/Linux-i386.conf
2025-08-07 19:30:16.754960172 Including conf/GNU/Linux.conf
2025-08-07 19:30:16.777517824 Including /etc/rear/local.conf
2025-08-07 19:30:16.790711002 Including /etc/rear/rescue.conf
2025-08-07 19:30:16.804499269 ======================
2025-08-07 19:30:16.813523871 Running 'init' stage
2025-08-07 19:30:16.822598227 ======================
2025-08-07 19:30:16.847728066 Including init/default/001_verify_config_arrays.sh
2025-08-07 19:30:17.330148192 Including init/default/002_check_rear_recover_mode.sh
2025-08-07 19:30:17.332252463 Running workflow recover within the ReaR rescue/recovery system
2025-08-07 19:30:17.336917247 Including init/default/010_EFISTUB_check.sh
2025-08-07 19:30:17.341851116 Including init/default/010_set_drlm_env.sh
2025-08-07 19:30:17.347452499 Including init/default/030_update_recovery_system.sh
2025-08-07 19:30:17.353149812 Including init/default/100_check_stale_nfs_mounts.sh
2025-08-07 19:30:17.360735270 Including init/default/950_check_missing_programs.sh
2025-08-07 19:30:17.370571535 Including init/default/998_dump_variables.sh
2025-08-07 19:30:17.376553483 Finished running 'init' stage in 1 seconds
2025-08-07 19:30:17.383636158 Running recover workflow
2025-08-07 19:30:17.389016228 ======================
2025-08-07 19:30:17.396321671 Running 'setup' stage
2025-08-07 19:30:17.405348584 ======================
2025-08-07 19:30:17.430593737 Including setup/default/002_clean_start.sh
2025-08-07 19:30:17.448580472 Including setup/default/005_ssh_agent_start.sh
2025-08-07 19:30:17.469288646 Starting up ssh-agent
2025-08-07 19:30:17.497894804 Including setup/default/007_set_dmesg_level.sh
2025-08-07 19:30:17.519374788 Including setup/default/010_pre_recovery_script.sh
2025-08-07 19:30:17.529556835 Finished running 'setup' stage in 0 seconds
2025-08-07 19:30:17.539633345 ======================
2025-08-07 19:30:17.549304829 Running 'verify' stage
2025-08-07 19:30:17.559187206 ======================
2025-08-07 19:30:17.585335141 Including verify/default/020_cciss_scsi_engage.sh
2025-08-07 19:30:17.607481921 Including verify/default/020_translate_url.sh
2025-08-07 19:30:17.626032919 Including verify/default/030_translate_tape.sh
2025-08-07 19:30:17.650734437 Including verify/default/040_validate_variables.sh
2025-08-07 19:30:17.669251616 Including verify/NETFS/default/050_check_NETFS_requirements.sh
2025-08-07 19:30:17.690668569 Skipping 'ping' test for host '' in BACKUP_URL 'file:///media/rear'
2025-08-07 19:30:17.716755626 Including verify/default/050_create_mappings_dir.sh
2025-08-07 19:30:17.735276388 Including verify/NETFS/default/050_start_required_nfs_daemons.sh
2025-08-07 19:30:17.760438336 Including verify/NETFS/default/060_mount_NETFS_path.sh
2025-08-07 19:30:17.785957633 Including verify/NETFS/default/070_set_backup_archive.sh
2025-08-07 19:30:17.807527744 Using backup archive '/media/rear/rpi5-killer/backup.tar.gz'
2025-08-07 19:30:17.827078347 Including verify/NETFS/default/090_set_readonly_options.sh
2025-08-07 19:30:17.845636628 Including verify/GNU/Linux/230_storage_and_network_modules.sh
2025-08-07 19:30:17.855489407 Including storage drivers
2025-08-07 19:30:17.876647780 Including network drivers
2025-08-07 19:30:17.900106612 Including crypto drivers
2025-08-07 19:30:17.917263710 Including virtualization drivers
2025-08-07 19:30:17.934421614 Including additional drivers
2025-08-07 19:30:17.959942944 Including verify/GNU/Linux/260_recovery_storage_drivers.sh
2025-08-07 19:30:18.126588543 No driver migration: '/var/tmp/rear.F5fZc3kybAVhEiZ/tmp/storage_drivers' and '/var/lib/rear/recovery/storage_drivers' are the same
2025-08-07 19:30:18.130398566 Including verify/NETFS/default/550_check_backup_archive.sh
2025-08-07 19:30:18.135605621 Calculating backup archive size
2025-08-07 19:30:18.138525162 Backup archive size is 1.8G    /media/rear/rpi5-killer/backup.tar.gz (compressed)
2025-08-07 19:30:18.142712077 Including verify/NETFS/default/600_check_encryption_key.sh
2025-08-07 19:30:18.147219741 Including verify/NETFS/default/980_umount_NETFS_dir.sh
2025-08-07 19:30:18.152225110 Finished running 'verify' stage in 1 seconds
2025-08-07 19:30:18.155355093 ======================
2025-08-07 19:30:18.159415311 Running 'layout/prepare' stage
2025-08-07 19:30:18.163856644 ======================
2025-08-07 19:30:18.181305924 Including layout/prepare/default/010_prepare_files.sh
2025-08-07 19:30:18.203513347 Including layout/prepare/GNU/Linux/100_include_partition_code.sh
2025-08-07 19:30:18.243384723 Including layout/prepare/GNU/Linux/110_include_lvm_code.sh
2025-08-07 19:30:18.282409485 Including layout/prepare/GNU/Linux/120_include_raid_code.sh
2025-08-07 19:30:18.301250050 Including layout/prepare/GNU/Linux/131_include_filesystem_code.sh
2025-08-07 19:30:18.323534790 Including layout/prepare/GNU/Linux/133_include_mount_filesystem_code.sh
2025-08-07 19:30:18.344246998 Including layout/prepare/GNU/Linux/135_include_btrfs_subvolumes_generic_code.sh
2025-08-07 19:30:18.364319289 Including layout/prepare/GNU/Linux/136_include_btrfs_subvolumes_SLES_code.sh
2025-08-07 19:30:18.387250395 Including layout/prepare/GNU/Linux/140_include_swap_code.sh
2025-08-07 19:30:18.420164439 Including layout/prepare/GNU/Linux/150_include_drbd_code.sh
2025-08-07 19:30:18.439244871 Including layout/prepare/GNU/Linux/160_include_luks_code.sh
2025-08-07 19:30:18.459610578 Including layout/prepare/GNU/Linux/170_include_hpraid_code.sh
2025-08-07 19:30:18.479634334 Including layout/prepare/GNU/Linux/180_include_opaldisk_code.sh
2025-08-07 19:30:18.499255492 Including layout/prepare/default/200_recreate_hpraid.sh
2025-08-07 19:30:18.522519507 Including layout/prepare/GNU/Linux/210_load_multipath.sh
2025-08-07 19:30:18.546508216 Including layout/prepare/default/250_compare_disks.sh
2025-08-07 19:30:18.556922669 Enforced manual disk layout configuration (MIGRATION_MODE is 'true')
2025-08-07 19:30:18.577413014 Including layout/prepare/default/270_overrule_migration_mode.sh
2025-08-07 19:30:18.601346563 Including layout/prepare/default/300_map_disks.sh
2025-08-07 19:30:19.186847186 Original disk /dev/nvme0n1 does not exist (with same size) in the target system
2025-08-07 19:30:19.211437696 '/dev/nvme0n1' is not write-protected (empty WRITE_PROTECTED_IDS and WRITE_PROTECTED_FS_LABEL_PATTERNS)
2025-08-07 19:30:19.221301161 sda excluded from device mapping choices (is a removable device)
2025-08-07 19:30:19.231341758 Using /dev/nvme0n1 (the only available of the disks) for recreating /dev/nvme0n1
2025-08-07 19:30:19.256124896 Original disk /dev/sda does not exist (with same size) in the target system
2025-08-07 19:30:19.281310294 /dev/nvme0n1 excluded from device mapping choices (is already used as mapping target)
2025-08-07 19:30:19.291467382 sda excluded from device mapping choices (is a removable device)
2025-08-07 19:30:19.301268783 No device found where to /dev/sda could be mapped so that it will not be recreated
2025-08-07 19:30:19.326550650 Original disk /dev/sdb does not exist (with same size) in the target system
2025-08-07 19:30:19.352043308 /dev/nvme0n1 excluded from device mapping choices (is already used as mapping target)
2025-08-07 19:30:19.361804537 sda excluded from device mapping choices (is a removable device)
2025-08-07 19:30:19.371613940 No device found where to /dev/sdb could be mapped so that it will not be recreated
2025-08-07 19:30:19.396744789 Original disk /dev/sdc does not exist (with same size) in the target system
2025-08-07 19:30:19.422423956 /dev/nvme0n1 excluded from device mapping choices (is already used as mapping target)
2025-08-07 19:30:19.432391674 sda excluded from device mapping choices (is a removable device)
2025-08-07 19:30:19.442208822 No device found where to /dev/sdc could be mapped so that it will not be recreated
2025-08-07 19:30:19.465250793 Current disk mapping table (source => target):
                                /dev/nvme0n1 => /dev/nvme0n1
2025-08-07 19:30:19.524563329 Currently unmapped disks and dependent devices will not be recreated
                              (unless identical disk mapping and proceeding without manual configuration):
                                /dev/sda /dev/sda1
                                /dev/sdb /dev/sdb1
                                /dev/sdc /dev/sdc1
2025-08-07 19:30:19.550687301 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:30:19.564085411 UserInput: called in /usr/share/rear/layout/prepare/default/300_map_disks.sh line 334
2025-08-07 19:30:19.579874562 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:30:19.589705960 Confirm or edit the disk mapping
2025-08-07 19:30:19.601865228 1) Confirm disk mapping and continue 'rear recover'
2025-08-07 19:30:19.615013496 2) Confirm identical disk mapping and proceed without manual configuration
2025-08-07 19:30:19.628077058 3) Edit disk mapping (/var/lib/rear/layout/disk_mappings)
2025-08-07 19:30:19.640833441 4) Use Relax-and-Recover shell and return back to here
2025-08-07 19:30:19.653684110 5) Abort 'rear recover'
2025-08-07 19:30:19.666110769 (default '1' timeout 300 seconds)
2025-08-07 19:30:21.851958856 UserInput: 'read' got as user input '1'
2025-08-07 19:30:21.868818782 User confirmed disk mapping
2025-08-07 19:30:21.898545112 Disk /dev/sda and all dependent devices will not be recreated
2025-08-07 19:30:21.948906291 Disk /dev/sdb and all dependent devices will not be recreated
2025-08-07 19:30:21.999280334 Disk /dev/sdc and all dependent devices will not be recreated
2025-08-07 19:30:22.054512305 Including layout/prepare/default/310_remove_exclusions.sh
2025-08-07 19:30:22.078246951 Disabling component 'disk /dev/sda' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.111163741 Disabling component 'part /dev/sda' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.136678030 Disabling component 'disk /dev/sdb' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.169875415 Disabling component 'part /dev/sdb' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.196766378 Disabling component 'disk /dev/sdc' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.229786838 Disabling component 'part /dev/sdc' in /var/lib/rear/layout/disklayout.conf
2025-08-07 19:30:22.264301285 Including layout/prepare/default/319_rename_xfs_configs.sh
2025-08-07 19:30:22.326806412 Including layout/prepare/default/320_apply_mappings.sh
2025-08-07 19:30:22.342621120 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:30:22.357967586 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:30:22.373669364 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:30:22.399437315 Including layout/prepare/default/420_autoresize_last_partitions.sh
2025-08-07 19:30:22.410750724 Trying to automatically resize last partition when disk size changed
2025-08-07 19:30:22.553243622 Last partition /dev/nvme0n1p3 must shrink by 6001000448 bytes to still fit on device
2025-08-07 19:30:22.574641296 Shrinking last partition /dev/nvme0n1p3 to end of device (new device at most 90% smaller)
2025-08-07 19:30:22.593739298 Changed last partition /dev/nvme0n1p3 size from 255010537472 to 249009537024 bytes
2025-08-07 19:30:22.631689806 Including layout/prepare/default/430_autoresize_all_partitions.sh
2025-08-07 19:30:22.652868958 Including layout/prepare/default/500_confirm_layout_file.sh
2025-08-07 19:30:22.671705742 UserInput: called in /usr/share/rear/layout/prepare/default/500_confirm_layout_file.sh line 26
2025-08-07 19:30:22.687884999 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:30:22.697973377 Confirm or edit the disk layout file
2025-08-07 19:30:22.711632186 1) Confirm disk layout and continue 'rear recover'
2025-08-07 19:30:22.726114523 2) Edit disk layout (/var/lib/rear/layout/disklayout.conf)
2025-08-07 19:30:22.739828374 3) View disk layout (/var/lib/rear/layout/disklayout.conf)
2025-08-07 19:30:22.751639991 4) View original disk space usage (/var/lib/rear/layout/config/df.txt)
2025-08-07 19:30:22.766487329 5) Use Relax-and-Recover shell and return back to here
2025-08-07 19:30:22.781070078 6) Abort 'rear recover'
2025-08-07 19:30:22.795070890 (default '1' timeout 300 seconds)
2025-08-07 19:30:24.532007746 UserInput: 'read' got as user input '1'
2025-08-07 19:30:24.549319644 User confirmed disk layout file
2025-08-07 19:30:24.574675943 Including layout/prepare/default/510_list_dependencies.sh
2025-08-07 19:30:24.938489191 Including layout/prepare/default/520_exclude_components.sh
2025-08-07 19:30:24.964770418 Including layout/prepare/default/540_generate_device_code.sh
2025-08-07 19:30:26.011122666 Begin create_fs( fs:/ )
2025-08-07 19:30:26.028004334 Begin generating code to create XFS on /dev/mapper/vg-root ...
2025-08-07 19:30:26.047857362 Parsing vg-root mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-root.xfs
2025-08-07 19:30:26.547918596 Using vg-root mkfs.xfs options: -i size=512 -d agcount=4 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:26.559861229 End of generating code to create XFS on /dev/mapper/vg-root
2025-08-07 19:30:26.569520518 Begin mount_fs( fs:/ )
2025-08-07 19:30:26.591042287 End mount_fs( fs:/ )
2025-08-07 19:30:26.600839114 End create_fs( fs:/ )
2025-08-07 19:30:26.658839058 Begin create_fs( fs:/home )
2025-08-07 19:30:26.676018526 Begin generating code to create XFS on /dev/mapper/vg-home ...
2025-08-07 19:30:26.695993002 Parsing vg-home mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-home.xfs
2025-08-07 19:30:27.199804153 Using vg-home mkfs.xfs options: -i size=512 -d agcount=4 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:27.212001277 End of generating code to create XFS on /dev/mapper/vg-home
2025-08-07 19:30:27.221821321 Begin mount_fs( fs:/home )
2025-08-07 19:30:27.243765336 End mount_fs( fs:/home )
2025-08-07 19:30:27.253750818 End create_fs( fs:/home )
2025-08-07 19:30:27.311909947 Begin create_fs( fs:/opt )
2025-08-07 19:30:27.329101199 Begin generating code to create XFS on /dev/mapper/vg-opt ...
2025-08-07 19:30:27.349432152 Parsing vg-opt mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-opt.xfs
2025-08-07 19:30:27.851305742 Using vg-opt mkfs.xfs options: -i size=512 -d agcount=4 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:27.863803625 End of generating code to create XFS on /dev/mapper/vg-opt
2025-08-07 19:30:27.873616502 Begin mount_fs( fs:/opt )
2025-08-07 19:30:27.895351409 End mount_fs( fs:/opt )
2025-08-07 19:30:27.905183726 End create_fs( fs:/opt )
2025-08-07 19:30:27.963475884 Begin create_fs( fs:/tmp )
2025-08-07 19:30:27.980663555 Begin generating code to create XFS on /dev/mapper/vg-tmp ...
2025-08-07 19:30:28.001185226 Parsing vg-tmp mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-tmp.xfs
2025-08-07 19:30:28.500377182 Using vg-tmp mkfs.xfs options: -i size=512 -d agcount=9 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:28.512682720 End of generating code to create XFS on /dev/mapper/vg-tmp
2025-08-07 19:30:28.522640186 Begin mount_fs( fs:/tmp )
2025-08-07 19:30:28.544458975 End mount_fs( fs:/tmp )
2025-08-07 19:30:28.554393159 End create_fs( fs:/tmp )
2025-08-07 19:30:28.612813125 Begin create_fs( fs:/usr )
2025-08-07 19:30:28.630412145 Begin generating code to create XFS on /dev/mapper/vg-usr ...
2025-08-07 19:30:28.651126705 Parsing vg-usr mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-usr.xfs
2025-08-07 19:30:29.157127168 Using vg-usr mkfs.xfs options: -i size=512 -d agcount=4 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:29.169486841 End of generating code to create XFS on /dev/mapper/vg-usr
2025-08-07 19:30:29.179704625 Begin mount_fs( fs:/usr )
2025-08-07 19:30:29.201384716 End mount_fs( fs:/usr )
2025-08-07 19:30:29.211472809 End create_fs( fs:/usr )
2025-08-07 19:30:29.269428558 Begin create_fs( fs:/var )
2025-08-07 19:30:29.286993155 Begin generating code to create XFS on /dev/mapper/vg-var ...
2025-08-07 19:30:29.307231136 Parsing vg-var mkfs.xfs options from /var/lib/rear/layout/xfs/restore/vg-var.xfs
2025-08-07 19:30:29.814529043 Using vg-var mkfs.xfs options: -i size=512 -d agcount=4 -s size=512 -i attr=2 -i projid32bit=1 -m crc=1 -m finobt=1 -b size=4096 -i maxpct=25 -d sunit=0 -d swidth=0 -l version=2 -l lazy-count=1 -n size=4096 -n version=2 -r extsize=4096 
2025-08-07 19:30:29.826864968 End of generating code to create XFS on /dev/mapper/vg-var
2025-08-07 19:30:29.836818382 Begin mount_fs( fs:/var )
2025-08-07 19:30:29.858449658 End mount_fs( fs:/var )
2025-08-07 19:30:29.868366175 End create_fs( fs:/var )
2025-08-07 19:30:29.944717721 Begin create_fs( fs:/boot )
2025-08-07 19:30:29.965572012 Begin mount_fs( fs:/boot )
2025-08-07 19:30:29.985301192 End mount_fs( fs:/boot )
2025-08-07 19:30:29.995435695 End create_fs( fs:/boot )
2025-08-07 19:30:30.057285839 Begin create_fs( fs:/boot/efi )
2025-08-07 19:30:30.087196185 Begin mount_fs( fs:/boot/efi )
2025-08-07 19:30:30.106271398 End mount_fs( fs:/boot/efi )
2025-08-07 19:30:30.116097958 End create_fs( fs:/boot/efi )
2025-08-07 19:30:30.217017872 Including layout/prepare/default/550_finalize_script.sh
2025-08-07 19:30:30.241402263 Including layout/prepare/default/600_show_unprocessed.sh
2025-08-07 19:30:30.269838564 Including layout/prepare/default/610_exclude_from_restore.sh
2025-08-07 19:30:30.282179423 Finished running 'layout/prepare' stage in 12 seconds
2025-08-07 19:30:30.293731301 ======================
2025-08-07 19:30:30.305066646 Running 'layout/recreate' stage
2025-08-07 19:30:30.316301071 ======================
2025-08-07 19:30:30.345363693 Including layout/recreate/default/100_confirm_layout_code.sh
2025-08-07 19:30:30.364196955 UserInput: called in /usr/share/rear/layout/recreate/default/100_confirm_layout_code.sh line 26
2025-08-07 19:30:30.380542786 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:30:30.390711159 Confirm or edit the disk recreation script
2025-08-07 19:30:30.405573552 1) Confirm disk recreation script and continue 'rear recover'
2025-08-07 19:30:30.420199518 2) Edit disk recreation script (/var/lib/rear/layout/diskrestore.sh)
2025-08-07 19:30:30.433645595 3) View disk recreation script (/var/lib/rear/layout/diskrestore.sh)
2025-08-07 19:30:30.447566637 4) View original disk space usage (/var/lib/rear/layout/config/df.txt)
2025-08-07 19:30:30.460599120 5) Use Relax-and-Recover shell and return back to here
2025-08-07 19:30:30.472508866 6) Abort 'rear recover'
2025-08-07 19:30:30.484541420 (default '1' timeout 300 seconds)
2025-08-07 19:30:31.716129867 UserInput: 'read' got as user input '1'
2025-08-07 19:30:31.733570901 User confirmed disk recreation script
2025-08-07 19:30:31.761736377 Including layout/recreate/default/120_confirm_wipedisk_disks.sh
2025-08-07 19:30:31.781083363 Disks to be completely overwritten and recreated by /var/lib/rear/layout/diskrestore.sh:
2025-08-07 19:30:31.796465491   /dev/nvme0n1 
2025-08-07 19:30:31.812238355 Determining disks to be wiped ...
2025-08-07 19:30:31.827631563 '/dev/nvme0n1' is not write-protected (empty WRITE_PROTECTED_IDS and WRITE_PROTECTED_FS_LABEL_PATTERNS)
2025-08-07 19:30:31.843190810 UserInput: called in /usr/share/rear/layout/recreate/default/120_confirm_wipedisk_disks.sh line 168
2025-08-07 19:30:31.859944266 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:30:31.870273823 Disks to be wiped: /dev/nvme0n1 
2025-08-07 19:30:31.883510281 1) Confirm disks to be wiped and continue 'rear recover'
2025-08-07 19:30:31.898053988 2) Skip wiping disks and continue 'rear recover'
2025-08-07 19:30:31.912070030 3) Use Relax-and-Recover shell and return back to here
2025-08-07 19:30:31.925445504 4) Abort 'rear recover'
2025-08-07 19:30:31.938128970 (default '1' timeout 300 seconds)
2025-08-07 19:30:35.540153386 UserInput: 'read' got as user input '1'
2025-08-07 19:30:35.558161691 User confirmed disks to be wiped
2025-08-07 19:30:35.580197521 Including layout/recreate/default/150_wipe_disks.sh
2025-08-07 19:30:35.591369408 Block devices structure on the unchanged replacement hardware before the disks /dev/nvme0n1  will be wiped (lsblk):
2025-08-07 19:30:35.615703250 NAME             KNAME          PKNAME       TRAN   TYPE FSTYPE        SIZE MOUNTPOINT
                              /dev/sda         /dev/sda                    usb    disk              59.8G 
                              |-/dev/sda1      /dev/sda1      /dev/sda            part exfat        59.7G /mnt/tmp
                              `-/dev/sda2      /dev/sda2      /dev/sda            part vfat           32M 
                              /dev/nvme0n1     /dev/nvme0n1                nvme   disk             232.9G 
                              |-/dev/nvme0n1p1 /dev/nvme0n1p1 /dev/nvme0n1 nvme   part vfat          512M 
                              |-/dev/nvme0n1p2 /dev/nvme0n1p2 /dev/nvme0n1 nvme   part ext4          488M 
                              `-/dev/nvme0n1p3 /dev/nvme0n1p3 /dev/nvme0n1 nvme   part LVM2_member 231.9G 
2025-08-07 19:30:36.083018632 Wiping child devices of /dev/nvme0n1 in reverse ordering: /dev/nvme0n1p3 /dev/nvme0n1p2 /dev/nvme0n1p1 /dev/nvme0n1 
2025-08-07 19:30:36.283191404 Remaining block devices structure after the disks /dev/nvme0n1  were wiped (lsblk):
2025-08-07 19:30:36.288587455 NAME         KNAME        PKNAME   TRAN   TYPE FSTYPE   SIZE MOUNTPOINT
                              /dev/sda     /dev/sda              usb    disk         59.8G 
                              |-/dev/sda1  /dev/sda1    /dev/sda        part exfat   59.7G /mnt/tmp
                              `-/dev/sda2  /dev/sda2    /dev/sda        part vfat      32M 
                              /dev/nvme0n1 /dev/nvme0n1          nvme   disk        232.9G 
2025-08-07 19:30:36.293105719 Including layout/recreate/default/200_run_layout_code.sh
2025-08-07 19:30:36.297233008 Start system layout restoration.
2025-08-07 19:30:36.375442988 Stop mdadm
2025-08-07 19:30:36.388920450 Erasing MBR of disk /dev/nvme0n1
2025-08-07 19:30:36.405875824 Disk '/dev/nvme0n1': creating 'gpt' partition table
2025-08-07 19:30:36.491138898 Disk '/dev/nvme0n1': creating partition number 1 with name ''EFI System Partition''
2025-08-07 19:30:36.878308652 Disk '/dev/nvme0n1': creating partition number 2 with name ''nvme0n1p2''
2025-08-07 19:30:37.060450695 Disk '/dev/nvme0n1': creating partition number 3 with name ''nvme0n1p3''
2025-08-07 19:30:38.624638297 Creating LVM PV /dev/nvme0n1p3
2025-08-07 19:30:38.802990766 Creating LVM VG 'vg' (some properties may not be preserved)
2025-08-07 19:30:39.067857801 Creating LVM volume 'vg/home' (some properties may not be preserved)
2025-08-07 19:30:39.156077530 Creating LVM volume 'vg/opt' (some properties may not be preserved)
2025-08-07 19:30:39.267910213 Creating LVM volume 'vg/swap' (some properties may not be preserved)
2025-08-07 19:30:39.356480926 Creating LVM volume 'vg/tmp' (some properties may not be preserved)
2025-08-07 19:30:39.448119142 Creating LVM volume 'vg/root' (some properties may not be preserved)
2025-08-07 19:30:39.536312881 Creating LVM volume 'vg/var' (some properties may not be preserved)
2025-08-07 19:30:39.652241799 Creating LVM volume 'vg/usr' (some properties may not be preserved)
2025-08-07 19:30:39.781999811 Creating filesystem of type xfs with mount point / on /dev/mapper/vg-root.
2025-08-07 19:30:39.966015537 Mounting filesystem /
2025-08-07 19:30:40.313604565 Creating filesystem of type xfs with mount point /home on /dev/mapper/vg-home.
2025-08-07 19:30:40.481852909 Mounting filesystem /home
2025-08-07 19:30:40.542074684 Creating filesystem of type xfs with mount point /opt on /dev/mapper/vg-opt.
2025-08-07 19:30:40.726304240 Mounting filesystem /opt
2025-08-07 19:30:40.781892599 Creating filesystem of type xfs with mount point /tmp on /dev/mapper/vg-tmp.
2025-08-07 19:30:40.987707465 Mounting filesystem /tmp
2025-08-07 19:30:41.036600435 Creating filesystem of type xfs with mount point /usr on /dev/mapper/vg-usr.
2025-08-07 19:30:41.285694301 Mounting filesystem /usr
2025-08-07 19:30:41.349978422 Creating filesystem of type xfs with mount point /var on /dev/mapper/vg-var.
2025-08-07 19:30:41.701420277 Mounting filesystem /var
2025-08-07 19:30:41.743232251 Creating filesystem of type ext4 with mount point /boot on /dev/nvme0n1p2.
2025-08-07 19:30:41.827302386 Mounting filesystem /boot
2025-08-07 19:30:41.959866086 Creating filesystem of type vfat with mount point /boot/efi on /dev/nvme0n1p1.
2025-08-07 19:30:42.010474123 Mounting filesystem /boot/efi
2025-08-07 19:30:42.058515746 Creating swap on /dev/mapper/vg-swap
2025-08-07 19:30:42.066608063 Disk layout created.
2025-08-07 19:30:42.071048265 Recreated storage layout:
2025-08-07 19:30:42.080815791 UserInput: called in /usr/share/rear/layout/recreate/default/200_run_layout_code.sh line 168
2025-08-07 19:30:42.086549185 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:30:42.089223982 Confirm the recreated disk layout or go back one step
NAME                    KNAME          TRAN   TYPE FSTYPE      LABEL     SIZE MOUNTPOINTS
/dev/sda                /dev/sda       usb    disk                      59.8G 
|-/dev/sda1             /dev/sda1             part exfat       Ventoy   59.7G /mnt/tmp
`-/dev/sda2             /dev/sda2             part vfat        VTOYEFI    32M 
/dev/nvme0n1            /dev/nvme0n1   nvme   disk                     232.9G 
|-/dev/nvme0n1p1        /dev/nvme0n1p1 nvme   part vfat                  512M /mnt/local/boot/efi
|-/dev/nvme0n1p2        /dev/nvme0n1p2 nvme   part ext4        boot      488M /mnt/local/boot
`-/dev/nvme0n1p3        /dev/nvme0n1p3 nvme   part LVM2_member         231.9G 
  |-/dev/mapper/vg-home /dev/dm-0             lvm  xfs                   976M /mnt/local/home
  |-/dev/mapper/vg-opt  /dev/dm-1             lvm  xfs                   976M /mnt/local/opt
  |-/dev/mapper/vg-swap /dev/dm-2             lvm  swap                  976M 
  |-/dev/mapper/vg-tmp  /dev/dm-3             lvm  xfs                   1.9G /mnt/local/tmp
  |-/dev/mapper/vg-root /dev/dm-4             lvm  xfs                   2.8G /mnt/local
  |-/dev/mapper/vg-var  /dev/dm-5             lvm  xfs         var       2.8G /mnt/local/var
  `-/dev/mapper/vg-usr  /dev/dm-6             lvm  xfs         usr       4.7G /mnt/local/usr
2025-08-07 19:30:42.104796648 1) Confirm recreated disk layout and continue 'rear recover'
2025-08-07 19:30:42.108856136 2) Go back one step to redo disk layout recreation
2025-08-07 19:30:42.112475634 3) Use Relax-and-Recover shell and return back to here
2025-08-07 19:30:42.116391183 4) Abort 'rear recover'
2025-08-07 19:30:42.120565828 (default '1' timeout 300 seconds)
2025-08-07 19:30:44.204030143 UserInput: 'read' got as user input '1'
2025-08-07 19:30:44.220820187 User confirmed recreated disk layout
2025-08-07 19:30:44.246221749 Including layout/recreate/default/220_verify_layout.sh
2025-08-07 19:30:44.279766425 Including layout/recreate/default/250_verify_mount.sh
2025-08-07 19:30:44.297571313 Finished running 'layout/recreate' stage in 14 seconds
2025-08-07 19:30:44.308511339 ======================
2025-08-07 19:30:44.319812104 Running 'restore' stage
2025-08-07 19:30:44.330997981 ======================
2025-08-07 19:30:44.360226333 Including restore/default/050_remount_async.sh
2025-08-07 19:30:44.380484768 Including restore/NETFS/default/100_mount_NETFS_path.sh
2025-08-07 19:30:44.409535800 Including restore/NETFS/default/200_remove_relative_rsync_option.sh
2025-08-07 19:30:44.438639802 Including restore/NETFS/default/380_prepare_multiple_isos.sh
2025-08-07 19:30:44.472693930 Including restore/NETFS/default/400_restore_backup.sh
2025-08-07 19:30:44.510339700 Restoring from '/media/rear/rpi5-killer/backup.tar.gz' (restore log in /var/lib/rear/restore/recover.backup.tar.gz.568.restore.log) ...
2025-08-07 19:30:44.525387337 Launched backup restore subshell (PID=5799)
2025-08-07 19:30:44.525387356 dd if=/media/rear/rpi5-killer/backup.tar.gz bs=1M | tar --block-number --totals --verbose --anchored --xattrs --xattrs-include=security.capability --xattrs-include=security.selinux --acls --gzip -C /mnt/local/ -x -f -
2025-08-07 19:31:05.628536213 Restored 3225 MiB in 21 seconds [avg. 157271 KiB/sec]
2025-08-07 19:31:05.643713628 Restoring finished (verify backup restore log messages in /var/lib/rear/restore/recover.backup.tar.gz.568.restore.log)
2025-08-07 19:31:05.670402287 Including restore/NETFS/default/500_selinux_autorelabel.sh
2025-08-07 19:31:05.704614687 Including restore/NETFS/Linux-i386/510_selinux_fixfiles_exclude_dirs.sh
2025-08-07 19:31:05.725658664 Including restore/NETFS/default/510_set_capabilities.sh
2025-08-07 19:31:05.746369504 Including restore/default/900_create_missing_directories.sh
2025-08-07 19:31:05.758070020 Recreating directories (with permissions) from /var/lib/rear/recovery/directories_permissions_owner_group
2025-08-07 19:31:05.792673852 Including restore/default/950_restore_esp.sh
2025-08-07 19:31:05.814025935 Including restore/NETFS/default/980_umount_NETFS_dir.sh
2025-08-07 19:31:05.843453456 Including restore/default/990_move_away_restored_files.sh
2025-08-07 19:31:05.880381627 Including restore/default/995_remount_sync.sh
2025-08-07 19:31:05.892190290 Finished running 'restore' stage in 21 seconds
2025-08-07 19:31:05.903614807 ======================
2025-08-07 19:31:05.914855976 Running 'finalize' stage
2025-08-07 19:31:05.925952666 ======================
2025-08-07 19:31:05.955701229 Including finalize/default/050_prepare_checks.sh
2025-08-07 19:31:05.981518948 Including finalize/default/060_compare_files.sh
2025-08-07 19:31:05.992220416 Checking if certain restored files are consistent with the recreated system
2025-08-07 19:31:06.028015653 Including finalize/default/110_bind_mount_proc_sys_dev_run.sh
2025-08-07 19:31:06.107386290 Including finalize/GNU/Linux/230_remove_lvmdevices.sh
2025-08-07 19:31:06.128145542 Including finalize/GNU/Linux/240_reassign_luks_keyfiles.sh
2025-08-07 19:31:06.156907461 Including finalize/GNU/Linux/250_migrate_disk_devices_layout.sh
2025-08-07 19:31:06.172966315 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:31:06.193341809 Including finalize/GNU/Linux/250_migrate_lun_wwid.sh
2025-08-07 19:31:06.214181546 Including finalize/GNU/Linux/260_rename_diskbyid.sh
2025-08-07 19:31:06.230386702 Completely identical layout mapping in /var/lib/rear/layout/disk_mappings
2025-08-07 19:31:06.926115459 Migrating disk-by-id mappings in certain restored files in /mnt/local to current disk-by-id mappings ...
2025-08-07 19:31:07.617939805 Including finalize/GNU/Linux/280_migrate_uuid_tags.sh
2025-08-07 19:31:07.639478161 Including finalize/GNU/Linux/300_create_mac_mapping.sh
2025-08-07 19:31:07.660325965 Including finalize/GNU/Linux/310_migrate_udev_rules.sh
2025-08-07 19:31:07.681933395 Including finalize/GNU/Linux/320_migrate_network_configuration_files.sh
2025-08-07 19:31:07.696155912 Patching /mnt/local/etc/network/interfaces
2025-08-07 19:31:07.727497355 Migrating restored network configuration files according to the mapping files ...
2025-08-07 19:31:07.742388683 Rewriting changed MAC addresses and network interfaces
2025-08-07 19:31:07.782964135 Wrote new MAC addresses and network interfaces in '/mnt/local/etc/network/interfaces'
2025-08-07 19:31:07.811818488 Including finalize/GNU/Linux/430_create_multipath_config.sh
2025-08-07 19:31:07.834529840 Including finalize/default/520_confirm_finalize.sh
2025-08-07 19:31:07.853553532 UserInput: called in /usr/share/rear/finalize/default/520_confirm_finalize.sh line 41
2025-08-07 19:31:07.869689496 UserInput: Default input in choices - using choice number 1 as default input
2025-08-07 19:31:07.879793191 Confirm restored config files are OK or adapt them as needed
2025-08-07 19:31:07.893639943 1) Confirm it is OK to recreate initrd and reinstall bootloader and continue 'rear recover'
2025-08-07 19:31:07.908446966 2) Edit restored etc/fstab (/mnt/local/etc/fstab)
2025-08-07 19:31:07.921370131 3) View restored etc/fstab (/mnt/local/etc/fstab)
2025-08-07 19:31:07.931926263 4) Use Relax-and-Recover shell and return back to here
2025-08-07 19:31:07.940570856 5) Abort 'rear recover'
2025-08-07 19:31:07.947940651 (default '1' timeout 300 seconds)
2025-08-07 19:31:09.907793657 UserInput: 'read' got as user input '1'
2025-08-07 19:31:09.925383767 User confirmed restored files
2025-08-07 19:31:09.952197652 Including finalize/Debian/i386/550_rebuild_initramfs.sh
2025-08-07 19:33:10.485148083 Updated initramfs with new drivers for this system.
2025-08-07 19:33:10.490548896 Including finalize/Linux-i386/610_EFISTUB_run_efibootmgr.sh
2025-08-07 19:33:10.494616034 Including finalize/Linux-i386/630_install_grub.sh
2025-08-07 19:33:10.498892393 Including finalize/Linux-i386/640_install_lilo.sh
2025-08-07 19:33:10.503618560 Including finalize/Linux-i386/650_install_elilo.sh
2025-08-07 19:33:10.509006067 Including finalize/Linux-i386/660_install_grub2.sh
2025-08-07 19:33:10.514659690 Including finalize/Linux-i386/670_run_efibootmgr.sh
2025-08-07 19:33:10.517766778 Creating EFI Boot Manager entries...
2025-08-07 19:33:10.600076811 Creating  EFI Boot Manager entry 'Debian 12' for 'EFI\debian\grubx64.efi' (UEFI_BOOTLOADER='/boot/efi/EFI/debian/grubx64.efi') 
2025-08-07 19:33:10.614054048 efibootmgr --create --gpt --disk /dev/nvme0n1 --part 1 --write-signature --label "Debian 12" --loader "\EFI\debian\grubx64.efi"
2025-08-07 19:33:10.657088198 Including finalize/default/880_check_for_mount_by_id.sh
2025-08-07 19:33:10.680991299 Including finalize/default/890_finish_checks.sh
2025-08-07 19:33:10.709958933 Including finalize/default/900_remount_sync.sh
2025-08-07 19:33:10.720978334 Finished running 'finalize' stage in 125 seconds
2025-08-07 19:33:10.731814108 ======================
2025-08-07 19:33:10.742365722 Running 'wrapup' stage
2025-08-07 19:33:10.752999274 ======================
2025-08-07 19:33:10.780578956 Including wrapup/default/500_post_recovery_script.sh
2025-08-07 19:33:10.799806183 Including wrapup/default/980_good_bye.sh
2025-08-07 19:33:10.823596854 Including wrapup/default/990_copy_logfile.sh
2025-08-07 19:33:10.850317804 Finished running 'wrapup' stage in 0 seconds
2025-08-07 19:33:10.861128670 Finished running recover workflow
2025-08-07 19:33:10.878741504 Exiting rear recover (PID 568) and its descendant processes ...
2025-08-07 19:33:10.914190873 rear,568 /bin/rear -v recover
                                `-rear,20478 /bin/rear -v recover
                                    `-pstree,20479 -Aplau 568
2025-08-07 19:33:10.940610399 Running exit tasks
 

recover.backup.tar.gz.568.restore.log

95%-ig ledokumentáltam a DR-t. Aki szeretne tanulhat belőle, mondjuk a PH :)

( Fisher v | 2025. 05. 19., h – 07:03 )

Ezt a reart nem nagyon vágom, de ez még nem csak a backup volt? Backupot csinálni könnyű, helyreállítani az érdekes.

(Mármint értem én, hogy ez így őrülten biztos hogy jó lesz, de na...)

Nálunk a cégnél 2 db REAR akalmazás specialista van összesen(én is :), mi csináljuk a DR teszteket és dokumentáljuk a hibákat fizikai és virtuális gépeken is. SLES/RH/Debian. Nem árt sokat tesztelni, mert vannak bugok rendesen, főleg HW szerveren, virtuális gépeken aránylag jól megy. Én még az mkcdrec-el kezdtem. Debian a legjobb utána jön a SLES majd RH. A RedHattel szívtam a legtöbbet ...

A REAR az nem nehéz, Zabbix 6.0 LTS-hez fejlesztettem(ünk) Templatet IBM FS9500-hoz(HPE Primera by HTTP Template alapján), IBM RESTFUL API-t és Zabbix 6.0 LTS API alkalmazásával Duktapet használva és 1 db BASH script + 1 cron jobbal. Ez már megüti a bonyolult szintet szerintem. :)