[SOLVED] ZFS Problem nach Software-Update

Nov 24, 2017
6
1
8
51
Hallo,

in meinem Cluster hab ich bei einem Knoten ein Software-Update durchgeführt (apt-get update). Nun ist der Zugriff auf den ZFS-Pool kaputt:

Code:
zpool list
zpool: symbol lookup error: /lib/libzfs.so.2: undefined symbol: efi_rescan
Folgende Pakete wurden aktualisiert:
Code:
proxmox-widget-toolkit:amd64 (1.0-28, 2.1-1)
panopta-agent:amd64 (2019.70.5, 2019.92.2)
libcmap4:amd64 (2.4.4-pve1, 3.0.2-pve4)
proxmox-mini-journalreader:amd64 (1.0-1, 1.1-1)
libsasl2-modules-db:amd64 (2.1.27~101-g0780600+dfsg-3, 2.1.27~101-g0780600+dfsg-3+deb9u1)
linux-libc-dev:amd64 (4.9.189-3+deb9u1, 4.9.189-3+deb9u2)
ifupdown:amd64 (0.8.19, 0.8.35+pve1)
git-man:amd64 (1:2.11.0-3+deb9u4, 1:2.11.0-3+deb9u5)
pve-firmware:amd64 (2.0-7, 3.0-4)
libgs9:amd64 (9.26a~dfsg-0+deb9u5, 9.26a~dfsg-0+deb9u6)
libquorum5:amd64 (2.4.4-pve1, 3.0.2-pve4)
ksm-control-daemon:amd64 (1.2-2, 1.3-1)
libdevmapper-event1.02.1:amd64 (2:1.02.137-pve6, 2:1.02.155-pve3)
pve-docs:amd64 (5.4-2, 6.1-3)
git:amd64 (1:2.11.0-3+deb9u4, 1:2.11.0-3+deb9u5)
libjs-extjs:amd64 (6.0.1-2, 6.0.1-10)
libsasl2-2:amd64 (2.1.27~101-g0780600+dfsg-3, 2.1.27~101-g0780600+dfsg-3+deb9u1)
pve-i18n:amd64 (1.1-4, 2.0-3)
pve-xtermjs:amd64 (3.12.0-1, 3.13.2-1)
libvotequorum8:amd64 (2.4.4-pve1, 3.0.2-pve4)
spl:amd64 (0.7.13-pve1~bpo2, 0.8.2-pve2)
novnc-pve:amd64 (1.0.0-3, 1.1.0-1)
ghostscript:amd64 (9.26a~dfsg-0+deb9u5, 9.26a~dfsg-0+deb9u6)
libgs9-common:amd64 (9.26a~dfsg-0+deb9u5, 9.26a~dfsg-0+deb9u6)
pve-edk2-firmware:amd64 (1.20190312-1, 2.20191127-1)
libnvpair1linux:amd64 (0.7.13-pve1~bpo2, 0.8.2-pve2)
omping:amd64 (0.0.5-1, 0.0.5-2)
libuutil1linux:amd64 (0.7.13-pve1~bpo2, 0.8.2-pve2)
libcpg4:amd64 (2.4.4-pve1, 3.0.2-pve4)
libpve-apiclient-perl:amd64 (2.0-5, 3.0-2)
libcorosync-common4:amd64 (2.4.4-pve1, 3.0.2-pve4)
libssl1.0.2:amd64 (1.0.2t-1~deb9u1, 1.0.2u-1~deb9u1)

Kernel Version

Linux 4.15.18-20-pve #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200)

An welchem Paket kann das Problem liegen und kann ich auf die frühere Version zurück?
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
3,009
327
83
bitte mal `pveversion -v` posten
und auch den content der sources.list files: '/etc/apt/sources.list' , '/etc/apt/sources.list.d/*list'

der laufende kernel klingt nach einem PVE 5.x - aber die upgegradeten pakete scheinen aus PVE 6.x zu kommen (zfs 0.8.2, corosync 3.0.2)

