ERROR: No filesystem mounted on '/mnt/local'. Stopping

[andreasberner]

I am trying to use rear to create a virtual copy from a physical system.
The virtual system is indeed different from the physical system and this is likely the reason for the above error message but I am trying to overcome this anyhow.

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-git201704252000 / 2017-04-25
• OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):
  Debian 8.11
• ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=ISO
OUTPUT_URL=file:///tmp/backup
BACKUP=NETFS
# BACKUP=EXTERNAL
BACKUP_URL=iso:///backup/
# Wegen Restore Problem auf Virtueller Maschine bei Netcup
AUTOEXCLUDE_MULTIPATH=n
BOOT_OVER_SAN=y

• Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR):
  Source: Physical maschine with 16GB RAM, 2*1 TB Harddisk with hardware Raid controller, RAID 1, LVM configuration of Harddisk
  Target: Virtual Mashine KVM with 480 GB SAS and 16GB, Intel XEON

• 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):
  Bootloader GRUB 2

• Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
  Source local Harddisk 2*1TB with Hardware Raid controller, RAID 1

• Description of the issue (ideally so that others can reproduce it):
  When trying to install the ISO on the target the system would stop
  with above message.

• Workaround, if any:

• Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):
  (I have problems to copy the logfile to here)

[gozora]

@andreasberner, I don't have exact answer for your problem, but I'd recommend you to start with storing your ReaR recovery system (ISO) and backup separately on some remote (CIFS or NFS) share.

Something like:

OUTPUT=ISO
BACKUP=NETFS
BACKUP_OPTIONS="nfsvers=3,nolock"
BACKUP_URL=nfs://your.NFS.server.IP/path/to/your/rear/backup

here you can find some easy and tested configuration examples.

Be aware file:// as a destination can be quite tricky and might require some hacks to work correctly ...

V.

[gozora]

@hamantri I'm somehow confused by your posts. As @andreasberner already wrote, they looks to be unrelated to this issue.
If you want, you can open new issue by filling the template here.

V.

[andreasberner]

@gozora: Thank you for your advice the source server is in a remote location and I would do hard to store the backup somewhere else if not on file. I have already used rear on a different hardware where I store everything on a mounted USB-Stick and this works like a charm.
Can you explain a bit more into detail why storing the resulting backup in a file would be problematic?
Of course I moved away to the iso to the cd of the desingated copy computer right after creating the iso on the source.

[gozora]

@andreasberner

Can you explain a bit more into detail why storing the resulting backup in a file would be problematic?

Well, I'm afraid I can't give you qualified answer, because I've never actually used file://. and honestly I have just foggy idea how it works ...
Anyhow, as far as I remember there has been some people already having trouble when they used file://, so you can search in closed issues and maybe you will find something usefull ...

V.

[jsmeix]

@andreasberner
in general when you like to recreate on different hardware
(where "hardware" could be also virtual hardware)
things can get soon rather complicated, see my
explanations in the mail thread with subject
"Move from bare-metal2vm ?"
http://lists.relax-and-recover.org/pipermail/rear-users/2018-November/003626.html
on the "rear-users" mailing list at
http://relax-and-recover.org/development/

[gdha]

@andreasberner Did you looked at the target system in detail when this issue happened? Were the file systems created? Could you inspect this with fdisk or parted? vgs, lvs and pvs commands?
The error seems to be related that the desired file system was not created somehow. The logs should tell you more what really happened as these are quite detailed for that section (in creating the disk partitions and so on).

[gdha]

@andreasberner Is this issue still relevant? I see Debian, Sles and lpar ?? Very confusing...

[jsmeix]

@gdha
I think the confusing SLES and lpar you see are in comment
#2227 (comment)
but This comment was marked as off-topic. by me.

[jsmeix]

Because "no news is good news" I close it.