[SOLVED] Restoring windows files on ReFS - connection error

[fluxX04]

Hey,

backup of a 1.6 TB disk runs successfully. I then checked if i can file restore from that disk but i get a connection error on the PVE side.


API request: https://pve.domain.my/api2/json/nodes/localhost/storage/PBS/file-restore/list?volume=PBS:backup/vm/100/2021-06-05T21:33:05Z&filepath=XXXXdmUtc2NzaTIuaW1nLmZpZHgvcGFyXXXX
Response: {"data":null}

Log on the pbs side:

2021-06-07T11:18:36+02:00: starting new backup reader datastore 'backup01': "/mnt/datastore/backup01"
2021-06-07T11:18:36+02:00: protocol upgrade done
2021-06-07T11:18:36+02:00: GET /download
2021-06-07T11:18:36+02:00: download "/mnt/datastore/backup/vm/100/2021-06-05T21:33:05Z/index.json.blob"
2021-06-07T11:18:36+02:00: GET /download
2021-06-07T11:18:36+02:00: download "/mnt/datastore/backup/vm/100/2021-06-05T21:33:05Z/drive-scsi2.img.fidx"
2021-06-07T11:18:36+02:00: register chunks in 'drive-scsi2.img.fidx' as downloadable.
2021-06-07T11:18:36+02:00: GET /chunk
2021-06-07T11:18:36+02:00: download chunk "/mnt/datastore/backup/.chunks/a3cc/a3ccba085d0605fc688ccee6b531611e6f5a79bc2e601b919aa2fa8aa6bb55dd"
2021-06-07T11:18:38+02:00: GET /chunk
2021-06-07T11:18:38+02:00: download chunk "/mnt/datastore/backup/.chunks/c295/c295722dff165748e5d50303271a7e1dab8c5d26a8089f03c4f235a5e73b104b"
2021-06-07T11:19:09+02:00: GET /chunk
2021-06-07T11:19:09+02:00: download chunk "/mnt/datastore/backup/.chunks/9df3/9df34f60a67c2db12f018b36d62208ba2226c1ef23e943af93acce71f509405c"

Nothing important in other logs.
The other drive (NTFS) on the same vm works smoothless.

Spoiler: VM Config

agent: 1
boot: order=scsi0;ide0
cores: 4
cpu: host
ide0: none,media=cdrom
machine: pc-i440fx-5.2
memory: 4092
name: 100
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win10
scsi0: storage01:vm-100-disk-0,cache=writeback,discard=on,iothread=1,size=80G,ssd=1
scsi1: storage01:vm-100-disk-1,cache=writeback,discard=on,iothread=1,size=450G,ssd=1
scsi2: storage01:vm-100-disk-2,cache=writeback,discard=on,iothread=1,size=1677722M,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=324a0f64-8f26-478f-999b-dd7fbfe775fb
sockets: 1
vga: virtio
vmgenid: ed5b232c-3eaa-45f6-ac2a-100406f6ac2f

Spoiler: PVE Packages

proxmox-ve: 6.4-1 (running kernel: 5.4.114-1-pve)
pve-manager: 6.4-8 (running version: 6.4-8/185e14db)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph: 15.2.11-pve1
ceph-fuse: 15.2.11-pve1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: not correctly installed
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.4-1
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-3
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.8-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-cluster: 6.4-1
pve-container: 3.3-5
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.2-4
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

Spoiler: PBS Packages

proxmox-backup: 1.0-4 (running kernel: 5.4.114-1-pve)
proxmox-backup-server: 1.1.9-1 (running version: 1.1.9)
pve-kernel-5.4: 6.4-2
pve-kernel-helper: 6.4-2
pve-kernel-5.4.114-1-pve: 5.4.114-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ifupdown2: 3.0.0-1+pve3
libjs-extjs: 6.0.1-10
proxmox-backup-docs: 1.1.9-1
proxmox-backup-client: 1.1.9-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-6
pve-xtermjs: 4.7.0-3
smartmontools: 7.2-pve2
zfsutils-linux: 2.0.4-pve1

Is this currently a bug or is the filesystem atm not supported?

