-
Notifications
You must be signed in to change notification settings - Fork 246
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
ERROR: No filesystem mounted on '/mnt/local'. Stopping. #1953
Comments
It struck me that the partition table is of msdos type instead of gpt. |
I already opened Red Hat case in parallel, but you guys are most of the time way more effective in finding root cause. :) RESCUE sop00dbhh04t:~ # parted /dev/sdd print Model: IBM 2145 (scsi) Disk /dev/sdd: 1100GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 1075MB 1074MB primary ext3 boot 2 1075MB 1100GB 1098GB primary lvm Does it mean I should focus on workaround scenario with AUTOEXCLUDE_MULTIPATH=y? Thanks, |
@pdanek Start with adding the following 2 lines in
However, what worries me is the partition table label msdos. How can a multipath disk:
of size 4TB be using a msdos partition table instead of gpt. That does not make sense at all. |
-- |
@gdha In #1953 (comment) How did you find out in the attached logs form @pdanek |
With latest ReaR 2.4 version and AUTOEXCLUDE_MULTIPATH=n + BOOT_OVER_SAN=y we get following after rear recover:
Also:
Do you have an idea what could be wrong please? |
@pdanek Was the restore (#1953 (comment)) successful that way? What is the content of |
I didn't try the option 1 yet as I was assumed "rear recover" should automatically know which disk is correct. disklayout.conf attached - disklayout.conf.txt Thanks. |
@pdanek what you can try to do is the following:
|
@pdanek For the reason behind see the MIGRATION_MODE documentation If you know what you do you can specify |
@pdanek |
@pdanek could you try out the snapshot version from http://download.opensuse.org/repositories/Archiving:/Backup:/Rear:/Snapshot/RHEL_7/x86_64/ ? The issue with missing NBU libraries should be fixed in there. |
@pdanek are your questions sufficient answered? |
Thanks everyone for the help here. In regards to the above issue with MIGRATION_MODE, already being resolved in #2050. |
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.00 / Git (rpm package rear-2.00-7.el7_5.x86_64)
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
Red Hat Enterprise Linux Server release 7.4, kernel 3.10.0-693.5.2.el7.x86_64
ReaR configuration file cat /etc/rear/local.conf:
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
Cisco UCS
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):
x86
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
BIOS
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
FC
Description of the issue (ideally so that others can reproduce it):
Log file attached.
rear-sop00dbhh04t_AUTOEXCLUDE_MULTIPATH=y.log
Using AUTOEXCLUDE_MULTIPATH=n, we get different error - log file attached.
rear-sop00dbhh04t_AUTOEXCLUDE_MULTIPATH=n.log
rear-sop00dbhh04t_AUTOEXCLUDE_MULTIPATH=y_DEBUG.log
The text was updated successfully, but these errors were encountered: