#1888 Issue closed: rear recover failing with ERROR: No filesystem mounted on '/mnt/local'. Stopping

Labels: support / question, fixed / solved / done

langerkunal opened issue at 2018-08-02 10:10:

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"): 2.4

  • OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): SLES 12 SP3

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
    OUTPUT=ISO
    BACKUP=NETFS
    BACKUP_URL=file:///tmp/rearbackup/

  • 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 excat ARM device): PPC64LE

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): UEFI

  • Description of the issue (ideally so that others can reproduce it): When I am trying to recover the backup image on a new hardware it is failing every time with error "No Filesystem mounted on /mnt/local" even though I have uncompressed the content of backup.tar.gz under /mnt/local

RESCUE DNW75APP2:~ rear recover
Relax-and-Recover 2.4 / 2018-06-21
Using log file: /var/log/rear/rear-DNW75APP2.log
Running workflow recover within the ReaR rescue/recovery system
Using backup archive '/tmp/rearbackup/DNW75APP2/backup.tar.gz'
Will do driver migration (recreating initramfs/initrd)
Calculating backup archive size
Backup archive size is 62M /tmp/rearbackup/DNW75APP2/backup.tar.gz (compressed)
Comparing disks
Disk configuration looks identical
Proceed with recovery (yes) otherwise manual disk layout configuration is enforced
(default 'yes' timeout 30 seconds)
yes
User confirmed to proceed with recovery
Start system layout restoration.
Disk layout created.
ERROR: No filesystem mounted on '/mnt/local'. Stopping.
Aborting due to an error, check /var/log/rear/rear-DNW75APP2.log for details
Exiting rear recover (PID 4595) and its descendant processes
Running exit tasks
Terminated
RESCUE DNW75APP2:~

  • Work-around, if any: No

jsmeix commented at 2018-08-02 11:01:

@langerkunal
you wrote "I am trying to recover the backup image on a new hardware".

Is your "new hardware" fully compatible with the hardware
of your original system where "rear mkbackup" was run?
Cf. the section "Fully compatible replacement hardware is needed" in
https://en.opensuse.org/SDB:Disaster_Recovery

Provided your "new hardware" is fully compatible with the hardware
of your original system where "rear mkbackup" was run
I need at least the debug log file for "rear -D recover"
to have a chance to understand what goes on
on your particular system.
Ideally I would need what is described in the section
"Debugging issues with Relax-and-Recover" in
https://en.opensuse.org/SDB:Disaster_Recovery

jsmeix commented at 2018-08-02 11:06:

@langerkunal
I noticed right now that you use

BACKUP_URL=file:///tmp/rearbackup/

which looks as if your backup is on a local disk on the original system
so that it cannot work to restore that on any other system
or do I misunderstand something here?

langerkunal commented at 2018-08-02 11:11:

@jsmeix For some reason NFS mount wasn't working in my environment so I took the backup on local system and then copied the backup files to a different system, from there I booted using DVD/CD (ISO) to start recovery
Attached recover.log file for reference.
recover.log

gdha commented at 2018-08-29 11:00:

@langerkunal Can you share the content of /var/lib/rear/layout/disklayout.conf please?

langerkunal commented at 2018-09-03 05:55:

Content of asked file:

[root@testlpar-rhel layout]# cat disklayout.conf
#lvmdev /dev/rhel /dev/mapper/mpatha3 RVfsTJ-2VGk-guvh-QewP-UfJy-Lr0L-CHLdiO 199550976
#lvmgrp /dev/rhel 4096 24359 99774464
#lvmvol /dev/rhel swap 1024 8388608
#lvmvol /dev/rhel home 10534 86294528
#lvmvol /dev/rhel root 12800 104857600
# Filesystems (only ext2,ext3,ext4,vfat,xfs,reiserfs,btrfs are supported).
# Format: fs <device> <mountpoint> <fstype> [uuid=<uuid>] [label=<label>] [<attributes>]
#fs /dev/mapper/mpatha2 /boot xfs uuid=72162934-6d2c-4197-94fd-eeb5899d190c label=  options=rw,relatime,attr2,inode64,noquota
#fs /dev/mapper/rhel-home /home xfs uuid=4213a384-dfcd-454b-9497-25887ac87a69 label=  options=rw,relatime,attr2,inode64,noquota
#fs /dev/mapper/rhel-root / xfs uuid=94c980d4-ac56-49b5-a94b-754f081cea3d label=  options=rw,relatime,attr2,inode64,noquota
# Swap partitions or swap files
# Format: swap <filename> uuid=<uuid> label=<label>
#swap /dev/mapper/rhel-swap uuid=f1218fca-dba0-49f2-907a-13d345f15dbf label=
#multipath /dev/mapper/mpatha /dev/sda,/dev/sdb
#part /dev/mapper/mpatha 4194304 1048576 primary boot,prep /dev/mapper/mpatha1
#part /dev/mapper/mpatha 1073741824 5242880 primary none /dev/mapper/mpatha2
#part /dev/mapper/mpatha 102170099712 1078984704 primary lvm /dev/mapper/mpatha3
[root@testlpar-rhel layout]#

gdha commented at 2018-09-03 15:05:

@langerkunal because all your storage devices are multipath devices you should add AUTOEXCLUDE_MULTIPATH=n to the /etc/rear/local.conf file as currently they are excluded by default

jsmeix commented at 2018-09-28 07:24:

No news is good news.

[Export of Github issue for rear/rear.]