PVE File Restore: mounting failed: all mounts failed or no supported file system (400)

tprice

New Member
Mar 27, 2025
22
7
3
Hi all,

Just came across this error when attempting to do a file restore from a backup of a Windows VM, mounting 'drive-scsi3.img.fidx/part/1' failed: all mounts failed or no supported file system (400). It looks like this error is seen when attempting to do file restores from multiple Windows machines. Below is logs from /var/log/proxmox-backup/file-restore,

Doing a full backup restore works without issue. Has anyone seen this before?

[2025-08-11T14:04:03.610Z 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 (vdd1): VFS: Can't find ext4 filesystem
EXT4-fs (vdd1): VFS: Can't find ext4 filesystem
EXT2-fs (vdd1): error: can't find an ext2 filesystem on dev vdd1.
FAT-fs (vdd1): bogus number of reserved sectors
FAT-fs (vdd1): bogus number of reserved sectors
exFAT-fs (vdd1): invalid fs_name
exFAT-fs (vdd1): failed to read boot sector
exFAT-fs (vdd1): failed to recognize exfat type
VFS: could not find a valid V7 on vdd1.
ntfs3(vdd1): Primary boot signature is not NTFS.
ntfs3(vdd1): try to read out of volume at offset 0xe0ffef8000
ufs: ufs_fill_super(): bad magic number
befs: (vdd1): invalid magic header
F2FS-fs (vdd1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdd1): Can't find valid F2FS filesystem in 2th superblock
bcachefs (/dev/vdd1): error reading default superblock: Not a bcachefs superblock (got magic 00000000-0000-0000-0000-000000000000)
bcachefs (/dev/vdd1): error reading superblock: Not a bcachefs superblock layout
bcachefs: bch2_fs_get_tree() error: invalid_sb_layout
[2025-08-11T14:04:17.772Z 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
watchdog expired, shutting down
reboot: Power down
 
Update: I was able to mount the disk in the snapshot to the PBS server and access the files through the CLI

1. proxmox-backup-client snapshots --repository YOUR_REPO vm/VMID -> Lists snapshots for specified VMID
2. proxmox-backup-client map vm/209/2025-08-06T06:37:25Z drive-scsi0.img --repository YOUR_REPO -> Maps the disk drive-scsi0.img from the chosen snapshot vm/209/2025-08-06T06:37:25Z to the local machine. (In my case mapped to /dev/loop0)
3. I then checked with fdisk -l /dev/loop0 to see the filesystem type of SFS
4. apt install ldmtool -> For managing Windows Dynamic disks
5. ldmtool create all -> Creates a device mapper for the previously mapped drive to /dev/loop0
6. You should then see the drive in /dev/mapper/ldm_vol_disk_name
7. apt install ntfs-3g
8. mount -t ntfs-3g /dev/mapper/ldm_vol_disk_name /yourmountpoint. You should then be able to navigate to the mounted drive and pull the file you need.
9. Umount /dev/mapper/ldm_vol_disk_name -> To unmount
10. ldmtool remove all -> cleans up dynamic disks

I would still appreciate any insight into why the GUI file restore is not working. For now this is a workaround.
 
Last edited:
  • Like
Reactions: Yendric