[SOLVED] mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400)

MisterDeeds · Jul 25, 2023

Dear all

I have a PVE system in use together with a Proxmox backup server. Now when I want to perform the "file restore" from the PVE, the following message appears:

Code:

mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400)

I use a normal GPT partition. However, I am not sure if it is because of the 128MB Reserved partition:

Does anyone know the problem? Thank you and best regards

MisterDeeds · Jul 26, 2023

I have now changed the partition to have only one and run a new backup. Unfortunately, the same message still appears. Can anyone help me?

MisterDeeds · Aug 6, 2023

Dear all

In consultation with Proxmox support, it turns out that the restore via web gui mounts the disk into a temporary virtual machine with the "ntfs-3g" command. This shows in the logfile of the PVE host under:

Code:

/var/log/proxmox-backup/file-restore/

an error.

There it was apparent that the file system had an error. Windows seems to have no problem with it, but the ntfs-3g command does.
A simple

Code:

CHKDSK D: /F /R /X

fixed the problem.

Thanks again to the great proxmox support!

Best regards

JL17 · Jan 10, 2024

Hello, i have the same problem with an NTFS disk backup.
If I try to do a "file restore" from GUI, i get the message:

mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400)

The file-restore log (/var/log/proxmox-backup/file-restore/qemu.log) show this information about ntfs:

ntfs: (device vda1): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda1): ntfs_fill_super(): Not an NTFS volume.

If i map the backup with "proxmox-backup-client map" and then mount the mapping i can access all the files without problem. Seems like "file-restore" and "map" works different. Is there a way to configure "file-restore" so i can force the mount an NTFS dirty-flagged partition?

Thanx in advance

fabian · Jan 10, 2024

how are you mounting the mapped snapshot? please give the exact command line/options used!

JL17 · Jan 16, 2024

fabian said:
how are you mounting the mapped snapshot? please give the exact command line/options used!

Using this commands:

proxmox-backup-client map vm/101/2024-01-10T07:15:12Z drive-virtio1.img --repository root@pam@192.168.1.2:8007:bk1 --ns jls
ls -lah /dev/loop0*
mkdir /mnt/test
mount -r /dev/loop0p1 /mnt/test
ls /mnt/test/

fabian · Jan 17, 2024

what does "mount" say about the /mnt/test mountpoint afterwards?

JL17 · Jan 18, 2024

fabian said:
what does "mount" say about the /mnt/test mountpoint afterwards?

/dev/loop0p1 on /mnt/test type fuseblk (ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

Mounts ok using that commands, I can acces all the files.
The problem is when I try to do a "file restore" from GUI

fabian · Jan 18, 2024

yeah, that seems to use a very different driver (ntfs-3g?) than the file-restore VM (which uses the in-tree kernel "ntfs" one)..

JL17 · Jan 18, 2024

can I change the driver in the file-restore?

fabian · Jan 18, 2024

no, that's hard-coded at the moment..

JL17 · Jan 18, 2024

Ok thanks for your help!

kellogs · Jan 16, 2025

MisterDeeds said:
Dear all

In consultation with Proxmox support, it turns out that the restore via web gui mounts the disk into a temporary virtual machine with the "ntfs-3g" command. This shows in the logfile of the PVE host under:

Code:

/var/log/proxmox-backup/file-restore/

an error.

There it was apparent that the file system had an error. Windows seems to have no problem with it, but the ntfs-3g command does.
A simple

Code:

CHKDSK D: /F /R /X

fixed the problem.

Thanks again to the great proxmox support!

Best regards

I am facing the same issue as well

EXT4-fs (vdb2): VFS: Can't find ext4 filesystem
EXT4-fs (vdb2): VFS: Can't find ext4 filesystem
EXT2-fs (vdb2): error: can't find an ext2 filesystem on dev vdb2.
FAT-fs (vdb2): bogus number of reserved sectors
FAT-fs (vdb2): bogus number of reserved sectors
VFS: could not find a valid V7 on vdb2.
[2025-01-16T23:09:43.112Z WARN proxmox_restore_daemon:

roxmox_restore_daemon::disk] mount error on '/dev/vdb2' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vdb2): invalid magic header
F2FS-fs (vdb2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdb2): Can't find valid F2FS filesystem in 2th superblock
[2025-01-16T23:09:43.128Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/2' failed: all mounts failed or no supported file system

Netzblicker · Jul 2, 2025

Hm, nearly the same error here:
I want to restore a file, but on IDE0 and folder 3 (where the files of c: are in) i get the error:
mounting 'drive-ide0.img.fidx/part/3' failed: all mounts failed or no supported file system (400)

I ran the chckdsk but it didn't help. My qemu.log says:

root@hv1:/var/log/proxmox-backup/file-restore# tail -f qemu.log
VFS: could not find a valid V7 on vdc3.
ntfs: (device vdc3): ntfs_attr_find(): Inode is corrupt. Run chkdsk.
ntfs: (device vdc3): ntfs_read_inode_mount(): Failed to lookup $MFT/$DATA attribute extent. $MFT is corrupt. Run chkdsk.
ntfs: (device vdc3): ntfs_read_inode_mount(): Failed. Marking inode as bad.
ntfs: (device vdc3): ntfs_fill_super(): Failed to load essential metadata.
ufs: ufs_fill_super(): bad magic number
befs: (vdc3): invalid magic header
F2FS-fs (vdc3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdc3): Can't find valid F2FS filesystem in 2th superblock
[2025-07-02T06:43:27.779Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtaWRlMC5pbWcuZmlkeC9wYXJ0LzM%3D: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-ide0.img.fidx/part/3' failed: all mounts failed or no supported file system

Any idea?

fabian · Jul 2, 2025

that sounds like your NTFS file system uses some features (or is in some specific state at the time of the backup) that is not supported by the Linux NTFS3 driver.. we've not yet been able to reproduce this problem, if you can find exact steps (starting with a fresh disk) that trigger this it would likely help narrowing it down.

Netzblicker · Jul 2, 2025

The funny thing is: i have a cluster with 3 Servers and a PBS, 7 VMs (all installed the same way) and only one of them has this error

fabian · Jul 2, 2025

it is possible it is not related to file system features, but to the state (either at time of the backup, or just by the nature of the I/O that has been done on it - e.g., a certain number of files, a certain write pattern that causes different on-disk structures, ..). are all snapshots of the VM affected, or just some?

Netzblicker · Jul 2, 2025

Poorly all snapshots from this VM are affectes

fabian · Jul 2, 2025

then the next step would be to find out what makes this disk special/different - is it bigger? has more data on it? what kind of data? special applications writing to it that might do something weird? properties of the file system? ...

swoop · Jul 3, 2025

Hello,

i have a simmilar problem.
When i try to restore the hole Machine i get:

Code:

error before or during data restore, some or all disks were not completely restored. VM 107 state is NOT cleaned up.

TASK ERROR: command '/usr/bin/pbs-restore --repository root@pam@<PBS>:pbs-backup vm/107/2025-07-01T22:00:00Z drive-efidisk0.img.fidx 'rbd:container/vm-107-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/container.keyring' --verbose --format raw --skip-zero' failed: exit code 255

When i try to file restore, i get this:

Code:

mounting 'drive-virtio1.img.fidx/part/2' failed: all mounts failed or no supported file system (400)

i have a 3 node cluster, my winodws servers got hacked an crypted so i need to restore the files, or bedder the hole machine.

i have the newest proxmox-backup-restore-image installed:

Code:

dpkg --list proxmox-backup-restore-image
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                         Version      Architecture Description
+++-============================-============-============-===============================================================
ii  proxmox-backup-restore-image 0.7.0        amd64        Kernel/initramfs images for Proxmox Backup single-file restore.

But i can Mount the latest disk-backup, but i cannot extract the files:

Code:

proxmox-backup-client map vm/107/2025-07-01T22:00:01Z drive-virtio1.img.fidx --repository root@pam@<PBS>:pbs-backup
mount -r /dev/loop0p2 /mnt/restore/

mount
/dev/loop0p2 on /mnt/restore type ntfs (ro,relatime,uid=0,gid=0,fmask=0177,dmask=077,nls=utf8,errors=continue,mft_zone_multiplier=1)

ls -l
ls: cannot access 'Datenaustausch _alt': Input/output error
ls: cannot access 'Folder2': Input/output error
ls: cannot access 'Treiber': Input/output error
ls: cannot access 'Wsus': Input/output error
total 16
dr-x------ 1 root root 16384 Jul  1 23:24  Datenaustausch
d????????? ? ?    ?        ?            ? 'Datenaustausch _alt'
d????????? ? ?    ?        ?            ?  Folder2
d????????? ? ?    ?        ?            ?  Treiber
d????????? ? ?    ?        ?            ?  Wsus

i urgently need help

i've updated all nodes and PBS

[SOLVED] mounting 'drive-scsiXX.img.fidx/part/1' failed: all mounts failed or no supported file system (400)

Active Member

Active Member

Active Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Active Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Member

Proxmox Staff Member

Active Member

We value your privacy