FileRestore nicht möglich, Fehlermeldung (BTRFS-Filesystem Ursache?)

D

DasMoritz

Member
Jun 6, 2022
116
6
23
Hallo liebes Forum,

ich habe eine Frage zum FileRestore aus meine Backups. Die Backups liegen auf meinem PBS Server, den FileRestore versuche ich via PVE zu starten.

Ein Screenshot sagt wieder mehr als viele Worte:
1685613031180.png

Kann mir jemand sagen, wodurch diese Fehlermeldung generiert wird bzw. wie ich das lösen kann?

Das Dateisystem, welches auf der vmDisk liegt ist BTRFS, welches durch Synology (XPenology) erzeugt wurde.
Hat jemand einen guten Hinweis wie ich hier dennoch einen FileRestore durchführen kann?

Die ganze VM würde ich nur ungerne wiederherstellen.

Vielen Dank,
MOritz
 
Wie sieht denn das Partitionslayout von der VM aus? Einfach in der aktuellen VM folgenden Befehl ausführen und den Output anhängen (bitte innerhalb von ICODE-Tags):

fdisk -l

Kannst du zusätzlich die Datei /var/log/proxmox-backup/file-restore/qemu.log vom PVE(!) Host hier anhängen?
 
Moin @shanreich

ich hoffe ich habe mit fdisk-l das richtige gemacht (bin per Putty auf die VM und dann ausgeführt). Und ich hoffe auch das CODE korrekt ist und nicht ICODE, mit ICODE sah es ganz sonderbar aus.

Code: 
admin@TMP-XPEnology:/$ sudo fdisk -l
Disk /dev/sda: 52 MiB, 54525952 bytes, 106496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F

Device     Start    End Sectors Size Type
/dev/sda1   2048  32767   30720  15M EFI System
/dev/sda2  32768  94207   61440  30M Linux filesystem
/dev/sda3  94208 102366    8159   4M BIOS boot


Disk /dev/sdc: 4.1 TiB, 4505420693504 bytes, 8799649792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 52 MiB, 54525952 bytes, 106496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B3CAAA25-3CA1-48FA-A5B6-105ADDE4793F

Device     Start    End Sectors Size Type
/dev/sdd1   2048  32767   30720  15M EFI System
/dev/sdd2  32768  94207   61440  30M Linux filesystem
/dev/sdd3  94208 102366    8159   4M BIOS boot


Disk /dev/sde: 6 GiB, 6442450944 bytes, 12582912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x733e7ee5

Device     Boot   Start     End Sectors  Size Id Type
/dev/sde1          2048 4982527 4980480  2.4G fd Linux raid autodetect
/dev/sde2       4982528 9176831 4194304    2G fd Linux raid autodetect


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 301 MiB, 315621376 bytes, 77056 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 301 MiB, 315621376 bytes, 77056 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram2: 301 MiB, 315621376 bytes, 77056 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram3: 301 MiB, 315621376 bytes, 77056 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Und dann hier noch das qemu-Logfile auch als Code:

