file restore error, failed: all mounts failed or no supported file system (400)

[akihiro hamada]

Guest OS
Windows Server 2019 (JP)

Disks
sata0 [R:] NTFS 10GB
scsi0 [C:] NTFS 200GB boot
scsi1 [D:] NTFS 400GB
scsi2 [R:] NTFS 600GB work area, without backup.

disk scsi0 [C:] is file restore error.
mounting 'drive-scsi0.img.fidx/part/1' failed: all mounts failed or no supported file system (400)

disk sata0 [R:] and scsi1 [D:] is file restore OK.


ProxmoxVE log
/var/log/proxmox-backup/file-restore/qemu.log
[2024-05-10T14:48:43+09: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 1.14s
[2024-05-10T05:48:45.146Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-05-10T05:48:45.147Z INFO proxmox_restore_daemon] scanning all disks...
[2024-05-10T05:48:45.148Z 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: Failed to load $Volume (-22).
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-05-10T05:48:45.221Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb1' (1, 214747316224B)
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): invalid media value (0xf3)
FAT-fs (vdc): invalid media value (0xf3)
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: ufs_fill_super(): bad magic number
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
[2024-05-10T05:48:45.308Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vdc' ('drive-sata0'): found partition '/dev/vdc1' (1, 10734272512B)
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 (0x00)
FAT-fs (vda): invalid media value (0x00)
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-05-10T05:48:45.371Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-scsi1'): found partition '/dev/vda1' (1, 429493583872B)
[2024-05-10T05:48:46.519Z 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.
[2024-05-10T05:48:59.648Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vda1' succeeded, fstype: 'ntfs3'
ntfs3: vda1: failed to convert "8d77" to iso8859-1
ntfs3: vda1: failed to convert "79fb" to iso8859-1
EXT4-fs (vdb1): VFS: Can't find ext4 filesystem
EXT4-fs (vdb1): VFS: Can't find ext4 filesystem
EXT2-fs (vdb1): error: can't find an ext2 filesystem on dev vdb1.
FAT-fs (vdb1): bogus number of reserved sectors
FAT-fs (vdb1): bogus number of reserved sectors
VFS: could not find a valid V7 on vdb1.
[2024-05-10T05:49:31.340Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb1' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vdb1): invalid magic header
F2FS-fs (vdb1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdb1): Can't find valid F2FS filesystem in 2th superblock
[2024-05-10T05:49:31.380Z 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 (vdb1): VFS: Can't find ext4 filesystem
EXT4-fs (vdb1): VFS: Can't find ext4 filesystem
EXT2-fs (vdb1): error: can't find an ext2 filesystem on dev vdb1.
FAT-fs (vdb1): bogus number of reserved sectors
FAT-fs (vdb1): bogus number of reserved sectors
VFS: could not find a valid V7 on vdb1.
[2024-05-10T05:49:39.430Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vdb1' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vdb1): invalid magic header
F2FS-fs (vdb1): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vdb1): Can't find valid F2FS filesystem in 2th superblock
[2024-05-10T05:49:39.470Z 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 (vdc1): VFS: Can't find ext4 filesystem
EXT4-fs (vdc1): VFS: Can't find ext4 filesystem
EXT2-fs (vdc1): error: can't find an ext2 filesystem on dev vdc1.
FAT-fs (vdc1): bogus number of reserved sectors
FAT-fs (vdc1): bogus number of reserved sectors
VFS: could not find a valid V7 on vdc1.
[2024-05-10T05:49:45.029Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vdc1' succeeded, fstype: 'ntfs3'
ntfs3: vdc1: failed to convert "30b7" to iso8859-1
ntfs3: vdc1: failed to convert "30d7" to iso8859-1

 

[Nymphick]

Today I encountered the same problem. Proxmox 8.2.4, PBS 3.2-7. When restoring a file via the web interface, an error occurs when mounting "drive-scsiXX.img.fidx/part/1": all mounts failed or there is no supported file system (400). At the same time, on PBS we make a map proxmox-backup-client vm/115/2024-10-18T17:00:02Z disk-sсsi0.img --repository localhost:data0
mount -t ntfs -o ro /dev/loop1p2 /mnt/test3
and there is access to the files

 

[sander93]

Today I encountered the same problem. Proxmox 8.2.4, PBS 3.2-7. When restoring a file via the web interface, an error occurs when mounting "drive-scsiXX.img.fidx/part/1": all mounts failed or there is no supported file system (400). At the same time, on PBS we make a map proxmox-backup-client vm/115/2024-10-18T17:00:02Z disk-sсsi0.img --repository localhost:data0
mount -t ntfs -o ro /dev/loop1p2 /mnt/test3
and there is access to the files

We are using same versions, and having same problem but in this case only on a single disk of a vm, disk-2 (disk0 and 1 have no problem).

The only thing we see is that the disk with the problem (disk-2) is resized/expanded, and it looks like after that it isn't working any more for the specific disk

 

[patrick.pesegodinski]

I have the same problem.

To test, I install new vm with Windows Server 2022 and atached this disk, but the problem return.

 

[sucher-42]

Dear Sirs,

Versions:
PVE1: 8.3.2
Backup Server: 3.3.2
VM: Win11 Pro Client

I have the same issue;
Tying to select files at "restore:

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

Is there any fix for this or any progress for a fix ?

Thank's in advance,

regards

 

[sucher-42]

2025-01-25

It is solved and working with the patch today.
Thank you;
regards

 

[patrick.pesegodinski]

2025-01-25

It is solved and working with the patch today.
Thank you;
regards

For me no.

What's the patch?

 

[sucher-42]

Hi Patrick,

not really a Patch. Only the Update last week they provided. I testen it on 2 different locations, 3 Systems.I can see the Windows files now.
Regards

 

[sucher-42]

Hi Patrick,
did a test again and it fails now again . No glue, it feels like a test of indicators light: Works, don't, works; don't ...
I'm not really satisfied

Sorry

 

[patrick.pesegodinski]

Hi Patrick,
did a test again and it fails now again . No glue, it feels like a test of indicators light: Works, don't, works; don't ...
I'm not really satisfied

Sorry

Hi Sucher.

No problem.

I try many things to fix the problem, but I never can.

 

[erik-symagic]

PVE 8.3.3 and PBS 3.3.2

I have the same issue with the error "mounting 'drive-virtio1.img.fidx/part/1' failed: all mounts failed or no supported file system (400)" when doing a file restore of the 2nd disk, D: drive with NTFS on Windows Server 2019 . When accessing the first drive (C, it works fine.

So I have updated systems but the issue remains, even with the backups made after the last updates & reboots.
What can I do?

Note: I have a subscription for this PVE server.

 

[patrick.pesegodinski]

PVE 8.3.3 and PBS 3.3.2

I have the same issue with the error "mounting 'drive-virtio1.img.fidx/part/1' failed: all mounts failed or no supported file system (400)" when doing a file restore of the 2nd disk, D: drive with NTFS on Windows Server 2019 . When accessing the first drive (C, it works fine.

So I have updated systems but the issue remains, even with the backups made after the last updates & reboots.
What can I do?

Note: I have a subscription for this PVE server.

Have you opened a ticket with support?

 

[sucher-42]

PBS 33.2
PVE 8.3.3

Hi,
I can't try to give an explanation.
But today it worked again.
???
Didn't change anything.

I try to understand; no way.

(Air Pressure today here:
1001 hPa )

 

[erik-symagic]

Have you opened a ticket with support?

I will open a ticket today, thanks for the suggestion.

 

[erik-symagic]

I will open a ticket today, thanks for the suggestion.

I do not have enterprise support for this server, just community :|
But to add a detail; no Bitlocker is active on the disks or any other encryption. It's just a 200GB NTFS basic drive.

 

[patrick.pesegodinski]

I will open a ticket today, thanks for the suggestion.

I do not have enterprise support for this server, just community :|
But to add a detail; no Bitlocker is active on the disks or any other encryption. It's just a 200GB NTFS basic drive.

Have you ever configured data deduplication on that disk?

 

[sucher-42]

Hi Patrick,
No, I didn't. I'm using 2 PBS. And, sometimes it works, sometimes it doesn't. Did you get any advice from Proxmox support?

 

[patrick.pesegodinski]

Hi Patrick,
No, I didn't. I'm using 2 PBS. And, sometimes it works, sometimes it doesn't. Did you get any advice from Proxmox support?

Hey friend.

I tested it on 2 PBS but it doesn't work. I don't have paid support and no one from the technical team has commented on this topic so far.

 

[patrick.pesegodinski]

Hello friends.

You already test map backup wit command line?

 

[erik-symagic]

Hello friends.

You already test map backup wit command line?

I will make a new backup using the commandline and try to restore this. Is there a realistic chance that this will make a difference?