Johannes Meixner

Because a Fedora 40 Cloud Base Image uses btrfs subvolumes ``` # findmnt -a -o TARGET,SOURCE -t btrfs TARGET SOURCE / /dev/vda4[/root] |-/home /dev/vda4[/home] `-/var /dev/vda4[/var] ``` and because https://github.com/rear/rear/pull/3175...

I booted the ReaR ISO on a second KVM/QEMU VM with identical virtual disk /dev/vda size 5.0 GiB. I did not get the ReaR recovery system startup messages which indicates...

In the recreated system I did 'poweroff' but it did not do a real poweroff. Instead it looks as if it did a 'reboot' because I got the VM's firmware...

Regarding the kernel command line 'console' option settings: On the original system i.e. in Fedora-Cloud-Base-Generic.x86_64-40-1.14.qcow2 ``` # find / /boot -xdev -type f | xargs grep 'console=.*115200' 2>/dev/null | grep...

@pcahyna thank you for your explanation what may have caused that unexpected automated reboot. Perhaps there was a message somewhere about SELinux and the automated reboot - but at least...

Most likely I didn't pay attention to the messages because I didn't expect something special to happen so I was surprised by the unexpected automated reboot. FWIW: In ReaR we...

I got this after "rear recover" (in my case the modern/default 'lvm vgcfgrestore' method was used): ``` RESCUE localhost:~ # lsblk -ipo NAME,KNAME,TYPE,FSTYPE,SIZE,MOUNTPOINTS /dev/vda NAME KNAME TYPE FSTYPE SIZE MOUNTPOINTS...

There is the same kind of issue with my currently experimental (and therefore intentionally not yet documented) support for the SUSE tool 'barrel', see in particular https://github.com/rear/rear/pull/2876#issuecomment-1278958908 The common generic...

I label it as 'bug' because what we describe in default.conf what user config variables like EXCLUDE_COMPONENTS should do does not work in any case so actually it is a...

Not for ReaR 3.0 - perhaps (as time permits) for ReaR 3.1