You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PowerVM LPAR
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
PPC64LE
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Open Firmware
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN-FC and multipath-DM
Description of the issue (ideally so that others can reproduce it):
After a rear recover the swap partition was recreated with type 0x83 while at installation the type was 0x82.
Workaround, if any:
I modified script 140_include_swap_code.sh , see below. I tested the modification in my test environment and it seems to work. Do you think it is reliable enough to be deployed in a production environment?
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
```
create_swap() {
local swap device uuid label junk pdev nrpart
read swap device uuid label junk < <(grep "^swap ${1#swap:} " "$LAYOUT_FILE")
if [[ "$FEATURE_MKSWAP_UUID" && -n "${uuid#uuid=}" ]] ; then
uuid="-U ${uuid#uuid=} "
else
uuid=""
fi
if [[ -n "${label#label=}" ]] ; then
label="-L ${label#label=} "
else
label=""
fi
nrpart="${device: -1}"
pdev=$(awk '$1==PART { print $NF}' PART=$device $LAYOUT_DEPS)
(
echo "LogPrint \"Change swap partition type on $device\""
echo "parted -s $pdev set $nrpart type 0x82"
echo "LogPrint \"Creating swap on $device\""
echo "mkswap ${uuid}${label}${device} >&2"
) >> "$LAYOUT_CODE"
}
```
The text was updated successfully, but these errors were encountered:
@musyl
thank you for the issue report and your fix!
I will have a look - as time permits - hopefully next week.
In general:
The ReaR scripts are meant to be adapted
and enhanced as needed by the user, cf.
"Disaster recovery with Relax-and-Recover (ReaR)" in https://en.opensuse.org/SDB:Disaster_Recovery
looks "suspicious" because I at a glance cannot find in "man parted" or in https://www.gnu.org/software/parted/manual/parted.html
that the parted command set supports type
but I may misunderstand the parted documentation.
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.5
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
SUSE Linux Enterprise Server 12 SP4
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PowerVM LPAR
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
PPC64LE
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Open Firmware
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
SAN-FC and multipath-DM
Description of the issue (ideally so that others can reproduce it):
After a rear recover the swap partition was recreated with type 0x83 while at installation the type was 0x82.
Workaround, if any:
I modified script 140_include_swap_code.sh , see below. I tested the modification in my test environment and it seems to work. Do you think it is reliable enough to be deployed in a production environment?
Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
To paste verbatim text like command output or file content,
include it between a leading and a closing line of three backticks like
The text was updated successfully, but these errors were encountered: