PBS2: proxmox-file-restore failed: Error: mounting 'drive-virtio0.img.fidx/part/["5"]' failed: all mounts failed or no supported file system (500)

[ahoi_]

Hello,

I updated PBS to PBS2 - the update went fine and I was able to create a new backup of a machine that has these mount points:

$ df -h

Dateisystem           Größe Benutzt Verf. Verw% Eingehängt auf
udev                   982M       0  982M    0% /dev
tmpfs                  200M     22M  178M   11% /run
/dev/mapper/vg00-root   30G    2,7G   26G   10% /
tmpfs                  998M       0  998M    0% /dev/shm
tmpfs                  5,0M       0  5,0M    0% /run/lock
tmpfs                  998M       0  998M    0% /sys/fs/cgroup
/dev/vda1              472M     85M  364M   19% /boot



$ cat /proc/mounts

sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=1005468k,nr_inodes=251367,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=204292k,mode=755 0 0
/dev/mapper/vg00-root / ext4 rw,relatime,errors=remount-ro 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup2 /sys/fs/cgroup/unified cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/rdma cgroup rw,nosuid,nodev,noexec,relatime,rdma 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=37,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11315 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
/dev/vda1 /boot ext2 rw,relatime 0 0



$ pvs
  PV         VG   Fmt  Attr PSize   PFree
  /dev/vda5  vg00 lvm2 a--  <31,52g    0



$ lvs
  LV     VG   Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root   vg00 -wi-ao----  30,56g                                                   
  swap_1 vg00 -wi-ao---- 980,00m

Restoring single files from part 2 and 5 still fails

proxmox-file-restore failed: Error: mounting 'drive-virtio0.img.fidx/part/["5"]' failed: all mounts failed or no supported file system (500)

 

[dcsapak]

seems the partition 2 is an extended partition (and in it partition 5)? if yes it does not contain a filesystem/lvm/zfs and thus it cannot be mounted

 

[ahoi_]

Hi @dcsapak

But in this case partition 5 should be mountable?

fdisk -l
Festplatte /dev/vda: 32 GiB, 34359738368 Bytes, 67108864 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes
Festplattenbezeichnungstyp: dos
Festplattenbezeichner: 0x44350605

Gerät      Boot  Anfang     Ende Sektoren Größe Kn Typ
/dev/vda1  *       2048   999423   997376  487M 83 Linux
/dev/vda2       1001470 67106815 66105346 31,5G  5 Erweiterte
/dev/vda5       1001472 67106815 66105344 31,5G 8e Linux LVM


Festplatte /dev/mapper/vg00-root: 30,6 GiB, 32816234496 Bytes, 64094208 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes


Festplatte /dev/mapper/vg00-swap_1: 980 MiB, 1027604480 Bytes, 2007040 Sektoren
Einheiten: Sektoren von 1 * 512 = 512 Bytes
Sektorgröße (logisch/physikalisch): 512 Bytes / 512 Bytes
E/A-Größe (minimal/optimal): 512 Bytes / 512 Bytes

 

[dcsapak]

But in this case partition 5 should be mountable?

yes, what is the output of 'pveversion -v' ?
lvm support only came in recently

 

[ahoi_]

pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.124-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-4
pve-kernel-helper: 6.4-4
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.119-1-pve: 5.4.119-1
ceph-fuse: 14.2.20-pve1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

So this feature depends on PVE7?

 

[dcsapak]

yes for now it is only available in pve7, i do not know if we will backport it to pve 6.4

 

[Papyruse]

yes for now it is only available in pve7, i do not know if we will backport it to pve 6.4

Hope and pray it will....
In our case, we can't upgrade our production cluster to pve7 for now and this feature was really expected for us (90% of vm on our cluster have LVM as backend) and that's a terrible news to know that...

Anyway, thank you Proxmox team, you make a really great work !

 

[BORNXenon]

I have 2 Proxmox clusters, both on v7.0-10 and each with a PBS running v2.0.7-1.
On each cluster I have a Debian based file server, configuration of these are identical with the exception that one is encrypted LVM, the other is unencrypted LVM.

On the unencrypted one, file-restore works as expected, on the encrypted one, I get the exact same error as the OP.

 

[fabian]

cryptsetup is not supported at all at the moment.

 

[BORNXenon]

I figured!
Does 'at the moment' mean that it will be t some point?

 

[fabian]

no concrete plans or promises - it would of course be possible to implement, but it would require additional flow of information (passphrase/key material from user to restore VM), there are several variants to support, etc.pp.. it's likely more realistic that there is some sort of "drop into shell to manually setup block device access inside restore VM" mechanism at some point that would handle ALL such complex scenarios, but there are no concrete plans for such a feature either at the moment

 

[BORNXenon]

No problem!
Looks like I'm going to be implementing a new file server next week then, this time without encrypted LVM!
That will then allow me to ditch the VM's I have solely running Bareos file backup.