[SOLVED] The following packages have been kept back: zfs-initramfs zfs-zed zfsutils-linux

r4dh4l

Well-Known Member
Feb 5, 2018
91
7
48
Proxmox version: Virtual Environment 6.4-14

Hello,

since my last proxmox upgrade (to my current version Virtual Environment 6.4-14 under Debian 10.12) I have the problem that "apt uprade" lists:
Code:
# apt upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  zfs-initramfs zfs-zed zfsutils-linux
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

# apt list --upgradable
Listing... Done
zfs-initramfs/stable 2.0.7-pve1 all [upgradable from: 0.8.5-pve1]
zfs-zed/stable 2.0.7-pve1 amd64 [upgradable from: 0.8.5-pve1]
zfsutils-linux/stable 2.0.7-pve1 amd64 [upgradable from: 0.8.5-pve1]

# apt policy zfs-initramfs
zfs-initramfs:
  Installed: 0.8.5-pve1
  Candidate: 2.0.7-pve1
  Version table:
     2.0.7-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.6-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.5-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
 *** 0.8.5-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
        100 /var/lib/dpkg/status
     0.8.4-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.7.12-2+deb10u2 500
        500 http://ftp.debian.org/debian buster/contrib amd64 Packages
# apt policy zfs-zed
zfs-zed:
  Installed: 0.8.5-pve1
  Candidate: 2.0.7-pve1
  Version table:
     2.0.7-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.6-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.5-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
 *** 0.8.5-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
        100 /var/lib/dpkg/status
     0.8.4-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.7.12-2+deb10u2 500
        500 http://ftp.debian.org/debian buster/contrib amd64 Packages
# apt policy zfsutils-linux
zfsutils-linux:
  Installed: 0.8.5-pve1
  Candidate: 2.0.7-pve1
  Version table:
     2.0.7-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.6-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.5-pve1~bpo10+1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     2.0.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
 *** 0.8.5-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
        100 /var/lib/dpkg/status
     0.8.4-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.4-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.3-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.2-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve2 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.8.1-pve1 500
        500 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 Packages
     0.7.12-2+deb10u2 500
        500 http://ftp.debian.org/debian buster/contrib amd64 Packages

I had this problem for months but ignored it during lack of time. I remember some dependency problems during my last attempts and to report this problem I tried antoher time to install the packages. Now I'm very confused that trying to install the first package in the list (zfs-initramfs) works and is asking how to handle the config file:

Code:
# apt install zfs-initramfs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libnvpair3linux libuutil3linux libzfs4linux libzpool4linux zfs-zed zfsutils-linux
Suggested packages:
  nfs-kernel-server samba-common-bin
The following packages will be REMOVED:
  libnvpair1linux libuutil1linux libzfs2linux libzpool2linux
The following NEW packages will be installed:
  libnvpair3linux libuutil3linux libzfs4linux libzpool4linux
The following packages will be upgraded:
  zfs-initramfs zfs-zed zfsutils-linux
3 upgraded, 4 newly installed, 4 to remove and 0 not upgraded.
Need to get 2,094 kB of archives.
After this operation, 1,329 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 zfs-initramfs all 2.0.7-pve1 [31.0 kB]
Get:2 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 zfsutils-linux amd64 2.0.7-pve1 [471 kB]
Get:3 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 zfs-zed amd64 2.0.7-pve1 [67.9 kB]
Get:4 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 libnvpair3linux amd64 2.0.7-pve1 [52.7 kB]
Get:5 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 libzfs4linux amd64 2.0.7-pve1 [221 kB]
Get:6 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 libuutil3linux amd64 2.0.7-pve1 [46.4 kB]
Get:7 https://enterprise.proxmox.com/debian/pve buster/pve-enterprise amd64 libzpool4linux amd64 2.0.7-pve1 [1,204 kB]
Fetched 2,094 kB in 0s (8,655 kB/s)
Reading changelogs... Done
(Reading database ... 78383 files and directories currently installed.)
Preparing to unpack .../zfs-initramfs_2.0.7-pve1_all.deb ...
Unpacking zfs-initramfs (2.0.7-pve1) over (0.8.5-pve1) ...
Preparing to unpack .../zfsutils-linux_2.0.7-pve1_amd64.deb ...
Unpacking zfsutils-linux (2.0.7-pve1) over (0.8.5-pve1) ...
Preparing to unpack .../zfs-zed_2.0.7-pve1_amd64.deb ...
Unpacking zfs-zed (2.0.7-pve1) over (0.8.5-pve1) ...
(Reading database ... 78462 files and directories currently installed.)
Removing libzfs2linux (0.8.5-pve1) ...
Removing libzpool2linux (0.8.5-pve1) ...
Removing libnvpair1linux (0.8.5-pve1) ...
Selecting previously unselected package libnvpair3linux.
(Reading database ... 78437 files and directories currently installed.)
Preparing to unpack .../libnvpair3linux_2.0.7-pve1_amd64.deb ...
Unpacking libnvpair3linux (2.0.7-pve1) ...
Selecting previously unselected package libzfs4linux.
Preparing to unpack .../libzfs4linux_2.0.7-pve1_amd64.deb ...
Unpacking libzfs4linux (2.0.7-pve1) ...
(Reading database ... 78454 files and directories currently installed.)
Removing libuutil1linux (0.8.5-pve1) ...
Selecting previously unselected package libuutil3linux.
(Reading database ... 78447 files and directories currently installed.)
Preparing to unpack .../libuutil3linux_2.0.7-pve1_amd64.deb ...
Unpacking libuutil3linux (2.0.7-pve1) ...
Selecting previously unselected package libzpool4linux.
Preparing to unpack .../libzpool4linux_2.0.7-pve1_amd64.deb ...
Unpacking libzpool4linux (2.0.7-pve1) ...
Setting up libnvpair3linux (2.0.7-pve1) ...
Setting up libuutil3linux (2.0.7-pve1) ...
Setting up libzfs4linux (2.0.7-pve1) ...
Setting up libzpool4linux (2.0.7-pve1) ...
Setting up zfsutils-linux (2.0.7-pve1) ...
Installing new version of config file /etc/cron.d/zfsutils-linux ...

Configuration file '/etc/default/zfs'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** zfs (Y/I/N/O/D/Z) [default=N] ? D
--- /etc/default/zfs    2021-02-22 16:57:18.625092245 +0100
+++ /etc/default/zfs.dpkg-new   2022-01-12 18:46:26.000000000 +0100
@@ -46,20 +46,12 @@
 # try '/dev/disk/by-id'.
 # The old variable will still work in the code, but is deprecated.
 #ZPOOL_IMPORT_PATH="/dev/disk/by-vdev:/dev/disk/by-id"
-ZPOOL_IMPORT_PATH="/dev/disk/by-vdev:/dev/disk/by-id"
 
 # List of pools that should NOT be imported at boot
 # when ZPOOL_IMPORT_ALL_VISIBLE is 'yes'.
 # This is a space separated list.
 #ZFS_POOL_EXCEPTIONS="test2"
 
-# List of pools that SHOULD be imported at boot by the initramfs
-# instead of trying to import all available pools.  If this is set
-# then ZFS_POOL_EXCEPTIONS is ignored.
-# Only applicable for Debian GNU/Linux {dkms,initramfs}.
-# This is a semi-colon separated list.
-#ZFS_POOL_IMPORT="pool1;pool2"
-
 # Should the datasets be mounted verbosely?
 # A mount counter will be used when mounting if set to 'yes'.
 VERBOSE_MOUNT='no'
@@ -106,35 +98,6 @@
 # Only applicable for Debian GNU/Linux {dkms,initramfs}.
 ZFS_DKMS_DISABLE_STRIP='no'
 
