#3012 Issue closed: Problems with the initial rear recover menu

Labels: no-issue-activity

danboid opened issue at 2023-06-09 11:04:

  • ReaR version ("/usr/sbin/rear -V"):

2.7

  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):

Ubuntu 20.04.6

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
### write the rescue initramfs to USB and update the USB bootloader
OUTPUT=USB

### create a backup using the internal NETFS method, using 'tar'
BACKUP=NETFS

### write both rescue image and backup to the device labeled REAR-000
BACKUP_URL=usb:///dev/disk/by-label/REAR-000
USE_RESOLV_CONF="no"
  • Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):

Any x86

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):

amd64

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):

UEFI

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):

local SATA

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):

mdraid 10

  • Description of the issue (ideally so that others can reproduce it):

There are two problems with the initial rear recover menu that I've become aware of in my testing of rear's support for md RAID.

It would seem to me that rear doesn't support (auto)resizing of md RAID arrays? In that case rear recover shouldn't offer the user the "Confirm disk mapping and continue rear recover" option (which I think should be renamed to "Confirm disk mapping and configure recovery options." as discussed in my previous ticket) in the first rear recover menu if the rear image uses RAID because it will fail with the error Cannot autoresize RAID /dev/md0 (autoresizing is not supported for RAID level 'raid 10'). I have attached a log of it failing to get beyond the first rear recover menu because of this.

The other problem is that when rear recover is run in debug mode (rear -D recover) the "Confirm identical disk mapping and proceed without manual configuration" that does usually work (in non debug mode) is supposedly unavailable, option 2 being labelled "n/a". If I quit rear after running it in debug mode and run it without the debug option, option #2 remains n/a. The option reappears after a reboot, if run without debug mode.

rear-testtree.log

github-actions commented at 2023-08-09 02:13:

Stale issue message

[Export of Github issue for rear/rear.]