File restore (NTFS) - all mount failed or no supported file system

[fabian]

sorry, haven't had a chance yet to set one up..

 

[Artem.ws]

Well, problem still not solved, even after update proxmox to latest version(((

 

[urnash]

sorry, haven't had a chance yet to set one up..

Good afternoon, please solve the problem. I have this problem on 4 servers.

 

[Artem.ws]

Good afternoon, please solve the problem. I have this problem on 4 servers.

Problem was solved on latest version. Just upgrade your nodes.

 

[dtruffo]

I've got the same problem. If i Mount manually backup images I can extract files, but using web gui always error.
Proxmox and backup are latest version available
Thank You

 

[fabian]

I've got the same problem. If i Mount manually backup images I can extract files, but using web gui always error.
Proxmox and backup are latest version available
Thank You

please provide details
- pveversion -v
- exact error
- debug log of the file-restore

 

[dtruffo]

PVEVERSION:
proxmox-ve: 8.2.0 (running kernel: 6.8.4-3-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-3
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph: 18.2.2-pve1
ceph-fuse: 18.2.2-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.2
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.3-1
proxmox-backup-file-restore: 3.2.3-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.6
pve-container: 5.1.10
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2


ERROR:



QEMU.LOG
[2024-07-09T16:28:47+02:00] PBS file restore VM log
Spectre V2 : Kernel not compiled with retpoline; no mitigation available!
[init-shim] beginning user space setup, version 1.0.0
[init-shim] booted Linux version 6.5.11-pbs-restore (build@proxmox) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP Mon Apr 22 16:46:49 CEST 2024

[init-shim] debug: agetty start failed: /sbin/agetty not found, probably not running debug mode and safe to ignore
[init-shim] reached daemon start after 0.89s
[2024-07-09T14:28:49.885Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-07-09T14:28:49.886Z INFO proxmox_restore_daemon] scanning all disks...
[2024-07-09T14:28:49.887Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] Supported FS: reiserfs, ext3, ext4, ext2, vfat, msdos, iso9660, hfsplus, hfs, sysv, v7, ntfs3, ufs, jfs, xfs, befs, f2fs, btrfs
EXT4-fs (vdb): VFS: Can't find ext4 filesystem
EXT4-fs (vdb): VFS: Can't find ext4 filesystem
EXT2-fs (vdb): error: can't find an ext2 filesystem on dev vdb.
FAT-fs (vdb): invalid media value (0xf3)
FAT-fs (vdb): invalid media value (0xf3)
VFS: could not find a valid V7 on vdb.
ntfs3: vdb: Primary boot signature is not NTFS.
ntfs3: vdb: Alternative boot signature is not NTFS.
ufs: ufs_fill_super(): bad magic number
befs: (vdb): invalid magic header
F2FS-fs (vdb): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdb): Can't find valid F2FS filesystem in 2th superblock
[2024-07-09T14:28:49.901Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb2' (2, 103809024B)
[2024-07-09T14:28:49.903Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb3' (3, 16777216B)
[2024-07-09T14:28:49.904Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb1' (1, 523239424B)
[2024-07-09T14:28:49.906Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb4' (4, 95990841344B)
EXT4-fs (vdc): VFS: Can't find ext4 filesystem
EXT4-fs (vdc): VFS: Can't find ext4 filesystem
EXT2-fs (vdc): error: can't find an ext2 filesystem on dev vdc.
FAT-fs (vdc): bogus number of reserved sectors
FAT-fs (vdc): bogus number of reserved sectors
VFS: could not find a valid V7 on vdc.
ntfs3: vdc: Primary boot signature is not NTFS.
ntfs3: vdc: Alternative boot signature is not NTFS.
ufs: this is not a 44bsd filesystem
befs: (vdc): invalid magic header
F2FS-fs (vdc): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdc): Can't find valid F2FS filesystem in 2th superblock
EXT4-fs (vda): VFS: Can't find ext4 filesystem
EXT4-fs (vda): VFS: Can't find ext4 filesystem
EXT2-fs (vda): error: can't find an ext2 filesystem on dev vda.
FAT-fs (vda): invalid media value (0xf3)
FAT-fs (vda): invalid media value (0xf3)
VFS: could not find a valid V7 on vda.
ntfs3: vda: Primary boot signature is not NTFS.
ntfs3: vda: Alternative boot signature is not NTFS.
ufs: ufs_fill_super(): bad magic number
befs: (vda): invalid magic header
F2FS-fs (vda): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda): Can't find valid F2FS filesystem in 2th superblock
[2024-07-09T14:28:49.926Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-scsi0'): found partition '/dev/vda2' (2, 9126786629632B)
[2024-07-09T14:28:49.927Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-scsi0'): found partition '/dev/vda1' (1, 16759808B)
[2024-07-09T14:28:51.296Z INFO proxmox_restore_daemon] disk scan complete.
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT2-fs (vda1): error: can't find an ext2 filesystem on dev vda1.
FAT-fs (vda1): bogus number of reserved sectors
FAT-fs (vda1): bogus number of reserved sectors
VFS: could not find a valid V7 on vda1.
ntfs3: vda1: Primary boot signature is not NTFS.
ntfs3: vda1: Alternative boot signature is not NTFS.
ufs: ufs_fill_super(): bad magic number
befs: (vda1): invalid magic header
F2FS-fs (vda1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda1): Can't find valid F2FS filesystem in 2th superblock
[2024-07-09T14:28:55.630Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8x: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/1' failed: all mounts failed or no supported file system
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
FAT-fs (vda2): bogus number of reserved sectors
FAT-fs (vda2): bogus number of reserved sectors
VFS: could not find a valid V7 on vda2.
[2024-07-09T14:29:04.606Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vda2): invalid magic header
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2024-07-09T14:29:04.618Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/2' failed: all mounts failed or no supported file system

 

[dtruffo]

If I map and mount from command line it works perfectly.

 

[Artem.ws]

proxmox-backup-client: 3.2.3-1
proxmox-backup-file-restore: 3.2.3-1

Like i said, just update your PVE node and problem will be solve.

 

[Artem.ws]

Latest packages:

proxmox-ve: 8.2.0 (running kernel: 6.8.8-2-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
pve-kernel-5.15: 7.4-9
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.8-1-pve-signed: 6.8.8-1
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5: 6.5.13-5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-5.15.131-2-pve: 5.15.131-3
pve-kernel-5.15.74-1-pve: 5.15.74-1
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.12-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1

Just compare with your version

 

[dtruffo]

How do i update ?

My node does not suggest any update of proxmox-backup-client and proxmox-backup-file-restore when I Refresh Node Packages

I'm using pve-enterprise repo for nodes.
Still no subsciption for PBS since before buying I need to be shure that it works !

 

[dtruffo]

Here is what I see listing updates on nedes.

proxmox-backup-client/stable,now 3.2.3-1 amd64 [installed]
proxmox-backup-client/stable 3.2.2-1 amd64
proxmox-backup-client/stable 3.2.1-1 amd64
proxmox-backup-client/stable 3.2.0-1 amd64
proxmox-backup-client/stable 3.1.5-1 amd64
proxmox-backup-client/stable 3.1.4-1 amd64
proxmox-backup-client/stable 3.1.3-1 amd64
proxmox-backup-client/stable 3.1.2-1 amd64
proxmox-backup-client/stable 3.0.4-1 amd64
proxmox-backup-client/stable 3.0.3-1 amd64
proxmox-backup-client/stable 3.0.2-1 amd64
proxmox-backup-client/stable 3.0.1-1 amd64
proxmox-backup-client/stable 2.99.0-1 amd64


proxmox-backup-client/stable,now 3.2.3-1 amd64 [installed]
proxmox-backup-client/stable 3.2.2-1 amd64
proxmox-backup-client/stable 3.2.1-1 amd64
proxmox-backup-client/stable 3.2.0-1 amd64
proxmox-backup-client/stable 3.1.5-1 amd64
proxmox-backup-client/stable 3.1.4-1 amd64
proxmox-backup-client/stable 3.1.3-1 amd64
proxmox-backup-client/stable 3.1.2-1 amd64
proxmox-backup-client/stable 3.0.4-1 amd64
proxmox-backup-client/stable 3.0.3-1 amd64
proxmox-backup-client/stable 3.0.2-1 amd64
proxmox-backup-client/stable 3.0.1-1 amd64
proxmox-backup-client/stable 2.99.0-1 amd64




And this if I list on PBS

root@pbs:~# apt list proxmox-backup-client -a
Listing... Done
proxmox-backup-client/stable,now 3.2.7-1 amd64 [installed]
proxmox-backup-client/stable 3.2.6-1 amd64
proxmox-backup-client/stable 3.2.5-1 amd64
proxmox-backup-client/stable 3.2.4-1 amd64
proxmox-backup-client/stable 3.2.3-1 amd64
proxmox-backup-client/stable 3.2.2-1 amd64
proxmox-backup-client/stable 3.1.5-1 amd64
proxmox-backup-client/stable 3.1.4-1 amd64
proxmox-backup-client/stable 3.1.3-1 amd64
proxmox-backup-client/stable 3.1.2-1 amd64
proxmox-backup-client/stable 3.0.4-1 amd64
proxmox-backup-client/stable 3.0.3-1 amd64
proxmox-backup-client/stable 3.0.2-1 amd64
proxmox-backup-client/stable 3.0.1-1 amd64




So on PVE there is no 3.2.7-1, but only on PBS


EDIT:
I found 3.2.7.1, but it is on test repo for PVE nodes.
I'm not sure that it is a good iodea to use that repo in production environment.

Anyway, In that way subscription is useless !!

 

[dtruffo]

UPDATE:

Upgraded all nodes by test repository to

proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1

Same error

[2024-07-10T05:33:29.292Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vda2): invalid magic header
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2024-07-10T05:33:29.304Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/2' failed: all mounts failed or no supported file system
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT2-fs (vda1): error: can't find an ext2 filesystem on dev vda1.
FAT-fs (vda1): bogus number of reserved sectors
FAT-fs (vda1): bogus number of reserved sectors
VFS: could not find a valid V7 on vda1.
ntfs3: vda1: Primary boot signature is not NTFS.
ntfs3: vda1: Alternative boot signature is not NTFS.
ufs: ufs_fill_super(): bad magic number
befs: (vda1): invalid magic header
F2FS-fs (vda1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda1): Can't find valid F2FS filesystem in 2th superblock
[2024-07-10T05:33:32.431Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8x: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/1' failed: all mounts failed or no supported file system
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
FAT-fs (vda2): bogus number of reserved sectors
FAT-fs (vda2): bogus number of reserved sectors
VFS: could not find a valid V7 on vda2.
I/O error, dev vda, sector 6324224 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
ntfs3: vda2: failed to read volume at offset 0xc0000000
ntfs3: vda2: Failed to load $Volume (-5).
[2024-07-10T05:38:46.751Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs3) - EIO: I/O error
ufs: ufs_fill_super(): bad magic number
befs: (vda2): invalid magic header
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2024-07-10T05:38:46.754Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/2' failed: all mounts failed or no supported file system
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT4-fs (vda1): VFS: Can't find ext4 filesystem
EXT2-fs (vda1): error: can't find an ext2 filesystem on dev vda1.
FAT-fs (vda1): bogus number of reserved sectors
FAT-fs (vda1): bogus number of reserved sectors
VFS: could not find a valid V7 on vda1.
ntfs3: vda1: Primary boot signature is not NTFS.
ntfs3: vda1: Alternative boot signature is not NTFS.
ufs: ufs_fill_super(): bad magic number
befs: (vda1): invalid magic header
F2FS-fs (vda1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda1): Can't find valid F2FS filesystem in 2th superblock
[2024-07-10T05:38:49.811Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTAuaW1nLmZpZHgvcGFydC8x: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi0.img.fidx/part/1' failed: all mounts failed or no supported file system
I/O error, dev vdb, sector 1259536 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
I/O error, dev vdb, sector 1259648 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
I/O error, dev vdb, sector 1259522 op 0x0READ) flags 0x1000 phys_seg 1 prio class 2
EXT4-fs (vdb4): unable to read superblock
[2024-07-10T05:38:58.203Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (ext3) - EIO: I/O error
I/O error, dev vdb, sector 1259522 op 0x0READ) flags 0x1000 phys_seg 1 prio class 2
EXT4-fs (vdb4): unable to read superblock
[2024-07-10T05:38:58.206Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (ext4) - EIO: I/O error
I/O error, dev vdb, sector 1259522 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
EXT2-fs (vdb4): error: unable to read superblock
I/O error, dev vdb, sector 1259520 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
FAT-fs (vdb4): unable to read boot sector
[2024-07-10T05:38:58.209Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (vfat) - EIO: I/O error
I/O error, dev vdb, sector 1259520 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
FAT-fs (vdb4): unable to read boot sector
[2024-07-10T05:38:58.212Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (msdos) - EIO: I/O error
I/O error, dev vdb, sector 1259584 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
I/O error, dev vdb, sector 1259522 op 0x0READ) flags 0x800 phys_seg 1 prio class 2
I/O error, dev vdb, sector 1259522 op 0x0READ) flags 0x0 phys_seg 1 prio class 2
VFS: could not find a valid V7 on vdb4.
ntfs3: vdb4: failed to read volume at offset 0x0
[2024-07-10T05:38:58.216Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (ntfs3) - EIO: I/O error
[2024-07-10T05:38:58.218Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (xfs) - EIO: I/O error
befs: (vdb4): unable to read superblock
F2FS-fs (vdb4): Unable to read 1th superblock
F2FS-fs (vdb4): Unable to read 2th superblock
[2024-07-10T05:38:58.220Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (f2fs) - EIO: I/O error
Buffer I/O error on dev vdb4, logical block 16, async page read
[2024-07-10T05:38:58.222Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb4' (btrfs) - EIO: I/O error
[2024-07-10T05:38:58.223Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTEuaW1nLmZpZHgvcGFydC80: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata1.img.fidx/part/4' failed: all mounts failed or no supported file system



On another VM (3.5TB) it works and it was workin before update of Proxmox-backup-client and proxmox-backup-file-restore.
Both VMs are windows 2019.

Both can be opened and file restore mapping and mount by command line.

 

[fabian]

and on the host you are also mounting using the ntfs3 driver (and not the ntfs one, or ntfs-3g)?

 

[dtruffo]

Used :

proxmox-backup-client map blablablabla
lsblk to sho mapped partitions

mounted with mount.ntfs /dev/loop0p2 /xxxxxxx -o ro

After that copied files and then

umount and proxmox-backup-client unmap blablabla

 

[fabian]

that's ntfs-3g, which is a totally different driver than in the file-restore VM..

 

[dtruffo]

that's ntfs-3g, which is a totally different driver than in the file-restore VM..

SO how can I manage file restore from GUI, itis not possible ?

 

[fabian]

can you try mapping and mounting using the ntfs3 driver from the kernel? if that works on the host, it might just need some tweaking of the VM settings (e.g., more memory). if not, than it's a limitation of that kernel driver, and we can only wait for improved support upstream.

 

[dtruffo]

From kernel works. Just wait...

 

[dtruffo]

This is what I do manually
proxmox-backup-client list --repository root@pam@10.10.60.10:8007ROXMOX-BACKUP
proxmox-backup-client map vm/126/2024-07-09T22:14:26Z drive-scsi0.img --repository root@pam@10.10.60.10:8007ROXMOX-BACKUP

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 8.3T 1 loop
├─loop0p1 259:0 0 16M 1 part
└─loop0p2 259:1 0 8.3T 1 part

mkdir /XX
mount.ntfs /dev/loop0p2 /XX -o ro

the I check mount
/dev/loop0p2 on /XX type fuseblk (ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

Can manage files on mountpoint /XX

After I

umount /XX
proxmox-backup-client unmap /dev/loop0


And all is OK

No way from GUI

Stange thing.

I execute GUI from Node3 , but I find /var/log/proxmox-backup/file-restore/qemu.log on node 1