-# Wait for this many seconds in the initrd pre_mountroot?
-# This delays startup and should be '0' on most systems.
-# Only applicable for Debian GNU/Linux {dkms,initramfs}.
-ZFS_INITRD_PRE_MOUNTROOT_SLEEP='0'
-
-# Wait for this many seconds in the initrd mountroot?
-# This delays startup and should be '0' on most systems. This might help on
-# systems which have their ZFS root on a USB disk that takes just a little
-# longer to be available
-# Only applicable for Debian GNU/Linux {dkms,initramfs}.
-ZFS_INITRD_POST_MODPROBE_SLEEP='0'
-
-# List of additional datasets to mount after the root dataset is mounted?
-#
-# The init script will use the mountpoint specified in the 'mountpoint'
-# property value in the dataset to determine where it should be mounted.
-#
-# This is a space separated list, and will be mounted in the order specified,
-# so if one filesystem depends on a previous mountpoint, make sure to put
-# them in the right order.
-#
-# It is not necessary to add filesystems below the root fs here. It is
-# taken care of by the initrd script automatically. These are only for
-# additional filesystems needed. Such as /opt, /usr/local which is not
-# located under the root fs.
-# Example: If root FS is 'rpool/ROOT/rootfs', this would make sense.
-#ZFS_INITRD_ADDITIONAL_DATASETS="rpool/ROOT/usr rpool/ROOT/var"
-
 # Optional arguments for the ZFS Event Daemon (ZED).
 # See zed(8) for more information on available options.
 #ZED_ARGS="-M"
-

So how I should proceed? Keep my current "/etc/default/zfs" or install the package maintainer one? Related to zfs packages I'm very afraid to destroy my RAID. That's why I'm asking.
 
that "apt uprade" lists:
always use `apt full-upgrade` (being the same as `apt dist-upgrade`) to upgrade PVE installations - never simply apt upgrade!

So how I should proceed? Keep my current "/etc/default/zfs" or install the package maintainer one? Related to zfs packages I'm very afraid to destroy my RAID. That's why I'm asking.
These questions from dpkg usually only get asked if you modified the file - did you do so? - do you remember why?

from a very quick glance I don't think that the modification to the file are relevant - and that you should be safe to simply use the new version
However, like always when modifying system configuration:
Make sure you have a working and tested backup before proceeding

I hope this helps!
 
  • Like
Reactions: r4dh4l
always use `apt full-upgrade` (being the same as `apt dist-upgrade`) to upgrade PVE installations - never simply apt upgrade!
Okay, I will keep this in mind. So the first problem "The following packages have been kept back: zfs-initramfs zfs-zed zfsutils-linux" was caused by not using just "apt full-upgrade"?
These questions from dpkg usually only get asked if you modified the file - did you do so? - do you remember why?
Thanks for reminding me to take a look into my config backup: Yes, I've modified /etc/default/zfs and /etc/zfs/zed.d/red.rc a long time ago. In /etc/default/zfs I've enabled

ZPOOL_IMPORT_PATH="/dev/disk/by-vdev:/dev/disk/by-id"

and in /etc/zfs/zed.d/red.rc I've enabled

ZED_EMAIL_OPTS="-s '@SUBJECT@' @ADDRESS@" ... ZED_NOTIFY_VERBOSE=1 ... ZED_NOTIFY_DATA=1

When I started to use Proxmox years I had some problems with my RAID (lost 2 HDDs). Maybe I wanted to have as much as information as possible in case of problems and made these changes.

from a very quick glance I don't think that the modification to the file are relevant - and that you should be safe to simply use the new version
However, like always when modifying system configuration:
Make sure you have a working and tested backup before proceeding

I hope this helps!

It did. I replaced all configs with the maintainers version and compared the content afterwards to set my custom settings again. Thank you very much!
 
  • Like
Reactions: Stoiko Ivanov
Okay, I will keep this in mind. So the first problem "The following packages have been kept back: zfs-initramfs zfs-zed zfsutils-linux" was caused by not using just "apt full-upgrade"?
That's what's the issue most of the times - so I'd assume that this is what happened on your system as well.
One other version is - if you've installed the zfs packages from stock-debian instead of the ones from the PVE repos it could also lead to similar issues - but that's more unlikely (and the fix would have been the same)

in any case -glad you fixed the issue :)
 
  • Like
Reactions: r4dh4l