-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.7
-
None
-
No
-
Moderate
-
Upstream
-
rhel-base-utils-core
-
0
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Create a backup of a system with one extra temporary mounted disk (e.g. /dev/sda with the scsi_debug kernel module) and store it on /dev/vdb. /dev/sda will be missing in the rescue and ReaR will attempt to replace it with /dev/vdb containing the backup. Therefore, the user may lose their backup if they proceed with this suggestion. ReaR should automatically skip all devices with backups when looking for candidates for recreation of missing devices:
... Comparing disks Ambiguous disk layout needs manual configuration (more than one disk with same size used in '/var/lib/rear/layout/disklayout.conf') Switching to manual disk layout configuration Using /dev/vda (same name and same size 10737418240) for recreating /dev/vda Using /dev/vdc (same name and same size 10737418240) for recreating /dev/vdc Using /dev/vdd (same name and same size 10737418240) for recreating /dev/vdd Using /dev/vde (same name and same size 10737418240) for recreating /dev/vde Using /dev/vdf (same name and same size 10737418240) for recreating /dev/vdf Original disk /dev/sda does not exist (with same size) in the target system The size of /dev/vdb is Using /dev/vdb (the only available of the disks) for recreating /dev/sda with size 16777216 <-- ISSUE! Current disk mapping table (source => target): /dev/vda => /dev/vda /dev/vdc => /dev/vdc /dev/vdd => /dev/vdd /dev/vde => /dev/vde /dev/vdf => /dev/vdf /dev/sda => /dev/vdb UserInput -I LAYOUT_MIGRATION_CONFIRM_MAPPINGS needed in /usr/share/rear/layout/prepare/default/300_map_disks.sh line 291
See https://issues.redhat.com/browse/RHEL-83241?focusedId=27874443&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-27874443 for additional details.