New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
diskrestore.sh fails on already used disk (works on empty disk) #2638
Comments
@cvijayvinoth
This behaviour is no bug in current ReaR. This kind of possible behaviour is well known at ReaR upstream. This possible behaviour is explained in the section Same kind of possible behaviour can also happen In current ReaR upstream master code I implemented some initial It is not at all yet "ready for general production use" By the way FYI: When "rear recover" failed during disk layout recreation What usually works much better when "rear recover" failed In contrast when "rear recover" failed after it had |
I think the issue is sufficiently answered. |
ReaR version ("/usr/sbin/rear -V"):
Relax-and-Recover 2.6 / Git
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
PC
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86 compatible
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
UEFI and GRUB
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
local
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,SIZE,MOUNTPOINT" or "lsblk" as makeshift):
during the recovery process restore
The disk layout recreation script failed
Attached disklayout file too. Same iso image is working fine in virtualbox.
Only on physical machine I am facing this issue.
In physical machine for
create_component "/dev/md0" "raid"
condition the touch file created like
rear-vgchange
when i manually ran the command
I got the below error.
It looks it will work fine for empty disks and
if the os already exist it throws an error.
rear-vijay.log
disklayout.txt
The text was updated successfully, but these errors were encountered: