-
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
SLES11.2 recover ERROR: No filesystem mounted on /mnt/local. Stopping. #166
Comments
The reason ReaR fails is because you have multipath on top of your /dev/vda disk. Your rootvg is on top of that multipath. AUTOEXCLUDE_MULTIPATH is 'y' by default, hence no filesystems saved or devices on top of it recreated. Solutions:
|
Thanks for your answer. I was under the impression that we had multipath generally disabled on our KVMs. So i did some investigating and found out that it's disabled on the SLES11.1 VMs and enabled on the SLES11.2s. Whats strange is that boot.multipath and multipathd init scripts are disabled but the dm_multipath module is loaded. I tried regenerating the initrd and tricking it into thinking that the VM isn't multipathed but to no avail. Any ideas how i could disable multipathing? The disks are virtio pci device
|
Maybe adding |
i tried adding i think the multipath.conf is not being used since the multipath daemon isn't running. Maybe i should open a SR with SuSE |
ok i got it to work by extracting the current initrd and removing everything multipath related. rebooted with the new initrd. now dm_multipath and dm_round_robin were gone and mkinitrd created a initrd without multipath feature. the VM is restoring fine right now :) thanks |
Hi
I'm having trouble restoring a SLES11.2 installation with rear 1.14 / Git.
It's a KVM node with two disks vda and vdb and im trying to restore it on
another kvm node with only on disk vda. Thats why i'm excluding smtvg01.
The error message is: ERROR: No filesystem mounted on /mnt/local.
Stopping.
Custom configuration in /etc/rear:
local.conf:
os.conf:
site.conf:
The node is configured with / on a ext3 partition and the rest of the
filesystem is on a VG.
Here's the "rear recover" output:
The target disk didn't get partitioned:
Here's the originial disk layout:
And the original mounts:
Any ideas?
Let me know if you need the logs of "rear mkrescue" and / or "rear -Dv
recover".
The text was updated successfully, but these errors were encountered: