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

I have the same problem with two VMs. Windows Server 2012R2 and Windows Server 2019.

On both I can see the files on the operating system drive, but the secondary drive with the data always returns the same error.

PVE and PBS are 100% updated.

- The error:

1735922227162.png

- qemu.log:

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
[2025-01-03T15:01:02.159Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc2' (2, 103809024B)
[2025-01-03T15:01:02.163Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc3' (3, 134217728B)
[2025-01-03T15:01:02.166Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc1' (1, 314572800B)
[2025-01-03T15:01:02.170Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc4' (4, 53132394496B)
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
[2025-01-03T15:01:02.201Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda2' (2, 268299141120B)
[2025-01-03T15:01:02.205Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda1' (1, 134217728B)
[2025-01-03T15:01:03.770Z INFO proxmox_restore_daemon] disk scan complete.
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-03T15:01:22.982Z WARN proxmox_restore_daemon::proxmox_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-03T15:01:23.027Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTEuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mountin>
watchdog expired, shutting down
reboot: Power down
 
looks like that particular disk is using some NTFS feature that the linux driver doesn't understand..
 
yeah, the file restore VM is Linux based and the driver there simply doesn't support everything the windows one does.. you can try to find out which particular feature/setting/.. is responsible and then avoid it in your VMs. or you can manually use windows VMs for recovering individual files ("proxmox-backup-client map .." allows you to access the backup as block device which you can then hand to any VM as virtual disk)
 
This VM is just a file server, there are no other more complex configurations.

I can connect bakcup with the "proxmox-backup-client" command, but when mounting the error I posted above is generated.
 
Last edited:
NTFS seems to work for me on 8.3.2, both on Server 2022 and Server 2019 editions.
What not working is drives formatted with ReFS. There I get the same error as described here...
 
gr3Y said:
NTFS seems to work for me on 8.3.2, both on Server 2022 and Server 2019 editions.
What not working is drives formatted with ReFS. There I get the same error as described here...
Click to expand...
I have other VMs with the same operating system working normally. But these two VMs, one from 2019 and the other from 2022 (old 2012 mentioned above), do not work. This 2022 is a new server and I attached the Server 2012 virtual disk and the error still persists. In 2019 I created a new virtual disk and copied the files and it is still not possible to recover from the backup.
 
Hello all,

Adding my stone here...
I've been switching to Proxmox for a few months. I built a first PBS server for test purposes with slow storage (NAS with NFS) and had this same file restore error after a while on some backups.
I blamed it on the slowness of the storage and possibly the garbage collector as most operations were very time-consuming (backups, verification, GC) and I suspected access conflicts that could generate corruptions.
So I built a second PBS with much faster local storage. I configured a file server backup with a 5 Tb data disk. After the first backup, file restore worked without a hitch. After the second, i.e. incremental, backup, it is no longer possible to use file restore with either the first or the second backup on the data disk, even though restoring from system disk is OK...
The source machine has not undergone any changes in the meantime, so I don't think the NTFS features used are to blame.
GC was never run on the second server, so it's not the culprit.
From my experience with my first server, it seems to happen more frequently with larger disks.
I don't know how many of us have this problem, but it doesn't seem to be marginal, so maybe it's worth a bug tracking?
Regards.
 
  • Like
Reactions: cwitsup
_Thom_ said:
Hello all,

Adding my stone here...
I've been switching to Proxmox for a few months. I built a first PBS server for test purposes with slow storage (NAS with NFS) and had this same file restore error after a while on some backups.
I blamed it on the slowness of the storage and possibly the garbage collector as most operations were very time-consuming (backups, verification, GC) and I suspected access conflicts that could generate corruptions.
So I built a second PBS with much faster local storage. I configured a file server backup with a 5 Tb data disk. After the first backup, file restore worked without a hitch. After the second, i.e. incremental, backup, it is no longer possible to use file restore with either the first or the second backup on the data disk, even though restoring from system disk is OK...
The source machine has not undergone any changes in the meantime, so I don't think the NTFS features used are to blame.
GC was never run on the second server, so it's not the culprit.
From my experience with my first server, it seems to happen more frequently with larger disks.
I don't know how many of us have this problem, but it doesn't seem to be marginal, so maybe it's worth a bug tracking?
Regards.
Click to expand...
I did the same tests as yours and continued to have the problem.

The error is the same, but the apparent cause is different.
 
Hi all, in case you're still getting this issue - it's because of Windows Bitlocker pre-encryption.

Even when you're not consciously using Bitlocker the OS will pre-encrypt part of the drive, which stops Proxmox from reading it. Do the following to fix it:

From an admin command prompt in Windows, run:
manage-bde -off c:

(replace c: with whichever drive you're concerned with).

The drive will start to decrypt. You can check ongoing status with:
manage-bde -status c:

You'll see the status like this:
decrypt.jpg

Once decryption is complete, run a backup in Proxmox of the VM. Then attempt a file restore:
restore.jpg

Problem solved :)
 
  • Like
Reactions: techadmin-local
You must log in or register to reply here.
Top Bottom