updates the ReaR issues pages

docs/issues/2024-02-06.3144.issue.closed.md

@@ -0,0 +1,41 @@
+[\#3144 Issue](https://github.com/rear/rear/issues/3144) `closed`: delete prep/Linux-s390/305\_include\_s390\_tools.sh
+======================================================================================================================
+
+**Labels**: `cleanup`, `fixed / solved / done`
+
+#### <img src="https://avatars.githubusercontent.com/u/26300485?u=9105d243bc9f7ade463a3e52e8dd13fa67837158&v=4" width="50">[pcahyna](https://github.com/pcahyna) opened issue at [2024-02-06 17:44](https://github.com/rear/rear/issues/3144):
+
+the whole check in
+usr/share/rear/prep/Linux-s390/305\_include\_s390\_tools.sh should now
+be deleted, it is useless and potentially harmful (any failure during
+checking /boot will result in all s390 tools omitted from the recovery
+image, with disastrous results).  
+Actually this whole file can then be deleted and the PROG+= lines moved
+to usr/share/rear/conf/Linux-s390x.conf or whatever is appropriate for
+s390 (this file got deleted in cba3590b27bedb526e5b439cd8d4d01e1ec0169a
+without explanation).
+
+*Originally posted by @pcahyna in
+[https://github.com/rear/rear/issues/3136\#issuecomment-1913671596](https://github.com/rear/rear/issues/3136#issuecomment-1913671596)*
+
+#### <img src="https://avatars.githubusercontent.com/in/15368?v=4" width="50">[github-actions](https://github.com/apps/github-actions) commented at [2024-04-07 02:06](https://github.com/rear/rear/issues/3144#issuecomment-2041276233):
+
+Stale issue message
+
+#### <img src="https://avatars.githubusercontent.com/u/48823770?v=4" width="50">[lzaoral](https://github.com/lzaoral) commented at [2024-04-29 11:19](https://github.com/rear/rear/issues/3144#issuecomment-2082459803):
+
+@jsmeix Could you please reassign this issue to me? Thank you!
+
+#### <img src="https://avatars.githubusercontent.com/u/1788608?u=925fc54e2ce01551392622446ece427f51e2f0ce&v=4" width="50">[jsmeix](https://github.com/jsmeix) commented at [2024-04-29 12:13](https://github.com/rear/rear/issues/3144#issuecomment-2082569655):
+
+@lzaoral  
+my pleasure!
+
+#### <img src="https://avatars.githubusercontent.com/in/15368?v=4" width="50">[github-actions](https://github.com/apps/github-actions) commented at [2024-06-29 02:11](https://github.com/rear/rear/issues/3144#issuecomment-2197855875):
+
+Stale issue message
+
+------------------------------------------------------------------------
+
+\[Export of Github issue for
+[rear/rear](https://github.com/rear/rear).\]

docs/issues/2024-07-10.3271.issue.closed.md

@@ -0,0 +1,111 @@
+[\#3271 Issue](https://github.com/rear/rear/issues/3271) `closed`: USB config not working
+=========================================================================================
+
+**Labels**: `support / question`
+
+#### <img src="https://avatars.githubusercontent.com/u/26038793?v=4" width="50">[oelkie](https://github.com/oelkie) opened issue at [2024-07-10 10:34](https://github.com/rear/rear/issues/3271):
+
+rear -V  
+2.6 / Git via 'apt install rear'
+
+Debian 11, fresh install
+
+/etc/rear/local.conf
+
+    BACKUP=NETFS
+    OUTPUT=USB
+    USB_DEVICE=/dev/disk/by-label/REAR-000
+    BACKUP_URL=usb:///dev/disk/by-label/REAR-000
+
+/etc/rear/site.conf
+
+    TIMESYNC=NTP
+
+    System, inxi -F information:
+    System:    Host: debian11rear Kernel: 5.10.0-30-amd64 x86_64 bits: 64 Console: tty 0 Distro: Debian GNU/Linux 11 (bullseye)
+    Machine:   Type: Laptop System: Hewlett-Packard product: HP ZBook 14 v: A3009DD10303 serial: 5CG5062MHR
+               Mobo: Hewlett-Packard model: 198F v: KBC Version 15.59 serial: PDYAC00WB8B09N BIOS: Hewlett-Packard
+               v: L71 Ver. 01.49 date: 02/24/2020
+    Battery:   ID-1: BAT0 charge: 0% condition: 42.5/42.5 Wh (100%)
+    CPU:       Info: Dual Core model: Intel Core i7-4600U bits: 64 type: MT MCP L2 cache: 4 MiB
+               Speed: 2095 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 2095 2: 2096 3: 2095 4: 2101
+    Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
+               Device-2: Advanced Micro Devices [AMD/ATI] Mars [Radeon HD 8730M] driver: N/A
+               Device-3: Cheng Uei Precision Industry (Foxlink) HP HD Webcam type: USB driver: uvcvideo
+               Display: server: No display server data found. Headless machine? tty: 180x42
+               Message: Advanced graphics data unavailable in console for root.
+    Audio:     Device-1: Intel Haswell-ULT HD Audio driver: snd_hda_intel
+               Device-2: Intel 8 Series HD Audio driver: snd_hda_intel
+               Device-3: AMD Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] driver: snd_hda_intel
+               Sound Server: ALSA v: k5.10.0-30-amd64
+    Network:   Device-1: Intel Ethernet I218-LM driver: e1000e
+               IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: 50:65:f3:b8:c7:b8
+               Device-2: Intel Wireless 7260 driver: N/A
+               Device-3: HP lt4112 Gobi 4G Module Network Device type: USB driver: qcserial,qmi_wwan
+               IF: wwan0 state: down mac: 32:ce:37:08:62:be
+    Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
+               Report: ID: hci0 state: up running bt-v: 2.1 address: D8:FC:93:6D:51:54
+    Drives:    Local Storage: total: 238.47 GiB used: 1.73 GiB (0.7%)
+               ID-1: /dev/sda vendor: Transcend model: TS256GMTS430S size: 238.47 GiB
+    Partition: ID-1: / size: 232.73 GiB used: 1.73 GiB (0.7%) fs: ext4 dev: /dev/sda1
+    Swap:      ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) dev: /dev/sda5
+    Sensors:   System Temperatures: cpu: 50.0 C mobo: 0.0 C
+               Fan Speeds (RPM): N/A
+    Info:      Processes: 115 Uptime: 4m Memory: 15.52 GiB used: 495.9 MiB (3.1%) Init: systemd runlevel: 5 Shell: Bash
+               inxi: 3.3.01
+
+    lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT
+    NAME        KNAME     PKNAME   TRAN   TYPE FSTYPE LABEL   SIZE MOUNTPOINT
+    /dev/sda    /dev/sda           sata   disk              238,5G
+    |-/dev/sda1 /dev/sda1 /dev/sda        part ext4         237,5G /
+    |-/dev/sda2 /dev/sda2 /dev/sda        part                  1K
+    `-/dev/sda5 /dev/sda5 /dev/sda        part swap           976M [SWAP]
+
+`rear -d -v mkbackup` gave message:
+
+    2024-07-10 12:16:40.030195929 WARNING: tar ended with return code 1 and below output:
+      ---snip---
+      tar: Removing leading `/' from member names
+      tar: Removing leading `/' from hard link targets
+      tar: /sys: 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.
+
+Booting from this device gave an 'Boot error'
+
+Best regards
+
+#### <img src="https://avatars.githubusercontent.com/u/888633?u=cdaeb31efcc0048d3619651aa18dd4b76e636b21&v=4" width="50">[gdha](https://github.com/gdha) commented at [2024-07-11 09:00](https://github.com/rear/rear/issues/3271#issuecomment-2222399197):
+
+@oelkie See example page
+[https://relax-and-recover.org/usage/\#recovery\_from\_usb](https://relax-and-recover.org/usage/#recovery_from_usb)
+
+#### <img src="https://avatars.githubusercontent.com/u/26038793?v=4" width="50">[oelkie](https://github.com/oelkie) commented at [2024-07-19 12:25](https://github.com/rear/rear/issues/3271#issuecomment-2239028657):
+
+This issue can be closed, i got working config:
+
+### backup to USB-Drive
+
+OUTPUT=USB  
+USB\_DEVICE=/dev/disk/by-label/REAR-000  
+BACKUP=NETFS  
+BACKUP\_URL=usb:///dev/disk/by-label/REAR-000  
+BACKUP\_PROG\_EXCLUDE=( ${BACKUP\_PROG\_EXCLUDE\[@\]} '/tmp' '/var/tmp'
+)  
+USING\_UEFI\_BOOTLOADER=1  
+USB\_PREFIX="${HOSTNAME}-$(date '+%Y-%m-%d-%H%M%S')"  
+USE\_DHCLIENT=n
+
+#### <img src="https://avatars.githubusercontent.com/u/888633?u=cdaeb31efcc0048d3619651aa18dd4b76e636b21&v=4" width="50">[gdha](https://github.com/gdha) commented at [2024-07-19 12:28](https://github.com/rear/rear/issues/3271#issuecomment-2239032565):
+
+@oelkie Thank you very much for the good feedback - you will help other
+users with it.
+
+------------------------------------------------------------------------
+
+\[Export of Github issue for
+[rear/rear](https://github.com/rear/rear).\]

docs/issues/2024-07-12.3276.issue.closed.md

@@ -0,0 +1,56 @@
+[\#3276 Issue](https://github.com/rear/rear/issues/3276) `closed`: Secure Boot with GRUB shim should work automatically
+=======================================================================================================================
+
+#### <img src="https://avatars.githubusercontent.com/u/101384?v=4" width="50">[schlomo](https://github.com/schlomo) opened issue at [2024-07-12 09:03](https://github.com/rear/rear/issues/3276):
+
+Currently one must set
+`SECURE_BOOT_BOOTLOADER=(/boot/efi/EFI/*/shimx64.efi)` or something like
+this on every system that uses [secure
+boot](https://wiki.debian.org/SecureBoot).
+
+I'd like to enhance ReaR to automatically detect secure boot and
+configure the shim.
+
+#### <img src="https://avatars.githubusercontent.com/u/101384?v=4" width="50">[schlomo](https://github.com/schlomo) commented at [2024-07-12 10:29](https://github.com/rear/rear/issues/3276#issuecomment-2225288733):
+
+I just notice that we already have code to read the EFI variables, added
+by @jsmeix in
+[https://github.com/rear/rear/commit/9a31a5fa9a75a72bfb01eedabadc104400982667](https://github.com/rear/rear/commit/9a31a5fa9a75a72bfb01eedabadc104400982667)
+
+Do you happen to remember why reading the EFI vars comes as a fallback
+solution instead of trying to do that first?
+
+#### <img src="https://avatars.githubusercontent.com/u/101384?v=4" width="50">[schlomo](https://github.com/schlomo) commented at [2024-07-12 10:46](https://github.com/rear/rear/issues/3276#issuecomment-2225313366):
+
+ReaR output for `rear -v mkrescue`:
+
+    Relax-and-Recover 2.7 / Git
+    Running rear mkrescue (PID 44344 date 2024-07-12 12:45:41)
+    Using log file: /tmp/rear_var/log/rear/rear-rear-ol9u3.log
+    Running workflow mkrescue on the normal/original system
+    Using UEFI Boot Loader for Linux (USING_UEFI_BOOTLOADER=1)
+    Secure Boot auto-configuration using '/boot/efi/EFI/redhat/shimx64.efi' as UEFI bootloader
+    Using autodetected kernel '/boot/vmlinuz-5.15.0-204.147.6.3.el9uek.x86_64' as kernel in the recovery system
+    Creating disk layout
+    ...
+
+Rescue system now also has `mokutil` to validate secure boot status:  
+![image](https://github.com/user-attachments/assets/4a53db48-0de9-466f-9ab5-b5ccabe3c9d2)
+
+#### <img src="https://avatars.githubusercontent.com/u/26300485?u=9105d243bc9f7ade463a3e52e8dd13fa67837158&v=4" width="50">[pcahyna](https://github.com/pcahyna) commented at [2024-07-12 11:21](https://github.com/rear/rear/issues/3276#issuecomment-2225362800):
+
+Hi @schlomo , I did some work to support this but never got around to
+complete it, so I am at least pushing it for public review as \#3277 .
+IIRC, the code works on RHEL main thing missing was to check
+compatibility with all the possible conventions for naming the
+bootloader and shim for various distro versions.
+
+#### <img src="https://avatars.githubusercontent.com/u/101384?v=4" width="50">[schlomo](https://github.com/schlomo) commented at [2024-07-12 11:26](https://github.com/rear/rear/issues/3276#issuecomment-2225370688):
+
+Ah, great. I'll have a look. My approach is rather primitive in
+comparison
+
+------------------------------------------------------------------------
+
+\[Export of Github issue for
+[rear/rear](https://github.com/rear/rear).\]