PBS Can't restore file on one VM.

[hzk916]

Hi
On PBS. Trying to restore files on one of the VM's fails (104 Win10). All others restore is fine. I read somewhere to do a chkdsk /r /f /x would sort it out. Made no difference. See attached image.

 

[Chris]

Hi,
please post the output of cat /var/log/proxmox-backup/file-restore/qemu.log from the Proxmox VE host you are using to access the disk filesystem, that might tell

 

[hzk916]

Here you go from /var/log/proxmox-backup/file-restore


[2024-12-09T07:25:08+00: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.05s
[2024-12-09T07:25:09.037Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-12-09T07:25:09.038Z INFO proxmox_restore_daemon] scanning all disks...
[2024-12-09T07:25:09.039Z 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 (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
[2024-12-09T07:25:09.090Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-ide0'): found partition '/dev/vda2' (2, 375208472064B)
[2024-12-09T07:25:09.092Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-ide0'): found partition '/dev/vda3' (3, 545591296B)
[2024-12-09T07:25:09.094Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-ide0'): found partition '/dev/vda1' (1, 52428800B)
[2024-12-09T07:25:10.300Z INFO proxmox_restore_daemon] disk scan complete.
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
FAT-fs (vda2): bogus number of reserved sectors
FAT-fs (vda2): bogus number of reserved sectors
VFS: could not find a valid V7 on vda2.
[2024-12-09T07:25:19.331Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vda2' succeeded, fstype: 'ntfs3'
watchdog expired, shutting down
reboot: Power down

 

[Chris]

[2024-12-09T07:25:19.331Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vda2' succeeded, fstype: 'ntfs3'

Is this the log from right after you try to access the files on the partition which gives the error? As the filesystem seems to be detected correctly according to the logs.

 

[hzk916]

OK Just went in and tried to connect, other folders in that VM look ok, you can see the files. Only Partition 2 (498.86GB) that does not open. Attached jpg of error and log.

[2024-12-16T13:47:16+00: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.03s
[2024-12-16T13:47:17.027Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-12-16T13:47:17.029Z INFO proxmox_restore_daemon] scanning all disks...
[2024-12-16T13:47:17.030Z 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 (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
[2024-12-16T13:47:17.059Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0'): found partition '/dev/vda4' (4, 555880448B)
[2024-12-16T13:47:17.061Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0'): found partition '/dev/vda2' (2, 535647706624B)
[2024-12-16T13:47:17.063Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0'): found partition '/dev/vda3' (3, 559321088B)
[2024-12-16T13:47:17.065Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] drive 'vda' ('drive-virtio0'): found partition '/dev/vda1' (1, 104857600B)
[2024-12-16T13:47:18.370Z INFO proxmox_restore_daemon] disk scan complete.
EXT4-fs (vda3): VFS: Can't find ext4 filesystem
EXT4-fs (vda3): VFS: Can't find ext4 filesystem
EXT2-fs (vda3): error: can't find an ext2 filesystem on dev vda3.
FAT-fs (vda3): bogus number of reserved sectors
FAT-fs (vda3): bogus number of reserved sectors
VFS: could not find a valid V7 on vda3.
[2024-12-16T13:47:23.496Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vda3' succeeded, fstype: 'ntfs3'
EXT4-fs (vda4): VFS: Can't find ext4 filesystem
EXT4-fs (vda4): VFS: Can't find ext4 filesystem
EXT2-fs (vda4): error: can't find an ext2 filesystem on dev vda4.
FAT-fs (vda4): bogus number of reserved sectors
FAT-fs (vda4): bogus number of reserved sectors
VFS: could not find a valid V7 on vda4.
[2024-12-16T13:47:25.975Z INFO proxmox_restore_daemon:roxmox_restore_daemon::disk] mounting '/dev/vda4' succeeded, fstype: 'ntfs3'
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
FAT-fs (vda2): bogus number of reserved sectors
FAT-fs (vda2): bogus number of reserved sectors
VFS: could not find a valid V7 on vda2.
ntfs3: vda2: Failed to initialize $Secure (-2).
[2024-12-16T13:47:29.907Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs3) - ENOENT: No such file or directory
ufs: ufs_fill_super(): bad magic number
befs: (vda2): invalid magic header
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2024-12-16T13:47:29.913Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtdmlydGlvMC5pbWcuZmlkeC9wYXJ0LzI%3D: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-virtio0.img.fidx/part/2' failed: all mounts failed or no supported file system

 

[Chris]

[2024-12-16T13:47:29.907Z WARN proxmox_restore_daemon:roxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs3) - ENOENT: No such file or directory

What filesystem is located on that partition? Is this even an NTFS?

 

[hzk916]

Yes it is a Windows10 x64 and C:\ drive is NTFS.

 

[Chris]

Trying to restore files on one of the VM's fails (104 Win10). All others restore is fine. I read somewhere to do a chkdsk /r /f /x would sort it out. Made no difference. See attached image.

Did you perform a new backup of the VM after running the filesystem check mentioned? This will of course not restore a corrupt filesystem of the already backed up snapshots. Also, is this filesystem encrypted?

From your screenshots it seems the snapshot has never been verified on the PBS side. Please run a verify job for the snapshot in question and see if the verification is successful.

Further, you could try to map and mount the filesystem manually. Running proxmox-backup-client map <snapshot> <archive-name> will map the snapshot to a loop device as returned by the output, which you then can mount via mount -t ntfs3 <loopdevice> <mountpoint>. See if that succeeds or if this tells more about why the mount fails.

 

[hzk916]

Not a full backup. No, not encrypted. I'll try the verification next.

 

[hzk916]

I deleted the backup for that VM and ran a complete new backup last night. I noticed that the "Change protection" was not working but is now.
I am running the verify now, will post results soon as complete.

 

[hzk916]

Attached is the log of the verification.