Code: 
[2023-06-01T11:15:47+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.63s
[2023-06-01T09:15:48.625Z INFO  proxmox_restore_daemon] setup basic system environment...
[2023-06-01T09:15:48.627Z INFO  proxmox_restore_daemon] scanning all disks...
[2023-06-01T09:15:48.628Z 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 (0x00)
FAT-fs (vdb): invalid media value (0x00)
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
[2023-06-01T09:15:48.652Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb2' (2, 2147483648B)
[2023-06-01T09:15:48.654Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-sata1'): found partition '/dev/vdb1' (1, 2550005760B)
EXT4-fs (vdc): VFS: Can't find ext4 filesystem
EXT4-fs (vdc): VFS: Can't find ext4 filesystem
EXT2-fs (vdc): error: can't find an ext2 filesystem on dev vdc.
FAT-fs (vdc): bogus number of reserved sectors
FAT-fs (vdc): bogus number of reserved sectors
VFS: could not find a valid V7 on vdc.
ntfs: (device vdc): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vdc): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vdc): ntfs_fill_super(): Not an NTFS volume.
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
[2023-06-01T09:15:48.678Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-sata0'): found partition '/dev/vdc2' (2, 31457280B)
[2023-06-01T09:15:48.682Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-sata0'): found partition '/dev/vdc3' (3, 4177408B)
[2023-06-01T09:15:48.685Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdc' ('drive-sata0'): found partition '/dev/vdc1' (1, 15728640B)
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
VFS: could not find a valid V7 on vda.
ntfs: (device vda): read_ntfs_boot_sector(): Primary boot sector is invalid.
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
[2023-06-01T09:15:48.703Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-sata2'): found partition '/dev/vda2' (2, 2147483648B)
[2023-06-01T09:15:48.705Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-sata2'): found partition '/dev/vda3' (3, 4500483997696B)
[2023-06-01T09:15:48.708Z INFO  proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-sata2'): found partition '/dev/vda1' (1, 2550005760B)
[2023-06-01T09:15:49.047Z 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.
ntfs: (device vda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda3): ntfs_fill_super(): Not an NTFS volume.
ufs: ufs_fill_super(): bad magic number
befs: (vda3): invalid magic header
F2FS-fs (vda3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda3): Can't find valid F2FS filesystem in 2th superblock
[2023-06-01T09:15:55.345Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8z: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/3' failed: all mounts failed or no supported file system
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.
ntfs: (device vda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda3): ntfs_fill_super(): Not an NTFS volume.
ufs: ufs_fill_super(): bad magic number
befs: (vda3): invalid magic header
F2FS-fs (vda3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda3): Can't find valid F2FS filesystem in 2th superblock
[2023-06-01T09:16:29.998Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8z: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/3' failed: all mounts failed or no supported file system
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.
ntfs: (device vda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda3): ntfs_fill_super(): Not an NTFS volume.
ufs: ufs_fill_super(): bad magic number
befs: (vda3): invalid magic header
F2FS-fs (vda3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda3): Can't find valid F2FS filesystem in 2th superblock
[2023-06-01T09:23:59.299Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8z: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/3' failed: all mounts failed or no supported file system
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): 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.
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
[2023-06-01T09:24:01.984Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8y: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/2' failed: all mounts failed or no supported file system
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.
ntfs: (device vda3): read_ntfs_boot_sector(): Primary boot sector is invalid.
ntfs: (device vda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
ntfs: (device vda3): ntfs_fill_super(): Not an NTFS volume.
ufs: ufs_fill_super(): bad magic number
befs: (vda3): invalid magic header
F2FS-fs (vda3): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (vda3): Can't find valid F2FS filesystem in 2th superblock
[2023-06-01T09:24:07.161Z ERROR proxmox_rest_server::rest] GET /api2/json/list?path=ZHJpdmUtc2F0YTIuaW1nLmZpZHgvcGFydC8z: 400 Bad Request: [client 0.0.0.0:807] mounting 'drive-sata2.img.fidx/part/3' failed: all mounts failed or no supported file system
watchdog expired, shutting down
reboot: Power down
 
Last edited:
Servus!

Ja, ich meinte natürlich CODE!

Ich habe das noch einmal versucht lokal bei mir nachzustellen, da ging btrfs ohne Probleme.

Entschuldige meinen Fehler, aber bei btrfs bringt fdisk -l natürlich wenig. Wesentlich interessanter wäre da eine Auflistung mit btrfs subvolume list -p <path> (<path> = Mountpoint vom Root-Volume).
Soweit ich das sehe, dürften aber zumindest die einzelnen Partitionen korrekt erkannt werden, er scheitert dann erst beim mounten vom subvolume.

Eine Sache, die hier ein Problem sein könnte: Wenn Btrfs Features aktiviert hat, die von der VM, die proxmox-file-restore benutzt, nicht unterstützt werden kann das zu Problemen führen. Man kann die gesetzten Properties mit btrfs property get <path> (<path> = Mountpoint vom Subvolume #3) herausfinden.

Funktionieren denn die Subvolumes #1 & #2? Oder kommt es da auch zu Problemen?


Alternativ kann man probieren mit Hilfe von proxmox-backup-client map [1] das Backup als Loopback-Device zu mappen, dann die Partitionen zu mounten und manuell die Dateien herausfischen.

[1] https://pbs.proxmox.com/docs/command-syntax.html
 
Last edited:
Moin!

Danke dir!
Also das Subvolume #1 kann geöffnet werden, das Subvolume #2 wirft den gleichen Fehler wie #3:

#1:
1685630587264.png

#2:
1685630637741.png

Die anderen Hinweise muss ich heute Abend / Nacht mal versuchen, habe gerade den Nachwuchs vor den Bauch gebunden ;-)
 
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