No Swap After Dist Upgrade

yena

Renowned Member
Nov 18, 2011
380
5
83
Hello,
in a brand new server i have done a apt-upgrade with no-subscription repo.
Now at boot i have this error:
"A strat Job is running for dev-zvol-rpool-swap.device"
after some minutes, the system load but i hav not swap mounted:

root@storage:~# ls -la /dev/zvol/
ls: cannot access '/dev/zvol/': No such file or directory


root@storage:~# free -h
total used free shared buff/cache available
Mem: 125G 1.6G 124G 34M 101M 123G

-------------------------------------------------------------------------------

zpool status
pool: rpool
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(5) for details.
scan: none requested
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
sda2 ONLINE 0 0 0
sdb2 ONLINE 0 0 0


root@storage:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool 10.2G 220G 96K /rpool
rpool/ROOT 1.67G 220G 96K /rpool/ROOT
rpool/ROOT/pve-1 1.67G 220G 1.67G /
rpool/data 96K 220G 96K /rpool/data
rpool/swap 8.50G 229G 64K -


--------------------------------------------------------------------------------


root@storage:~# zpool import -N rpool
cannot import 'rpool': a pool with that name already exists
use the form 'zpool import <pool | id> <newpool>' to give it a new name

--------------------------------------------------------------------------------

I Have done:

/etc/default/zfs
ZFS_INITRD_PRE_MOUNTROOT_SLEEP='10'
ZFS_INITRD_POST_MODPROBE_SLEEP='6'
update-initramfs -u


and
rootdelay=10 on /etc/default/grub
update-grub

-------------------------------------------------------------------------

root@storage:~# cat /lib/udev/rules.d/60-zvol.rules
# Persistent links for zvol
#
# persistent disk links: /dev/zvol/dataset_name
# also creates compatibility symlink of /dev/dataset_name

KERNEL=="zd*" SUBSYSTEM=="block" ACTION=="add|change" PROGRAM="/lib/udev/zvol_id $tempnode" SYMLINK+="zvol/%c %c"


root@storage:~# ls -la /lib/udev/zvol_id
-rwxr-xr-x 1 root root 10232 Nov 6 09:14 /lib/udev/zvol_id
----------------------------------------------------------------------------





pveversion -V
proxmox-ve: 5.0-19 (running kernel: 4.10.17-2-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.10.17-2-pve: 4.10.17-20
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-15
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9

-----------------------------------------------------

Thanks!
 

Attachments

  • proxmox-errore2.jpg
    proxmox-errore2.jpg
    117.1 KB · Views: 3
  • proxmox-errore.jpg
    proxmox-errore.jpg
    26.9 KB · Views: 3
  • journalctl-b.txt
    journalctl-b.txt
    166.2 KB · Views: 2
Last edited:
your kernel has 0.6.5.x ZFS/SPL modules, but your ZFS userspace utilities are on 0.7.3. this does not work.. please verify your repository configuration and run the update again - your node is only halfway upgraded to 5.1...
 
your kernel has 0.6.5.x ZFS/SPL modules, but your ZFS userspace utilities are on 0.7.3. this does not work.. please verify your repository configuration and run the update again - your node is only halfway upgraded to 5.1...

If i do a dist-upgrade instead upgrade i can't boot anymore, i attach a capture screen.
( Can't mount ZFS Volumes .. )
 

Attachments

  • proxmox-errore3.jpg
    proxmox-errore3.jpg
    117.3 KB · Views: 9

So the solution is boot with old kernel and install manualy this kernel:

"to help trouble shoot upgrading issues, we built a 4.10-based kernel including ZFS 0.7.3, available on pvetest. you need to manually download and install it, as no meta-package pulls it in automatically:
http://download.proxmox.com/debian/...pve-kernel-4.10.17-5-pve_4.10.17-25_amd64.deb"

I have notice that on this server i have two SFP ethernet with iscsi protocol configurable on bios settings .. this maybe the issue ..

How can i set this "custom kernel" the default kernel for the boot process ?
(your kernel 17-5 solve the problem )
Thanks
 

Attachments

  • proxmox-err4.jpg
    proxmox-err4.jpg
    188.6 KB · Views: 2
Last edited:
So the solution is boot with old kernel and install manualy this kernel:

"to help trouble shoot upgrading issues, we built a 4.10-based kernel including ZFS 0.7.3, available on pvetest. you need to manually download and install it, as no meta-package pulls it in automatically:
http://download.proxmox.com/debian/...pve-kernel-4.10.17-5-pve_4.10.17-25_amd64.deb"

I have notice that on this server i have two SFP ethernet with iscsi protocol configurable on bios settings .. this maybe the issue ..

How can i set this "custom kernel" the default kernel for the boot process ?
(your kernel 17-5 solve the problem )
Thanks


Done:
The custom kernel is on a submenu (second row) so:

vi /etc/default/grub

GRUB_DEFAULT="gnulinux-4.10.17-5-pve-advanced-418214a2fdeb0bb0" -> doasn't work

GRUB_DEFAULT="1>1" -> Works

update-grub