luisfmrosa

Igor, really sorry, I didn't mean to be rude. This error with ZFS really put me out of my comfort zone! But thanks to this forum, all is solved now.

Hello, ==> UPDATE: I finally managed to fix the issue by moving away from current kernel and installing the edge one: on armbian-config, install "edge" kernel (5.17.5-meson64) install manually the kernel header (armbian-config only install "current" kernel header, i.e., 5.10.*): sudo apt install linux-headers-edge-meson64 sudo apt remove zfs-dkms sudo apt install zfs-dkms sudo apt install zfsutils-linux Then I managed to recover my zfs pool with: sudo zpool import -f mypool sudo zpool upgrade mypool Now it's working again! 🥰 It's me again. I have been busy since my last attempt to fix my ZFS issues, but now I found some time to start from zero: grabbed the latest version from https://redirect.armbian.com/odroidhc4/Jammy_current, installed on my SD card with Balena Etcher, and recreated my system from zero. I installed the kernel headers with armbian-config, as it was not activated by default, and then, I followed the same steps as described above in @Igor's post: Then started apt upgrade: While doing apt upgrade, I had 2 issues appeared, saying /etc/issue and /etc/issue.net were different from maintainers. I assume it's not a big deal, installed from the maintainer and continued: Then it continued the upgrade without noticeable issue: Then I tried to install zfs... and it doesn't work: sudo apt install zfs-dkms It starts by showing a message about licence incompatibility. I select 'OK' to continue... and then, it crashes! It says "Unable to build an empty module": What did I do wrong?! I would be grateful if someone could help me to solve it. All my NAS data is bricked. 🥵 I don't understand why it's so difficult to have ZFS running on my ODROID HC4 (but it worked in the past with an older version) ... this raises another question: shall I move away from ZFS for peace of mind? Thank you, guys! And sorry to bother you again. Luis

Hi, Sorry for the silly question: is there a way to move to Jammy straight from armbian-config? Or another simple way through ssh without a hard full reinstallation? Let me explain my issue first. This is my current situation: ___ _ _ _ _ _ ____ _ _ / _ \ __| |_ __ ___ (_) __| | | | | |/ ___| || | | | | |/ _` | '__/ _ \| |/ _` | | |_| | | | || |_ | |_| | (_| | | | (_) | | (_| | | _ | |___|__ _| \___/ \__,_|_| \___/|_|\__,_| |_| |_|\____| |_| Welcome to Armbian 21.02.3 Buster with Linux 5.17.5-meson64 System load: 5% Up time: 20 min Memory usage: 9% of 3.70G IP: 192.168.1.96 CPU temp: 47°C Usage of /: 5% of 58G [ General system configuration (beta): armbian-config ] Last login: Wed Jun 8 23:16:48 2022 from 192.168.1.86 root@odroidhc4:~# My issue: root@odroidhc4:~/sys-oled-hc4# apt install zfs-dkms zfsutils-linux Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: zfsutils-linux : Depends: libnvpair3linux (= 2.1.4-1~bpo11+1) but 2.0.3-9 is to be installed Depends: libuutil3linux (= 2.1.4-1~bpo11+1) but 2.0.3-9 is to be installed Depends: libzfs4linux (= 2.1.4-1~bpo11+1) but 2.0.3-9 is to be installed E: Unable to correct problems, you have held broken packages. This issue happened while upgrading my OMV5 to OMV6, when I suddenly realised for my dispair that I had lost zfs (and of course, my access to my disks). I was on stable version of kernel (5.10.102) and since then, I tried several things, like adding backports repository, without success. Then I moved to the current kernel version through armbian-config System / Other... ... so I assume that if I get to move to the same exact version as yours, it will work. But how? 🙂 Thank you for your help! NOTE: Just in case, thank you for the tips for the LCD: I had lost it on the migration, now working again.