Ich hoffe das hilft!
 
Nov 24, 2017
6
1
8
51
pveversion -v

proxmox-ve: 5.4-2 (running kernel: 4.15.18-20-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.13: 5.2-2
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.13.16-4-pve: 4.13.16-51
pve-kernel-4.13.16-3-pve: 4.13.16-50
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.13-1-pve: 4.13.13-31
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-2-pve: 4.10.17-20
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libpve-access-control: 5.1-12
libpve-apiclient-perl: 3.0-2
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.1.0-1
proxmox-widget-toolkit: 2.1-1
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 2.20191127-1
pve-firewall: 3.0-22
pve-firmware: 3.0-4
pve-ha-manager: 2.0-9
pve-i18n: 2.0-3
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.13.2-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2


cat /etc/apt/sources.list

deb http://ftp.de.debian.org/debian stretch main contrib

# security updates
deb http://security.debian.org stretch/updates main contrib
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription
deb http://packages.panopta.com/deb stable main

cat /etc/apt/sources.list.d/*
deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

Hm, seh gerade, dass das Enterprise Repo auf buster zeigt, ich benutze aber noch Stretch. Hab das gerade geändert, aber ein Update danach hilft auch nicht:

Code:
apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  pve-kernel-4.15
The following packages will be upgraded:
  libpve-common-perl pve-container
2 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 201 kB of archives.
After this operation, 2.048 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 libpve-common-perl all 5.0-56 [96,3 kB]
Get:2 http://download.proxmox.com/debian/pve stretch/pve-no-subscription amd64 pve-container all 2.0-41 [105 kB]
Fetched 201 kB in 0s (5.723 kB/s)       
Reading changelogs... Done
(Reading database ... 178170 files and directories currently installed.)
Preparing to unpack .../libpve-common-perl_5.0-56_all.deb ...
Unpacking libpve-common-perl (5.0-56) over (5.0-55) ...
Preparing to unpack .../pve-container_2.0-41_all.deb ...
Unpacking pve-container (2.0-41) over (2.0-40) ...
Setting up libpve-common-perl (5.0-56) ...
Processing triggers for systemd (232-25+deb9u12) ...
Setting up pve-container (2.0-41) ...
Processing triggers for pve-ha-manager (2.0-9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for pve-manager (5.4-13) ...
Processing triggers for systemd (232-25+deb9u12) ...
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
3,009
327
83
apt-get upgrade
PVE muss mit `apt-get dist-upgrade` upgegraded werden - 'apt-get upgrade' reicht nicht aus!

was ist denn das output von `dpkg -l |grep -i zfs` ?
 
Nov 24, 2017
6
1
8
51
PVE muss mit `apt-get dist-upgrade` upgegraded werden - 'apt-get upgrade' reicht nicht aus!
Ich wollte eigentlich auch kein dist-upgrade machen

Code:
ii  libzfs2linux                         0.7.13-pve1~bpo2                  amd64        OpenZFS filesystem library for Linux
ii  libzpool2linux                       0.7.13-pve1~bpo2                  amd64        OpenZFS pool library for Linux
ii  zfs-initramfs                        0.7.13-pve1~bpo2                  all          OpenZFS root filesystem capabilities for Linux - initramfs
ii  zfsutils-linux                       0.7.13-pve1~bpo2                  amd64        command-line tools to manage OpenZFS filesystems
 

Stoiko Ivanov

Proxmox Staff Member
Staff member
May 2, 2018
3,009
327
83

MartyMcFly

New Member
Feb 4, 2020
1
0
1
43
Ich habe das gleiche Problem, d.h. die gleiche Fehlermeldung, allerdings nach einem Neustart und lande in der BusyBox. Hat jemand eine Idee, wie ich von dort die Library downgraden kann?
 

About

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

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 your own in 60 seconds.

Buy now!