Hello,
I have multiple Windows 10 VMs (MBR/BIOS boot) backed up on Proxmox Backup Server.
When I try to use File Restore, the small 500MB system partition mounts successfully, but the main C: NTFS partition always fails with the following:
The PVE file-restore VM log shows an ntfs3 metadata error related to $BadClus:
My PVE and PBS versions:
What I have done so far:
The VM uses MBR (not EFI). The partition table looks normal and both partitions are detected.
This appears to be an issue with the ntfs3 driver inside the File Restore environment failing to parse the $BadClus metadata on the NTFS volume, even though Windows handles it fine and CHKDSK /B has already rebuilt the metadata.
Is this a known limitation or bug in the restore image?
Any help or guidance would be greatly appreciated.
Thanks in advance.
I have multiple Windows 10 VMs (MBR/BIOS boot) backed up on Proxmox Backup Server.
When I try to use File Restore, the small 500MB system partition mounts successfully, but the main C: NTFS partition always fails with the following:
Code:
mounting 'drive-scsi0.img.fidx/part/2' failed: all mounts failed or no supported file system (400)The PVE file-restore VM log shows an ntfs3 metadata error related to $BadClus:
Code:
ntfs3(vdb2): ino=8, mi_enum_attr
ntfs3(vdb2): Failed to load $BadClus (-22).My PVE and PBS versions:
Code:
proxmox-ve: 9.0.0 (running kernel: 6.14.11-4-pve)
pve-manager: 9.0.15 (running version: 9.0.15/6ef4690b0bee651d)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-4-pve-signed: 6.14.11-4
proxmox-kernel-6.14: 6.14.11-4
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
amd64-microcode: 3.20250311.1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.4
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.0.15
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.0
libpve-rs-perl: 0.11.3
libpve-storage-perl: 9.0.16
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-3
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.20-1
proxmox-backup-file-restore: 4.0.20-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.0
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.1
pve-cluster: 9.0.7
pve-container: 6.0.14
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.17-2
pve-ha-manager: 5.0.7
pve-i18n: 3.6.1
pve-qemu-kvm: 10.1.2-2
pve-xtermjs: 5.5.0-3
qemu-server: 9.0.27
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
Code:
proxmox-backup-server 4.0.20-1 running version: 4.0.20What I have done so far:
The VM uses MBR (not EFI). The partition table looks normal and both partitions are detected.
- BitLocker has never been enabled on any of the windows systems.
- I ran full CHKDSK repair passes from inside Windows:
Code:
chkdsk C: /F /R /X
chkdsk C: /F /R /B- Both of these completed successfully.
After running them, Windows reports the filesystem as clean with no bad sectors. - I created a new PBS backup after completing the full CHKDSK /B scan.
- Even in this new backup, the File Restore still cannot mount the C: partition and shows the same $BadClus error.
- The VM itself boots normally and Windows can read the filesystem with no issues.
Code:
[2025-11-20T23:11:11+01:00] PBS file restore VM log
[init-shim] beginning user space setup, version 1.0.0
[init-shim] booted Linux version 6.14.6-pbs-restore (build@proxmox) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #1 SMP Wed Jun 25 15:30:39 CEST 2025
[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.46s
[2025-11-20T22:11:11.466Z INFO proxmox_restore_daemon] setup basic system environment...
[2025-11-20T22:11:11.468Z INFO proxmox_restore_daemon] scanning all disks...
[2025-11-20T22:11:11.469Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] Supported FS: ext3, ext4, ext2, vfat, msdos, exfat, iso9660, hfsplus, hfs, sysv, v7, ntfs3, ufs, jfs, xfs, befs, f2fs, bcachefs, 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)
exFAT-fs (vdb): invalid fs_name
exFAT-fs (vdb): failed to read boot sector
exFAT-fs (vdb): failed to recognize exfat type
VFS: could not find a valid V7 on vdb.
ntfs3(vdb): Primary boot signature is not NTFS.
ntfs3(vdb): try to read out of volume at offset 0x1ffffffe00
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
bcachefs (/dev/vdb): error reading default superblock: Not a bcachefs superblock (got magic 00000000-0000-0000-0000-000000000000)
bcachefs (/dev/vdb): error reading superblock: Not a bcachefs superblock layout
bcachefs: bch2_fs_get_tree() error: invalid_sb_layout
[2025-11-20T22:11:11.494Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb2' (2, 136913616896B)
[2025-11-20T22:11:11.496Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb1' (1, 524288000B)
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): bogus number of reserved sectors
FAT-fs (vda): bogus number of reserved sectors
exFAT-fs (vda): invalid boot record signature
exFAT-fs (vda): failed to read boot sector
exFAT-fs (vda): failed to recognize exfat type
VFS: could not find a valid V7 on vda.
ntfs3(vda): Primary boot signature is not NTFS.
ntfs3(vda): try to read out of volume at offset 0x3ffe00
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
bcachefs (/dev/vda): error reading default superblock: Not a bcachefs superblock (got magic b6b6c7df-c3b4-75e9-c2d2-9c746de94cea)
bcachefs (/dev/vda): error reading superblock: Not a bcachefs superblock layout
bcachefs: bch2_fs_get_tree() error: invalid_sb_layout
given image 'drive-tpmstate0-backup.img.fidx' not found with 'drive-tpmstate0-backup', trying with 'drive-tpmstate0-back'.
[2025-11-20T22:11:12.649Z INFO proxmox_restore_daemon] disk scan complete.
EXT4-fs (vdb1): VFS: Can't find ext4 filesystem
EXT4-fs (vdb1): VVFS: 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
exFAT-fs (vdb1): invalid fs_name
exFAT-fs (vdb1): failed to read boot sector
exFAT-fs (vdb1): failed to recognize exfat type
VFS: could not find a valid V7 on vdb1.
[2025-11-20T22:11:15.963Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] mounting '/dev/vdb1' succeeded, fstype: 'ntfs3'
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
exFAT-fs (vdb2): invalid fs_name
exFAT-fs (vdb2): failed to read boot sector
exFAT-fs (vdb2): failed to recognize exfat type
VFS: could not find a valid V7 on vdb2.
ntfs3(vdb2): ino=8, mi_enum_attr
ntfs3(vdb2): Failed to load $BadClus (-22).
ufs: this is not a 44bsd filesystem
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
bcachefs (/dev/vdb2): error reading default superblock: Not a bcachefs superblock (got magic a8006661-901f-0706-1e66-6067807b0800)
bcachefs (/dev/vdb2): error reading superblock: Not a bcachefs superblock layout
bcachefs: bch2_fs_get_tree() error: invalid_sb_layout
[2025-11-20T22:11:17.751Z 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 systemThis appears to be an issue with the ntfs3 driver inside the File Restore environment failing to parse the $BadClus metadata on the NTFS volume, even though Windows handles it fine and CHKDSK /B has already rebuilt the metadata.
Is this a known limitation or bug in the restore image?
Any help or guidance would be greatly appreciated.
Thanks in advance.