Johannes Meixner

I didn't look at the details but ``` PACKAGES+=" nfs-utils" ``` is not something that ReaR supports. 'PACKAGES' is not a ReaR config variable. See usr/share/rear/conf/default.conf what config variables are...

I will have to think about it... We already have a LogPrintError function which is currently used differently, see its description in lib/_input-output-functions.sh For specific usage examples see for example...

Nothing severe or urgent here, so postponed to 'ReaR v3.1' milestone...

@kai-uwe-rommel please attach a "rear -D mkrescue" (or "rear -D mkbackup") debug log file. In general: Caution with possible secrets in a debug log file: When 'rear' is run via...

@kai-uwe-rommel it seems your https://github.com/rear/rear/files/14855435/rear-mkrescue-debug.log is only the terminal output of "rear -D mkrescue" (excerpts) ``` hermes:~ # rear -D mkrescue Relax-and-Recover 2.7 / 2022-07-13 Running rear mkrescue (PID 11791...

@kai-uwe-rommel in your initial description you wrote ``` But the initrd file is in the ISO and seems to be referenced properly in the grub.cfg file. https://github.com/rear/rear/files/14837101/boot.log Please see content...

@kai-uwe-rommel see my "FYI (2)" part in https://github.com/rear/rear/discussions/3184#discussioncomment-8902863 how you may use `KEEP_BUILD_DIR="yes"` to inspect the recovery system contents after "rear mkrescue" so you could inspect in particular your grub.cfg...

@kai-uwe-rommel thank you for your prompt replies! Now I am stuck because everything looks OK (as far as I can see) but things are not OK. I am not a...

As far as I know - at least in the usual cases - SUSE provides Relax-and-Recover (ReaR) only via the SUSE Linux Enterprise High Availability Extension (SLE-HA) which is the...

@kai-uwe-rommel an offhanded idea based on what I vaguely remember from the past about booting issues which we had here at ReaR upstream with POWER architecture: You use 'BACKUP=TSM' which...