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

A

Artem.ws

Member
Dec 20, 2021
27
1
8
34
I have same problem, like in this topic (German) https://forum.proxmox.com/threads/file-restore-aus-proxmox-backup-server.133168/ Member fabian build proxmox-backup-restore-image_0.6.1~test1_amd64.deb for test, and it works not as well

After upgrading to proxmox-backup-restore-image_0.6.1~test1_amd64.deb i can mount (very slowly mount, but ok) and see ntfs volume. but not all directorys. If name of directory contain for example Cyrillic name, i can't see this directory
 
Last edited:
could you post a debug log of the restore? the linked thread contains instructions ;)
 
fabian said:
could you post a debug log of the restore? the linked thread contains instructions ;)
Click to expand...
[2024-04-02T22:11:37+07: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 Tue Nov 28 16:37:51 UTC 2023

[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 2.14s
[2024-04-02T15:11:42.153Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-04-02T15:11:42.156Z INFO proxmox_restore_daemon] scanning all disks...
[2024-04-02T15:11:42.159Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] Supported FS: reiserfs, ext3, ext4, ext2, vfat, msdos, iso9660, hfsplus, hfs, sysv, v7, ntfs, 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.
ntfs: (device vdb): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vdb): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vdb): ntfs_fill_super(): Not an NTFS volume.
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-04-02T15:11:42.222Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb2' (2, 53160706048B)
[2024-04-02T15:11:42.227Z 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): invalid media value (0xf3)
FAT-fs (vda): invalid media value (0xf3)
VFS: could not find a valid V7 on vda.
ntfs: (device vda): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda): ntfs_fill_super(): Not an NTFS volume.
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-04-02T15:11:42.285Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda2' (2, 5372866723840B)
[2024-04-02T15:11:42.290Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda1' (1, 134217728B)
[2024-04-02T15:11:52.807Z 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.
ntfs: (device vda2): ntfs_attr_find(): Inode is corrupt. Run chkdsk.
ntfs: (device vda2): ntfs_read_inode_mount(): Failed to lookup $MFT/$DATA attribute extent. $MFT is corrupt. Run chkdsk.
ntfs: (device vda2): ntfs_read_inode_mount(): Failed. Marking inode as bad.
ntfs: (device vda2): ntfs_fill_super(): Failed to load essential metadata.
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-04-02T15:12:07.390Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2NzaTIuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-scsi2.img.fidx/part/2' failed: all mounts failed or no supported file system
 
that is with the old version though, what about the new version?
 
fabian said:
that is with the old version though, what about the new version?
Click to expand...
you mean, what will, if i'll install package proxmox-backup-restore-image_0.6.1~test1_amd64.deb ? I tried. NTFS mount ok(very slowly), but i can't see files and folders with Cyrillic names.
 
please do that and post the log :)
 
fabian said:
please do that and post the log :)
Click to expand...
[2024-04-04T15:12:14+07: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 Thu Feb 1 09:48:23 CET 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.98s
[2024-04-04T08:12:20.983Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-04-04T08:12:20.988Z INFO proxmox_restore_daemon] scanning all disks...
[2024-04-04T08:12:20.991Z INFO proxmox_restore_daemon::proxmox_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: Alternative boot signature is not NTFS.
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-04-04T08:12:21.213Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb2' (2, 53160706048B)
[2024-04-04T08:12:21.220Z 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): 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-04-04T08:12:21.280Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda2' (2, 6446608547840B)
[2024-04-04T08:12:21.287Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda1' (1, 134217728B)
[2024-04-04T08:12:22.793Z 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-04-04T08:13:11.228Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] mounting '/dev/vda2' succeeded, fstype: 'ntfs3'
 
could you try "mapping" the image (using "proxmox-backup-client map ...") and then mounting it using the "ntfs3" driver with and without the "utf8" mount option and see if you can list the files on the shell? you can also do all of that in a VM if you prefer, or using the debug mode of "proxmox-file-restore" that allows accessing via a virtual serial console.
 
fabian said:
could you try "mapping" the image (using "proxmox-backup-client map ...") and then mounting it using the "ntfs3" driver with and without the "utf8" mount option and see if you can list the files on the shell? you can also do all of that in a VM if you prefer, or using the debug mode of "proxmox-file-restore" that allows accessing via a virtual serial console.
Click to expand...

1. proxmox-backup-client map ... ok
2. mkdir test
3. mount -t ntfs3 /dev/loop0p2 test
4. cd test
5. ls
All ok, and i can see files and folders with Cyrillic names.

how can i mount without utf8? Utf8 enabled by default:

/dev/loop0p2 on /root/test type ntfs3 (ro,relatime,uid=0,gid=0,iocharset=utf8)
 
Last edited:
Kungolf said:
you could probably try to mount image with option to select different charset:

mount -t ntfs3 /dev/loop0p2 test -o iocharset=<charset>

charsets list (example): https://man7.org/linux/man-pages/man7/charsets.7.html

Hope it helps - K.
Click to expand...
root@hp1:~# mount -t ntfs3 /dev/loop0p2 test -o iocharset=ASCII
mount: /root/test: wrong fs type, bad option, bad superblock on /dev/loop0p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.

[448476.650324] /dev/loop0p2: Can't open blockdev
[448476.656009] Cannot load nls ASCII
 
Artem.ws said:
root@hp1:~# mount -t ntfs3 /dev/loop0p2 test -o iocharset=ASCII
mount: /root/test: wrong fs type, bad option, bad superblock on /dev/loop0p2, missing codepage or helper program, or other error.
dmesg(1) may have more information after failed mount system call.

[448476.650324] /dev/loop0p2: Can't open blockdev
[448476.656009] Cannot load nls ASCII
Click to expand...
Sorry for the obvious question, but the mount error may indicate the lack of ntfs-3g package (the "missing helper program" part). Are you sure you have it installed on your server?
Also please try "mount -t ntfs" without "3" after package check
 
Last edited:
Kungolf said:
Sorry for the obvious question, but the mount error may indicate the lack of ntfs-3g package (the "missing helper program" part). Are you sure you have it installed on your server?
Click to expand...
Yes, i'm sure)

root@hp1:~# apt install ntfs-3g
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ntfs-3g is already the newest version (1:2022.10.3-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded.

Kungolf said:
Also please try "mount -t ntfs" without "3" after package check
Click to expand...

root@hp1:~# mount -t ntfs /dev/loop0p2 test -o iocharset=ASCII
Error opening '/dev/loop0p2' read-write
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Could not mount read-write, trying read-only

Works ok, Cyrillic files and folders also ok
 
  • Like
Reactions: Kungolf
Kungolf said:
I hope read-only will be sufficient for your purpose as I don't recall any tool to clean NTFS partition outside Windows environment. Best regards - K.
Click to expand...
But problem in web-gui in proxmox. I can't restore files from web-gui.
 
@Kungolf "ntfs3" and "ntfs-3g" are two very different things ;) I guess the non-utf8 test would be something like "iso8559-1"? in any case, it is interesting to know that it works on the host - that should hopefully mean that we can also make it work in the file-restore VM :)
 
fabian said:
@Kungolf "ntfs3" and "ntfs-3g" are two very different things ;) I guess the non-utf8 test would be something like "iso8559-1"? in any case, it is interesting to know that it works on the host - that should hopefully mean that we can also make it work in the file-restore VM :)
Click to expand...
well, like i said, mount works only with utf8 (((
 
it is possible it's our Rust code mishandling something somewhere, I'd have to setup a reproducer first :)
 
  • Like
Reactions: Artem.ws
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back