[SOLVED] Problems after upgrading 7.X to 8.X. Can't file restore via PBS

A

Artem.ws

Member
Dec 20, 2021
27
1
8
35
Hi! Everything was ok, but when i upgrade proxmox from 7.x to 8.x, i can not use file restore option in backup. When i'm trying to restore file, i've got message - "VM exited before connection could be established (500)"

Log from /var/log/proxmox-backup/file-restore/qemu*

Packages version:
1. Proxmox-backup-client (version 3.1.5-1)
2. Proxmox-backup-file-restore (version 3.1.5-1)

[2024-03-30T16:23:45+07: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
/proxmox-restore-daemon: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory

--------
ERROR: Init shim failed

child process /proxmox-restore-daemon (pid=53 exitcode=127) exited unexpectedly, check log for more info
--------

reboot: Power down

All works ok, if i downgrade 2 packages:
1. Proxmox-backup-client (version 2.4.6-1)
2. Proxmox-backup-file-restore (version 2.4.6-1)


So, how to fix it?

This is log from downgraded packages:

[2024-03-30T16:27:18+07: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.58s
[2024-03-30T09:27:22.581Z INFO proxmox_restore_daemon] setup basic system environment...
[2024-03-30T09:27:22.583Z INFO proxmox_restore_daemon] scanning all disks...
[2024-03-30T09:27:22.583Z 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-03-30T09:27:22.603Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vdb' ('drive-scsi0'): found partition '/dev/vdb2' (2, 53160706048B)
[2024-03-30T09:27:22.605Z 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-03-30T09:27:22.622Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda2' (2, 5372866723840B)
[2024-03-30T09:27:22.624Z INFO proxmox_restore_daemon::proxmox_restore_daemon::disk] drive 'vda' ('drive-scsi2'): found partition '/dev/vda1' (1, 134217728B)
[2024-03-30T09:27:22.983Z INFO proxmox_restore_daemon] disk scan complete.
 
Last edited:
It's also strange, libcrypto.so.3 exist, if check it via ldd

root@hp1:~# ldd /usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/proxmox-restore-daemon
linux-vdso.so.1 (0x00007ffead3f6000)
libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x0000740ad8a00000)
libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x0000740ad97bb000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x0000740ad96ff000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000740ad881f000)
/lib64/ld-linux-x86-64.so.2 (0x0000740ad97d0000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x0000740ad96df000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x0000740ad8f21000)
root@hp1:~# ldd /usr/bin/proxmox-file-restore
linux-vdso.so.1 (0x00007fff240a8000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x000071b507956000)
libssl.so.3 => /lib/x86_64-linux-gnu/libssl.so.3 (0x000071b5078ac000)
libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x000071b506a00000)
libacl.so.1 => /lib/x86_64-linux-gnu/libacl.so.1 (0x000071b5078a1000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x000071b506f44000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000071b50681f000)
/lib64/ld-linux-x86-64.so.2 (0x000071b50796a000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x000071b50787f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x000071b506740000)
 
Last edited:
Hi!

Do your system using Selinux or Apparmor?


Code: 
$> apt-get install policycoreutils


Check the output of the followings:
$> aa-status
$> sestatus

You can disable, or make rule for exceptions ( I prefer disable both on Proxmox )
Code: 
/etc/default/grub
GRUB_CMDLINE_LINUX="... apparmor=0 selinux=0"

/etc/selinux/config
SELINUX=disabled

REBOOT
 
Last edited:
emunt6 said:
Hi!

Do your system using Selinux or Apparmor?


Code: 
$> apt-get install policycoreutils


Check the output of the followings:
$> aa-status
$> sestatus

You can disable, or make rule for exceptions ( I prefer disable both)
Code: 
/etc/default/grub
GRUB_CMDLINE_LINUX="... apparmor=0 selinux=0"

/etc/selinux/config
SELINUX=disabled

REBOOT
Click to expand...
No, i don't use Selinux or Apparmor.
 
I think, problem in file-restore initramfs, when installing DEB package... What i did...

1. Unpacked proxmox-backup-file-restore_2.4.6-1_amd64.deb and proxmox-backup-file-restore_3.1.5-1_amd64.deb
2. All this two packages contains:
/usr/bin/proxmox-file-restore
/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/proxmox-restore-daemon

3. Installed proxmox-backup-file-restore_2.4.6-1_amd64.deb
4. Replaced

/usr/bin/proxmox-file-restore
/usr/lib/x86_64-linux-gnu/proxmox-backup/file-restore/proxmox-restore-daemon

from version 3.1.5-1 and all works ok..

So, this is bug, or it's my locally problem?
 
Problem solved. I just reinstall this packages to latest version:

1. proxmox-backup-client
2. proxmox-backup-file-restore
3. proxmox-backup-restore-image
 
You must log in or register to reply here.
Top Bottom