850_make_USB_bootable.sh line 12: RAW_USB_DEVICE and REAL_USB_DEVICE are not both set¶

Labels: support / question

macMikey opened issue at 2024-09-24 16:39:¶

ReaR version ("/usr/sbin/rear -V"): Relax-and-Recover 2.7 / Git
If your ReaR version is not the current version, explain why you can't upgrade:
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):

NAME="Red Hat Enterprise Linux Server"
VERSION="7.9 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.9"
PRETTY_NAME="Red Hat Enterprise Linux"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.9:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.9
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.9"

ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=USB
BACKUP=NETFS
BACKUP_URL="usb:///dev/disk/by-label/REAR-000"

Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):
SMBIOS 3.0.0 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: HPE
Product Name: ProLiant MicroServer Gen10
Version: Rev B
Serial Number: 7CE732P0J5
UUID: ba8f516f-b1a5-2d41-91db-98f2b3e87446
Wake-up Type: Power Switch
SKU Number: 870208-001
Family: ProLiant

Handle 0x001A, DMI type 12, 5 bytes
System Configuration Options
Option 1: Default string

Handle 0x0021, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected

System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
GRUB
SMBIOS 3.0.0 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 5.12
Release Date: 06/05/2017
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 8192 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.12

Handle 0x0055, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1

Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local SSD
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
Description of the issue (ideally so that others can reproduce it):
see title
Workaround, if any:
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

rear-toaster.log

gdha commented at 2024-10-04 09:24:¶

@macMikey Did you format the USB before running rear mkbackup?
I found an error in your log file:

2024-09-24 12:15:06.575315355 Including prep/USB/default/480_initialize_write_protect_settings.sh
2024-09-24 12:15:06.584650170 Cannot write protect USB disk of '/dev/disk/by-label/REAR-000' via ID (no ID found)

macMikey commented at 2024-10-04 14:15:¶

i have tried partitioning+formatting it several different ways, used rear to format it as per the quickstart, etc.
i'm also not a worthy sysadmin, so suggestions (like - repartitioning a certain way then formatting a certain way) are welcome.
the goal is to make a bootable system recovery disk that i can build daily or weekly, and save myself if the main drive on the machine dies.

macMikey commented at 2024-10-07 18:45:¶

i just did a rear format, again. then i did a verbose run of rear
full verbose log attached
rear-toaster-2.txt

macMikey commented at 2024-10-07 19:38:¶

running rear -D mkrescue log attached

rear-toaster.txt

macMikey commented at 2024-10-24 13:10:¶

any suggestions on how to proceed?

gdha commented at 2024-10-24 13:19:¶

@macMikey I noticed in your log-file that you renamed script /usr/share/rear/prep/USB/default/350_check_usb_disk.sh to /usr/share/rear/prep/USB/default/350_check_usb_disk.sh.bak. Was there a reason for?

In script /usr/share/rear/output/USB/Linux-i386/850_make_USB_bootable.sh you see a comment like:

# We assume REAL_USB_DEVICE and RAW_USB_DEVICE are both set by prep/USB/Linux-i386/350_check_usb_disk.sh
[ "$RAW_USB_DEVICE" -a "$REAL_USB_DEVICE" ] || BugError "RAW_USB_DEVICE and REAL_USB_DEVICE are not both set"

macMikey commented at 2024-10-25 21:13:¶

thanks for jumping in.
i did not rename anything...at least not intentionally. AFAIK all i changed was the configuration file.
how did you even find that? is there a script that can be run that would identify issues like that?
looking at that directory, it appears that that file is owned by root (all the others are owned by me - i installed rear), and was created a few minutes after the other files in the directory. so, either i managed to rename it (???), or something else happened...
so, just now, i copied the bak file to sh, and tried again:

sudo cp /usr/share/rear/prep/USB/default/350_check_usb_disk.sh.bak /usr/share/rear/prep/USB/default/350_check_usb_disk.sh
sudo rear -vD mkrecover

the output looked promising. it looks like it might have achieved.
i'll reply with all of it, including the log file, on monday...

macMikey commented at 2024-10-28 17:54:¶

i'm not going to waste space with the log. i have tried this multiple times.
thanks for the help. i think that fixed it.

[Export of Github issue for rear/rear.]

#3322 Issue closed: BUG in /usr/share/rear/output/USB/Linux-i386/850_make_USB_bootable.sh line 12: RAW_USB_DEVICE and REAL_USB_DEVICE are not both set¶