Thanks,
Greetz

 

[dcsapak]

what does the log under '/var/log/proxmox-backup/file-restore/qemu.log' say?

 

[fluxX04]

Hey @dcsapak,

the content of the log file:

[2021-06-07T11:18:36+02:00] PBS file restore VM log
[init-shim] beginning user space setup
[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.78s
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi1'): found partition '/dev/vdb2' (2, 483165995008B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi1'): found partition '/dev/vdb1' (1, 16759808B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc2' (2, 84844758528B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc3' (3, 515899392B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-scsi0'): found partition '/dev/vdc1' (1, 524288000B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda2' (2, 1759029231616B)
[2021-06-07T09:18:36Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda1' (1, 134217728B)
[2021-06-07T09:18:36Z 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
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (reiserfs) - EINVAL: Invalid argument
EXT4-fs (vdb2): VFS: Can't find ext4 filesystem
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (ext3) - EINVAL: Invalid argument
EXT4-fs (vdb2): VFS: Can't find ext4 filesystem
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (ext4) - EINVAL: Invalid argument
EXT2-fs (vdb2): error: can't find an ext2 filesystem on dev vdb2.
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (ext2) - EINVAL: Invalid argument
FAT-fs (vdb2): bogus number of reserved sectors
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (vfat) - EINVAL: Invalid argument
FAT-fs (vdb2): bogus number of reserved sectors
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (msdos) - EINVAL: Invalid argument
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (iso9660) - EINVAL: Invalid argument
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (hfsplus) - EINVAL: Invalid argument
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (hfs) - EINVAL: Invalid argument
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (sysv) - EINVAL: Invalid argument
VFS: could not find a valid V7 on vdb2.
[2021-06-07T09:19:01Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vdb2' (v7) - EINVAL: Invalid argument
[2021-06-07T09:19:01Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] mounting '/dev/vdb2' succeeded, fstype: 'ntfs'
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (reiserfs) - EINVAL: Invalid argument
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext3) - EINVAL: Invalid argument
EXT4-fs (vda2): VFS: Can't find ext4 filesystem
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext4) - EINVAL: Invalid argument
EXT2-fs (vda2): error: can't find an ext2 filesystem on dev vda2.
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ext2) - EINVAL: Invalid argument
FAT-fs (vda2): bogus number of reserved sectors
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (vfat) - EINVAL: Invalid argument
FAT-fs (vda2): bogus number of reserved sectors
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (msdos) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (iso9660) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (hfsplus) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (hfs) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (sysv) - EINVAL: Invalid argument
VFS: could not find a valid V7 on vda2.
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (v7) - EINVAL: Invalid argument
ntfs: (device vda2): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda2): ntfs_fill_super(): Not an NTFS volume.
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ntfs) - EINVAL: Invalid argument
ufs: ufs_fill_super(): bad magic number
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (ufs) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (jfs) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (xfs) - EINVAL: Invalid argument
befs: (vda2): invalid magic header
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (befs) - EINVAL: Invalid argument
F2FS-fs (vda2): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda2): Can't find valid F2FS filesystem in 2th superblock
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (f2fs) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z WARN  proxmox_restore_daemon::proxmox_restore_daemon::disk] mount error on '/dev/vda2' (btrfs) - EINVAL: Invalid argument
[2021-06-07T09:19:08Z ERROR proxmox_backup::server::rest] GET /api2/json/list?path=XXXXdmUtc2NzaTIuaW1nLmZpZHgvcGFyXXXX: 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
watchdog expired, shutting down
reboot: Power down

Greetz

 

[dcsapak]

ah i overlooked the 'refs' in the title . sorry no refs is not supported, only filesystems that are available in the linux kernel

 

[fluxX04]

Hey,

no problem, thanks for the info

Greetz

 

[Cookiefamily]

You can do a file-level restore in a bit more manual way by using the proxmox-backup-client map command. This maps the disk to a read-only loopback device.
You should then be able to mount refs by hand. This requires a refs driver... There is a company well known for their filesystem ports that offers refs for linux. I have not tested this and it is probably somewhat experimental, so I won't encourage you to do this