# rear -v -d -D mkbackup
Relax-and-Recover 2.9 / 2025-01-31
Running rear mkbackup (PID 91846 date 2025-10-17 19:55:43)
Command line options: /usr/sbin/rear -v -d -D mkbackup
Using log file: /var/log/rear/rear-server-11-0-x86-64-minimal-20251017.log
Using build area: /tmp/.private/root/rear.7hwmMjZ9rUre2h5
Changing TMPDIR to ReaR's '/tmp/.private/root/rear.7hwmMjZ9rUre2h5/tmp' (was '/tmp/.private/root' when ReaR was launched)
Sourced files must be owned by one of the TRUSTED_OWNERS: root
Sourced files must be below one of the TRUSTED_PATHS: /usr/ /etc/ /var/lib/rear/ /lib/
Running 'init' stage ======================
Running workflow mkbackup on the normal/original system
Running 'prep' stage ======================
No 'console=...' setting for recovery system kernel (none in /proc/cmdline)
Using '/usr/bin/mkisofs' to create ISO filesystem images
mokutil not found, cannot detect Secure Boot status, not using Secure Boot shim
Using autodetected kernel '/boot/vmlinuz-6.12.52-6.12-alt1' as kernel in the recovery system
Modified ReaR recovery system area after 'prep' stage (/tmp/.private/root/rear.7hwmMjZ9rUre2h5/rootfs contains regular files)
Running 'layout/save' stage ======================
Creating disk layout
Overwriting existing disk layout file /var/lib/rear/layout/disklayout.conf
Automatically excluding disk /dev/sdb (not used by any mounted filesystem)
Marking component '/dev/sdb' as done in /var/lib/rear/layout/disktodo.conf
Dependent component /dev/sdb1 is a child of component /dev/sdb
Marking component '/dev/sdb1' as done in /var/lib/rear/layout/disktodo.conf
Dependent component /dev/sdb2 is a child of component /dev/sdb
Marking component '/dev/sdb2' as done in /var/lib/rear/layout/disktodo.conf
Dependent component /dev/sdb3 is a child of component /dev/sdb
Marking component '/dev/sdb3' as done in /var/lib/rear/layout/disktodo.conf
Disabling excluded components in /var/lib/rear/layout/disklayout.conf
Disabling component 'disk /dev/sdb' in /var/lib/rear/layout/disklayout.conf
Disabling component 'part /dev/sdb' in /var/lib/rear/layout/disklayout.conf
Component 'part /dev/sdb' is disabled in /var/lib/rear/layout/disklayout.conf
Component 'part /dev/sdb' is disabled in /var/lib/rear/layout/disklayout.conf
GRUB found in first bytes on /dev/sda and GRUB 2 is installed, using GRUB2 as a guessed bootloader for 'rear recover'
Skip saving storage layout as 'barrel' devicegraph (no 'barrel' command)
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)
Running 'rescue' stage ======================
Creating recovery system root filesystem skeleton layout
Handling network interface 'ens19'
ens19 is a physical device
Handled network interface 'ens19'
Skipping network interface 'lo': not bound to any physical interface.
Included current keyboard mapping (via 'dumpkeys -f')
Included default US keyboard mapping /lib/kbd/keymaps/i386/qwerty/defkeymap.map.gz
Included other keyboard mappings in /lib/kbd/keymaps
Copying logfile /var/log/rear/rear-server-11-0-x86-64-minimal-20251017.log into initramfs as '/tmp/rear-server-11-0-x86-64-minimal-20251017-partial-2025-10-17T19:55:54+03:00.log'
Running 'build' stage ======================
Copying files and directories
Copying binaries and libraries
Copying all kernel modules in /lib/modules/6.12.52-6.12-alt1 (MODULES contains 'all_modules')
Copying all files in /lib*/firmware/
Broken symlink '/usr/lib/firmware/libertas/sd8688_helper.bin.xz' in recovery system because 'readlink' cannot determine its link target
Broken symlink '/usr/lib/firmware/libertas/sd8688.bin.xz' in recovery system because 'readlink' cannot determine its link target
Broken symlink '/usr/lib/firmware/a300_pm4.fw.xz' in recovery system because 'readlink' cannot determine its link target
Broken symlink '/usr/lib/firmware/a300_pfp.fw.xz' in recovery system because 'readlink' cannot determine its link target
Skip copying broken symlink '/etc/mtab' target '/proc/103293/mounts' on /proc/ /sys/ /dev/ or /run/
There is no sshd configuration at /tmp/.private/root/rear.7hwmMjZ9rUre2h5/rootfs/etc/ssh/sshd_config - logging into the rescue system via ssh may not work
Testing that the ReaR recovery system in '/tmp/.private/root/rear.7hwmMjZ9rUre2h5/rootfs' contains a usable system
Testing each binary with 'ldd' for 'not found' libraries within the ReaR recovery system
Testing that the existing programs in the PROGS array can be found as executable command within the ReaR recovery system
Testing that each program in the REQUIRED_PROGS array can be found as executable command within the ReaR recovery system
Running 'pack' stage ======================
Creating recovery/rescue system initramfs/initrd initrd.cgz with gzip default compression
Created initrd.cgz with gzip default compression (656 MiB) in 31 seconds
Running 'output' stage ======================
Making ISO image
ERROR: Could not create ISO image (with /usr/bin/mkisofs)
Some latest log messages since the last called script 820_create_iso_image.sh:
  962
  320
  55544
  2115
  24576
  Unknown charset '(NULL POINTER)'.
  Known charsets are:
  mkisofs: 'iconv -l' lists more available names.
Aborting due to an error, check /var/log/rear/rear-server-11-0-x86-64-minimal-20251017.log for details
Exiting rear mkbackup (PID 91846) and its descendant processes ...
Running exit tasks
To remove the build area you may use (with caution): rm -Rf --one-file-system /tmp/.private/root/rear.7hwmMjZ9rUre2h5
Завершено