[SOLVED] zfs problem: /sbin/zpool: undefined symbol: thread_init

myzamri

Active Member
May 11, 2017
20
3
43
50
I got problem when I updated the zfs package. This is the details after dropping to busybox:

SPL : loaded module 0.7.3-1
znvpair module license 'CDDL' taints' kernel
ZFS loaded module v0.7.3.1-1 , ZFS pool version 5000 , ZFS filesystem version 5

The error (some of them):

Command: /sbin/zpool import -N 'rpool'
Message: /sbin/zpool : symbol lookup error: /sbin/zpool: undefined symbol: thread_init
Error:127

Failed to import pool 'rpool'.

I tried booting from CD (rescue boot) but the error still the same after dropping to busybox.

Looks like to zfs utilities are missing the required libraries or not installed.

How do i install the libraries in busybox?
Can I reinstall proxmox 5.1 with my vm still intact?

Any solution?
 
sounds like you did a partial upgrade. but with a live CD supporting ZFS, import your rpool, chroot into it and fix the installed packages.
 
Debian Stretch is fine unless your pool has features active that require 0.7 (in that case, you need to install packages from testing..)
 
Could you give me point me to a direction on how to import rpool and chroot it
 
Ok thank you for the pointer.

I have solved the problem by using Ubuntu 16.04 desktop live iso. Booted into the live system ran these:

zpool import -N 'rpool'
zpool set mountpoint=/mnt rpool/RPOOL/pve-1
zfs mount rpool/ROOT/pve-1
mount -t proc /proc /mnt/proc
mount --rbind /dev /mnt/dev


#Enter the chroot
chroot /mnt /bin/bash
source /etc/profile
apt update && apt upgrade & apt dist-upgrade <-- this installed new kernel
zpool status <-- test that zpool can be ran ok
zfs set mountpoint=/ rpool/RPOOL/pve-1
exit

The restart the server. Voila!. The server ran ok.

Thank you for the idea to solve this issue fabian.
 
  • Like
Reactions: chrone
you should always run "apt update && apt dist-upgrade", as PVE upgrades will sometimes pull in new packages or remove older ones
 
Hello
I think I have the same error as in this matter, can you confirm me?
could not activate storage 'local-zfs', zfs error: zpool: symbol lookup error: zpool: undefined symbol: zpool_get_prop_literal (500)
Thanks
Captura.JPG
 
probably a different issue.. could you give the output of pveversion -v? was this system recently updated from 6 to 7?
 
probably a different issue.. could you give the output of pveversion -v? was this system recently updated from 6 to 7?
Hello, before the mistake, a colleague made:

apt-get install zfsutils-linux
apt-get install zfs-initramfs

I oponend this case:
https://forum.proxmox.com/threads/c...ined-symbol-zpool_get_prop_literal-500.97389/

The node with problem:

proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-44
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.6.5.9-5

The other node:

proxmox-ve: 5.3-1 (running kernel: 4.15.18-10-pve)
pve-manager: 5.3-8 (running version: 5.3-8/2929af8e)
pve-kernel-4.15: 5.3-1
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-44
libpve-guest-common-perl: 2.0-19
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-36
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-33
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-45
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1
 
those systems are end of life and no longer supported (for over a year already!)
 

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!

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!