Error after updates a zfs kernal

  • Today, I tried to update a zfs kernal (something, just one package). And errors appeared.


    First, the zfs plugin could not detect pools.


    Second, when I log out the Web GUI, I could not open the website anymore.


    Third, I try to reboot. After reboot, I found lots of services failed to start, including `rrdcached`, `openmediavault iptables firewall`, `chrony` and `chronyd`.


    Error message is like:


    1. rrdcached


    2. openmediavault iptables firewall

    3. chrony & chronyd‘s error could be solved with methods in here: Chronyd and Chrony services failed to start


    (1) Edit /etc/default/chrony and change DAEMON_OPTS="-F -1" to DAEMON_OPTS=""

    (2) Start chronyd systemctl start chronyd check status systemclt status chronyd


    But I'm not sure whether the error of chrony & chronyd would appear again in the next reboot.


    Any helps? Thanks a lot!


    By the way, when trying to update a package in OMV (in the update management section), it's a matter of life and death. Are there any safer way to do this?

  • Also, I found the omv-salt had been lost in OMV. I think there must be more potential problems after trying to update the zfs-kernal package. The zfs-kernal package was not update normally with lots of errors.

  • The openmediavault iptables firewall error could also been solved:


    1. Download the helper function from: https://github.com/openmediava…re/openmediavault/scripts


    2. Go to /usr/share/openmediavault/. Greate /share/. Put the helper-functions into the dir.


    3. Restart the openmediavault iptables firewall.


    Done.


    However, the web GUI of OMV could not been open, which means the existence of other problems.


    I notices that the omv-envr, omv-salt had been loss. I check packages related to omv:


    Code
    $ dpkg -l|grep -E "omv|openmediavault"
    
    rc  openmediavault                       5.6.8-1                             all          openmediavault - The open network attached storage solution
    ii  openmediavault-keyring               1.0                                 all          GnuPG archive keys of the OpenMediaVault archive
    rc  openmediavault-lvm2                  5.0.2-1                             all          openmediavault Logical Volume Manager (LVM2) plugin
    rc  openmediavault-omvextrasorg          5.6                                 all          OMV-Extras.org Package Repositories for OpenMediaVault
    rc  openmediavault-zfs                   5.0.6                               amd64        OpenMediaVault plugin for ZFS


    I think reinstall these packages might help.


    Any suggestions?

  • Surprisingly, I finally deal with the problems by myself. And...


    My OMV upgrade from 5.x to 6.x...


    Here are the processes:


    1. sudo apt-get update


    2. sudo apt-get -y upgrade


    3. if needed, load sudo apt-get -y upgrade --fix-missing # debian


    4. sudo apt-get dist-upgrade # omv


    5. According to (Error salt), wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash


    6. sudo reboot


    Sometimes, there were some errors happening. Just repeated them and reboot.


    One of annoying error is proftpd dependency. According to https://bugs.launchpad.net/ubu…proftpd-dfsg/+bug/1933318, you can try


    (1) sudo apt-get remove proftpd*

    (2) sudo apt-get purge proftpd*

    (3) sudo apt-get install proftpd*

    (4) sudo service proftpd start


    Anyway, finally, You can check:


    Code
    $ dpkg -l | grep openmediavault
    
    ii  openmediavault                       6.0.7-1                         all          openmediavault - The open network attached storage solution
    ii  openmediavault-keyring               1.0                             all          GnuPG archive keys of the OpenMediaVault archive
    rc  openmediavault-lvm2                  5.0.2-1                         all          openmediavault Logical Volume Manager (LVM2) plugin
    rc  openmediavault-omvextrasorg          5.6                             all          OMV-Extras.org Package Repositories for OpenMediaVault
    rc  openmediavault-zfs                   5.0.6                           amd64        OpenMediaVault plugin for ZFS


    If you meet GUI login problem: 500-Internal Server Error Failed to connect to socket: No such file or directory. According to OMV GUI Login Error: Failed to connect to socket: No such file or directory, just try

    Code
    systemctl status openmediavault-engined 
    systemctl unmask openmediavault-engined # if the statu is masked, just unmask it
    systemctl start openmediavault-engined

    Succed.


    Very hard.


    Also, here is a tip: upgrade pakage by using sudo apt-get dist-upgrade instead of doing it in the GUI.

  • Succed.

    rc openmediavault-lvm2 5.0.2-1 all openmediavault Logical Volume Manager (LVM2) plugin
    rc openmediavault-omvextrasorg 5.6 all OMV-Extras.org Package Repositories for OpenMediaVault
    rc openmediavault-zfs 5.0.6

    Are you sure it is fully updated???

  • Thanks for reminding. Soma  macom


    The original reason for me to upgrade packages is to fix problems of login instead of upgrading to OMV 6.x. But now the login is normal, so I think it doesn't matter whether the 5.x or 6.x was installed.


    Now I had enter the new GUI, whose appearance is very different from OMV 5.x. After reboot, the OMV had nothing change, which showed that the version in my NAS is stable. However, check the version of OMV:



    Code
    $ cat /etc/issue
    
    openmediavault 6.0.7-1 (Shaitan) \n \l
    Copyright (C) 2009-2022 by Volker Theile. All rights reserved.
    ...
    
    $ uname -a
    Linux openmediavault 5.4.157-1-pve #1 SMP PVE 5.4.157-1 (Mon, 29 Nov 2021 12:01:44 +0100) x86_64 GNU/Linux

    emm...Very interesting.


    Does it matter?

  • The kernel version has nothing to do with the OMV version (or Debian, for that matter)

    Kernel is on v5 and will be for a LOOOONNNGGG time.


    What matter's is, you managed to update OMV to v6 (as seen on you previous posts) but the omv-extras and (subsequentially) your plugins are still on v5.


    This means that your update/upgrade isn't fully complete.


    [EDIT]

    Search the forum with "omv-release-upgrade" (include the aspas)

    [/EDIT]

  • macom

    Added the Label resolved
  • macom

    Set the Label from OMV 5.x to OMV 6.x (RC1)
  • macom

    Added the Label Upgrade 5.x -> 6.x

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!