ZFS on Helios64


grek
 Share

11 11

Recommended Posts

The services you have to enable are  zfs-import-cache, zsf-import.target, zfs-mount, zfs.target, and zfs-zed. You don't have to unmask anything. Just enable those and it'll work.

 

25 minutes ago, SIGSEGV said:

 

Were you able to make a deb package with the kmod?? The dmks is nice, but a kernel module to match the Armbian release would probably be better for end users.

Yup. If you build using deb-kmod instead of deb-dkms, it'll build the kmod. That's what I did.

Link to post
Share on other sites

Donate and support the project!

2 minutes ago, Demodude123 said:

zfs-2.0.0.tar.gz
zfs-kmod-2.0.0-rc5.src.rpm
kmod-zfs-5.8.14-rockchip64_2.0.0-0_arm64.deb
kmod-zfs-devel_2.0.0-0_arm64.deb
kmod-zfs-devel-5.8.14-rockchip64_2.0.0-0_arm64.deb
zfs-dkms-2.0.0-rc5.src.rpm
zfs-dkms_2.0.0-0_arm64.deb
zfs-2.0.0-rc5.src.rpm
zfs_2.0.0-0_arm64.deb
libnvpair1_2.0.0-0_arm64.deb
libuutil1_2.0.0-0_arm64.deb
libzfs2_2.0.0-0_arm64.deb
libzpool2_2.0.0-0_arm64.deb
libzfs2-devel_2.0.0-0_arm64.deb
zfs-test_2.0.0-0_arm64.deb
zfs-dracut_2.0.0-0_arm64.deb
zfs-initramfs_2.0.0-0_arm64.deb
python3-pyzfs_2.0.0-0_arm64.deb

Here's what it built for me

The only ones really needed to make it work are the libs, either zfs-dkms or kmod-zfs, zfs, zfs-initramfs, and python3-pyzfs. The others are optional.

Link to post
Share on other sites

8 hours ago, SIGSEGV said:

 what would your thoughts be on this matter? I'm aware that not all armbian supported hardware might benefit from it since not all are used for storage purposes, but those that are could have a new option for the filesystem.


There are tho paths - currently build with 0.5.8. but the same goes for 2.0.

https://github.com/armbian/build/pull/2410 (works automagically, slow to build, overhead)

https://github.com/armbian/build/pull/2414 (need a bit more attention and help to put it together but its better solution)

Link to post
Share on other sites

8 hours ago, Igor said:

2.0

 

Something else I totally forgot about in my long rant on page 1 (until TonyMac32 reminded me in IRC) is that it's going to be some time before upstream Debian ship ZFS 2.0.

 

This has nothing to do with Armbian, and is a subject of long debate around Debian itself.  I will spare you guys another wall of text so long as no one says something along the lines of "Debian is slow/behind" etc.  :D

Link to post
Share on other sites

On 12/4/2020 at 7:05 PM, Igor said:


There are tho paths - currently build with 0.5.8. but the same goes for 2.0.

https://github.com/armbian/build/pull/2410 (works automagically, slow to build, overhead)

https://github.com/armbian/build/pull/2414 (need a bit more attention and help to put it together but its better solution)

Hi Igor, 


I have been going down this path for the Helios and it is a pain. I am the type of user who knows enough about linux to need to reinstall :)

 

Are you able to suggest actually putting this into practice? Is it as simple as editing the various files listed in the repos here? if you update won't this be overwritten?

Link to post
Share on other sites

@scottf007,

 

Igor's comment was more directed at the others in the thread who are trying to solve this particular bugbear.  In other words, mostly development talk.

 

There are lots of clues and instructions littered throughout these forums that will tell you how to get this working.  However if you get too frustrated or can't figure it out, just wait a bit longer and eventually something will be released to make this "easier" for the average Joe.

Link to post
Share on other sites

Hey,

Do You using compression on Your ZFS datastore ? 

Yesterday I wanted to do some cleanup (Previously i have only pool created and all directories were there) ,I created new datastore for each 'directory' like home, docker-data etc. 

Also I setup them with ACL support and compression:

zfs set aclinherit=passthrough data/docker-data
zfs set acltype=posixacl data/docker-data
zfs set xattr=sa data/docker-data
zfs set compression=lz4 data/docker-data


I successfully moved 3 directories (about 300 GB each) from main 'data' datastore to 'data'/something . 

The load was quite big and write speed about 40 - 55 MB/s . ( ZFS Mirror - 2x 4TB hdd ) 

When I tried with another (directory to new datastore) I got kernel panic. I faced this problem twice yesterday. Finally I disabled compression on the rest datastories 

 

kernel:  5.9.11 

 

Dec 14 22:46:36 localhost kernel: [  469.592940] Modules linked in: quota_v2 quota_tree dm_crypt algif_skcipher af_alg dm_mod softdog governor_performance r8152 snd_soc_hdmi_codec pwm_fan gpio_charger leds_pwm snd_soc_rockchip_i2s snd_soc_core rockchip_vdec(C) snd_pcm_dmaengine snd_pcm hantro_vpu(C) rockchip_rga v4l2_h264 snd_timer fusb302 videobuf2_dma_contig rockchipdrm snd videobuf2_dma_sg dw_mipi_dsi v4l2_mem2mem videobuf2_vmalloc dw_hdmi soundcore videobuf2_memops tcpm analogix_dp panfrost videobuf2_v4l2 gpu_sched typec videobuf2_common drm_kms_helper cec videodev rc_core mc sg drm drm_panel_orientation_quirks cpufreq_dt gpio_beeper zfs(POE) zunicode(POE) zzstd(OE) zlua(OE) nfsd auth_rpcgss nfs_acl lockd grace zcommon(POE) znvpair(POE) zavl(POE) icp(POE) spl(OE) sunrpc lm75 ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear md_mod realtek dwmac_rk stmmac_platform stmmac mdio_xpcs adc_keys
Dec 14 22:46:36 localhost kernel: [  469.600200] CPU: 5 PID: 5769 Comm: z_wr_iss Tainted: P         C OE     5.9.11-rockchip64 #20.11.1
Dec 14 22:46:36 localhost kernel: [  469.600982] Hardware name: Helios64 (DT)
Dec 14 22:46:36 localhost kernel: [  469.601328] pstate: 20000005 (nzCv daif -PAN -UAO BTYPE=--)
Dec 14 22:46:36 localhost kernel: [  469.601942] pc : lz4_compress_zfs+0xfc/0x7d0 [zfs]
Dec 14 22:46:36 localhost kernel: [  469.602367] lr : 0x11be8
Dec 14 22:46:36 localhost kernel: [  469.602591] sp : ffff80001434bbd0
Dec 14 22:46:36 localhost kernel: [  469.602882] x29: ffff80001434bbd0 x28: ffff0000af99cf80 
Dec 14 22:46:36 localhost kernel: [  469.603349] x27: 00000000000000ff x26: ffff000064adaca8 
Dec 14 22:46:36 localhost kernel: [  469.603815] x25: ffff800022378be8 x24: ffff800012855004 
Dec 14 22:46:36 localhost kernel: [  469.604280] x23: ffff0000a04c4000 x22: ffff8000095c0000 
Dec 14 22:46:36 localhost kernel: [  469.604746] x21: ffff800012855000 x20: 0000000000020000 
Dec 14 22:46:36 localhost kernel: [  469.605212] x19: ffff800022367000 x18: 000000005b5eaa7e 
Dec 14 22:46:36 localhost kernel: [  469.605677] x17: 00000000fffffff0 x16: ffff800022386ff8 
Dec 14 22:46:36 localhost kernel: [  469.606143] x15: ffff800022386ffa x14: ffff800022386ffb 
Dec 14 22:46:36 localhost kernel: [  469.606609] x13: 00000000ffffffff x12: ffffffffffff0001 
Dec 14 22:46:36 localhost kernel: [  469.607075] x11: ffff800012867a81 x10: 000000009e3779b1 
Dec 14 22:46:36 localhost kernel: [  469.607540] x9 : ffff80002236a2f2 x8 : ffff80002237a2f9 
Dec 14 22:46:36 localhost kernel: [  469.608006] x7 : ffff800012871000 x6 : ffff800022387000 
Dec 14 22:46:36 localhost kernel: [  469.608472] x5 : ffff800022386ff4 x4 : ffff80002237a301 
Dec 14 22:46:36 localhost kernel: [  469.608937] x3 : 0000000000000239 x2 : ffff80002237a2f1 
Dec 14 22:46:36 localhost kernel: [  469.609402] x1 : ffff800022379a3b x0 : 00000000000005b5 
Dec 14 22:46:36 localhost kernel: [  469.609870] Call trace:
Dec 14 22:46:36 localhost kernel: [  469.610234]  lz4_compress_zfs+0xfc/0x7d0 [zfs]
Dec 14 22:46:36 localhost kernel: [  469.610737]  zio_compress_data+0xc0/0x13c [zfs]
Dec 14 22:46:36 localhost kernel: [  469.611243]  zio_write_compress+0x294/0x6d0 [zfs]
Dec 14 22:46:36 localhost kernel: [  469.611764]  zio_execute+0xa4/0x144 [zfs]
Dec 14 22:46:36 localhost kernel: [  469.612137]  taskq_thread+0x278/0x450 [spl]
Dec 14 22:46:36 localhost kernel: [  469.612517]  kthread+0x118/0x150
Dec 14 22:46:36 localhost kernel: [  469.612804]  ret_from_fork+0x10/0x34
Dec 14 22:46:36 localhost kernel: [  469.613660] ---[ end trace 34e3e71ff3a20382 ]---

 

Link to post
Share on other sites

Hello folks.

I received my Helios64 some days ago.
I was able to build zfs 2.0.0 with the script from @grek with the 5.9.14 release. However, the docker env built the kmod for 5.9.11 and I cannot find the 5.9.14 headers in the repos...
I can rebuild at will but where are the header package?

 

Link to post
Share on other sites

@grek I've been using compression since the get-go, and can't say I've had similar issues so far. The only time I had a kernel panic was from before I switched to the performance governor for the CPU. LZ4 is also a pretty light-weight compression algorithm, but it does increase CPU to a small degree.

 

Potential changes I have compared to your setup:

  • I run root (/) on ZFS
  • I use full disk encryption via LUKS (that's an additional layer between ZFS and kernel)
  • I use the performance governor
  • My disks are limited to 3.0 Gbps SATA speed

Things you could try:

  • Upgrade to the latest 5.9.14-rockchip64 kernel
  • Upgrade to the latest ZFS 0.8.6 kernel modules
  • Try the performance governor
  • Do you use a swap partition? If yes, you could try to swapoff before repeating the process that paniced the kernel
  • Wildcard idea: You could also try disabling the Armbian zram config in /etc/default/armbian-zram-config (I have it disabled)
Edited by ShadowDance
Accidentally wrote LZ4 is an encryption algorithm, corrected to compression
Link to post
Share on other sites

@tionebrr I have built it from this script yesterday without any issue.

I only changed a line with make deb to make deb-kmod to create only kmod package (it was needed for me after kernel upgrade)

 

cd "/scratch/$zfsver-$(uname -r)"
sh autogen.sh
./configure
make -s -j$(nproc)
make deb-kmod
mkdir "/scratch/deb-$zfsver-$(uname -r)"
cp *.deb "/scratch/deb-$zfsver-$(uname -r)"
rm -rf  "/scratch/$zfsver-$(uname -r)"
exit
EOF


If you have a trouble pls pm me, i can send you this deb package.  (mine is: kmod-zfs-5.9.14-rockchip64_2.0.0-1_arm64.deb )  , I have changed zfsver  git to 2.0.0 instead of zfsver="zfs-2.0.0-rc6"

 

Also i hashed all cleanup section, and i installed ZFS from official repo and im using only kmod installed manually. In other way I had a problem with OMV :/

root@helios64:~# zfs version
zfs-0.8.5-3~bpo10+1
zfs-kmod-2.0.0-1
root@helios64:~# 

 

root@helios64:~# dpkg -l |grep zfs
ii  kmod-zfs-5.9.10-rockchip64           2.0.0-0                             arm64        zfs kernel module(s) for 5.9.10-rockchip64
ii  kmod-zfs-5.9.11-rockchip64           2.0.0-1                             arm64        zfs kernel module(s) for 5.9.11-rockchip64
ii  kmod-zfs-5.9.14-rockchip64           2.0.0-1                             arm64        zfs kernel module(s) for 5.9.14-rockchip64
ii  libzfs2linux                         0.8.5-3~bpo10+1                     arm64        OpenZFS filesystem library for Linux
ii  openmediavault-zfs                   5.0.5                               arm64        OpenMediaVault plugin for ZFS
ii  zfs-auto-snapshot                    1.2.4-2                             all          ZFS automatic snapshot service
iF  zfs-dkms                             0.8.5-3~bpo10+1                     all          OpenZFS filesystem kernel modules for Linux
ii  zfs-dkms-dummy                       0.8.4                               all          Dummy zfs-dkms package for when using built kmod
ii  zfs-zed                              0.8.5-3~bpo10+1                     arm64        OpenZFS Event Daemon
ii  zfsutils-linux                       0.8.5-3~bpo10+1                     arm64        command-line tools to manage OpenZFS filesystems
root@helios64:~# 

 

 

@ShadowDance

I forgot to mention that on the top i have full encryption with LUKS. like You :)

yesterday i upgraded OS to Armbian 20.11.3 and kernel to Linux helios64 5.9.14-rockchip64

I posted what version I have. I wanted to have ZFS with OMV and this solution is somehow working for me. If i used all packages from manual build i wasn't force omv zfs plugin to work :/ 

My swap is off

I will change something in the settings if I will face the problem again. currently i finished copy my data and everything is working as desired. 

 

 

 

Link to post
Share on other sites

@grek
Hey thanks a lot. I found what the issue was finally. The -current- headers were still the 5.9.11 in the repos until recently; but the latest download from kobol was already packaged with the 5.9.14 kernel. So modprobe couldn't find the 9.14 kmod for zfs after the build.
I'm not experienced enough to know what might be the downsides of using 2.0.0 and getting out of trouble (if any). I finally built ZFS from the DKMS and will stick to that for now.
Thanks for the help :)

Link to post
Share on other sites

Hi! I successfully setup ZFS of Armbian Helios64 along with OMV, using almost standard procedure. Using latest software (Linux helios64 5.9.14-rockchip64 #20.11.4 SMP PREEMPT Tue Dec 15 08:52:20 CET 2020 aarch64 GNU/Linux)

BUT I cannot turn on the plugin (openmediavault-zfs) to use zfs from OMV. That package simply doesn't exist, because Arm platform officially unsupported by OMV team.

Can you help me?

Edited by Дмитрий Самородкин
Link to post
Share on other sites

11 hours ago, Дмитрий Самородкин said:

BUT I cannot turn on the plugin (openmediavault-zfs) to use zfs from OMV. That package simply doesn't exist, because Arm platform officially unsupported by OMV team.

 

This is more a question to ask on openmediavault forum.

Link to post
Share on other sites

ZFS was just upgraded to v2.0.1 https://armbian.atlassian.net/browse/AR-614 which is a preparation for pushing a kernel on and above 5.10.y. Upgrade was tested on Armbian Buster/Bullseye/Focal/Hirsute. My test ZPOOL was always loaded without any troubles.

We only support upgrade troubles - for ZFS functional problems, please check / file a bug report here https://github.com/openzfs/zfs/issues

 

Link to post
Share on other sites

It looks like the latest update Linux helios64 5.10.12-rockchip64 #21.02.1  broke ZFS dkms 

 

After the reboot zfs kernel module is missing...

Probably I have to build it manually again :(

 

Quote

root@helios64:/# uname -a
Linux helios64 5.10.12-rockchip64 #21.02.1 SMP PREEMPT Wed Feb 3 20:55:02 CET 2021 aarch64 GNU/Linux
root@helios64:/# zfs --version
zfs-2.0.1-1
zfs_version_kernel() failed: No such file or directory
 

 

 

Quote

root@helios64:/# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  dkms
Use 'apt autoremove' to remove it.
The following packages will be upgraded:
  armbian-config armbian-firmware base-files device-tree-compiler file iproute2 libcairo2 libgnutls30 libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libsystemd0
  libudev1 linux-buster-root-current-helios64 linux-dtb-current-rockchip64 linux-headers-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-helios64-current
  systemd systemd-sysv udev unzip
23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 68.4 MB of archives.
After this operation, 8992 kB disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian buster/main arm64 base-files arm64 10.3+deb10u8 [69.9 kB]
Get:2 http://deb.debian.org/debian buster/main arm64 systemd-sysv arm64 241-7~deb10u6 [100 kB]
Get:3 http://deb.debian.org/debian buster/main arm64 libpam-systemd arm64 241-7~deb10u6 [201 kB]
Get:4 http://deb.debian.org/debian buster/main arm64 libsystemd0 arm64 241-7~deb10u6 [314 kB]
Get:5 http://deb.debian.org/debian buster/main arm64 libnss-myhostname arm64 241-7~deb10u6 [122 kB]
Get:6 http://deb.debian.org/debian buster/main arm64 systemd arm64 241-7~deb10u6 [3258 kB]
Get:7 http://deb.debian.org/debian buster/main arm64 udev arm64 241-7~deb10u6 [1245 kB]
Get:8 http://deb.debian.org/debian buster/main arm64 libudev1 arm64 241-7~deb10u6 [146 kB]
Get:9 http://deb.debian.org/debian buster/main arm64 libgnutls30 arm64 3.6.7-4+deb10u6 [1062 kB]
Get:10 http://deb.debian.org/debian buster/main arm64 iproute2 arm64 4.20.0-2+deb10u1 [805 kB]
Get:11 http://deb.debian.org/debian buster/main arm64 file arm64 1:5.35-4+deb10u2 [66.5 kB]
Get:12 http://deb.debian.org/debian buster/main arm64 libmagic1 arm64 1:5.35-4+deb10u2 [115 kB]
Get:13 http://deb.debian.org/debian buster/main arm64 libmagic-mgc arm64 1:5.35-4+deb10u2 [242 kB]
Get:14 http://deb.debian.org/debian buster/main arm64 unzip arm64 6.0-23+deb10u2 [166 kB]
Get:15 http://deb.debian.org/debian buster/main arm64 device-tree-compiler arm64 1.4.7-4 [251 kB]
Get:16 http://deb.debian.org/debian buster/main arm64 libcairo2 arm64 1.16.0-4+deb10u1 [644 kB]
Get:17 https://imola.armbian.com/apt buster/main arm64 armbian-config all 21.02.1 [44.8 kB]
Get:18 https://mirrors.netix.net/armbian/apt buster/main arm64 armbian-firmware all 21.02.1 [6922 kB]
Get:19 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 linux-buster-root-current-helios64 arm64 21.02.1 [416 kB]
Get:21 https://imola.armbian.com/apt buster/main arm64 linux-headers-current-rockchip64 arm64 21.02.1 [11.5 MB]
Get:20 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 linux-dtb-current-rockchip64 arm64 21.02.1 [311 kB]
Get:23 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 linux-u-boot-helios64-current arm64 21.02.1 [478 kB]
Get:22 https://mirrors.netix.net/armbian/apt buster/main arm64 linux-image-current-rockchip64 arm64 21.02.1 [39.9 MB]
Fetched 68.4 MB in 5s (13.7 MB/s)
Preconfiguring packages ...
(Reading database ... 102529 files and directories currently installed.)
Preparing to unpack .../base-files_10.3+deb10u8_arm64.deb ...
Unpacking base-files (10.3+deb10u8) over (10.3+deb10u7) ...
Setting up base-files (10.3+deb10u8) ...
Installing new version of config file /etc/debian_version ...
(Reading database ... 102529 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_241-7~deb10u6_arm64.deb ...
Unpacking systemd-sysv (241-7~deb10u6) over (241-7~deb10u5) ...
Preparing to unpack .../libpam-systemd_241-7~deb10u6_arm64.deb ...
Unpacking libpam-systemd:arm64 (241-7~deb10u6) over (241-7~deb10u5) ...
Preparing to unpack .../libsystemd0_241-7~deb10u6_arm64.deb ...
Unpacking libsystemd0:arm64 (241-7~deb10u6) over (241-7~deb10u5) ...
Setting up libsystemd0:arm64 (241-7~deb10u6) ...
(Reading database ... 102529 files and directories currently installed.)
Preparing to unpack .../libnss-myhostname_241-7~deb10u6_arm64.deb ...
Unpacking libnss-myhostname:arm64 (241-7~deb10u6) over (241-7~deb10u5) ...
Preparing to unpack .../systemd_241-7~deb10u6_arm64.deb ...
Unpacking systemd (241-7~deb10u6) over (241-7~deb10u5) ...
Preparing to unpack .../udev_241-7~deb10u6_arm64.deb ...
Unpacking udev (241-7~deb10u6) over (241-7~deb10u5) ...
Preparing to unpack .../libudev1_241-7~deb10u6_arm64.deb ...
Unpacking libudev1:arm64 (241-7~deb10u6) over (241-7~deb10u5) ...
Setting up libudev1:arm64 (241-7~deb10u6) ...
(Reading database ... 102529 files and directories currently installed.)
Preparing to unpack .../libgnutls30_3.6.7-4+deb10u6_arm64.deb ...
Unpacking libgnutls30:arm64 (3.6.7-4+deb10u6) over (3.6.7-4+deb10u5) ...
Setting up libgnutls30:arm64 (3.6.7-4+deb10u6) ...
(Reading database ... 102529 files and directories currently installed.)
Preparing to unpack .../00-iproute2_4.20.0-2+deb10u1_arm64.deb ...
Unpacking iproute2 (4.20.0-2+deb10u1) over (4.20.0-2) ...
Preparing to unpack .../01-file_1%3a5.35-4+deb10u2_arm64.deb ...
Unpacking file (1:5.35-4+deb10u2) over (1:5.35-4+deb10u1) ...
Preparing to unpack .../02-libmagic1_1%3a5.35-4+deb10u2_arm64.deb ...
Unpacking libmagic1:arm64 (1:5.35-4+deb10u2) over (1:5.35-4+deb10u1) ...
Preparing to unpack .../03-libmagic-mgc_1%3a5.35-4+deb10u2_arm64.deb ...
Unpacking libmagic-mgc (1:5.35-4+deb10u2) over (1:5.35-4+deb10u1) ...
Preparing to unpack .../04-unzip_6.0-23+deb10u2_arm64.deb ...
Unpacking unzip (6.0-23+deb10u2) over (6.0-23+deb10u1) ...
Preparing to unpack .../05-armbian-config_21.02.1_all.deb ...
Unpacking armbian-config (21.02.1) over (20.11.6) ...
Preparing to unpack .../06-armbian-firmware_21.02.1_all.deb ...
Unpacking armbian-firmware (21.02.1) over (20.11.3) ...
Preparing to unpack .../07-device-tree-compiler_1.4.7-4_arm64.deb ...
Unpacking device-tree-compiler (1.4.7-4) over (1.4.7-3) ...
Preparing to unpack .../08-libcairo2_1.16.0-4+deb10u1_arm64.deb ...
Unpacking libcairo2:arm64 (1.16.0-4+deb10u1) over (1.16.0-4) ...
Preparing to unpack .../09-linux-buster-root-current-helios64_21.02.1_arm64.deb ...
Unpacking linux-buster-root-current-helios64 (21.02.1) over (20.11.6) ...
Preparing to unpack .../10-linux-dtb-current-rockchip64_21.02.1_arm64.deb ...
Unpacking linux-dtb-current-rockchip64 (21.02.1) over (20.11.4) ...
Preparing to unpack .../11-linux-headers-current-rockchip64_21.02.1_arm64.deb ...
Unpacking linux-headers-current-rockchip64 (21.02.1) over (20.11.4) ...
Preparing to unpack .../12-linux-image-current-rockchip64_21.02.1_arm64.deb ...
dkms: removing: zfs 2.0.1 (5.9.14-rockchip64) (aarch64)

-------- Uninstall Beginning --------
Module:  zfs
Version: 2.0.1
Kernel:  5.9.14-rockchip64 (aarch64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

zavl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


znvpair.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


zunicode.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


zcommon.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/updates/dkms/
rmdir: failed to remove 'updates/dkms': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


zfs.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/updates/dkms/
rmdir: failed to remove 'updates/dkms': Directory not empty
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


icp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


zlua.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


spl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


zzstd.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.9.14-rockchip64/
rmdir: failed to remove '': No such file or directory
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall completed.
update-initramfs: Deleting /boot/initrd.img-5.9.14-rockchip64
Removing obsolete file uInitrd-5.9.14-rockchip64
Unpacking linux-image-current-rockchip64 (21.02.1) over (20.11.4) ...
Preparing to unpack .../13-linux-u-boot-helios64-current_21.02.1_arm64.deb ...
Unpacking linux-u-boot-helios64-current (21.02.1) over (20.11.6) ...
Setting up linux-u-boot-helios64-current (21.02.1) ...
Setting up libmagic-mgc (1:5.35-4+deb10u2) ...
Setting up iproute2 (4.20.0-2+deb10u1) ...
Setting up unzip (6.0-23+deb10u2) ...
Setting up linux-image-current-rockchip64 (21.02.1) ...
configure: error:
        *** Unable to build an empty module.

Error! Bad return status for module build on kernel: 5.10.12-rockchip64 (aarch64)
Consult /var/lib/dkms/zfs/2.0.1/build/make.log for more information.
update-initramfs: Generating /boot/initrd.img-5.10.12-rockchip64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
update-initramfs: Converting to u-boot format
Setting up libmagic1:arm64 (1:5.35-4+deb10u2) ...
Setting up linux-buster-root-current-helios64 (21.02.1) ...
Setting up systemd (241-7~deb10u6) ...
Setting up file (1:5.35-4+deb10u2) ...
Setting up libcairo2:arm64 (1.16.0-4+deb10u1) ...
Setting up armbian-config (21.02.1) ...
Setting up linux-dtb-current-rockchip64 (21.02.1) ...
Setting up udev (241-7~deb10u6) ...
update-initramfs: deferring update (trigger activated)
Setting up libnss-myhostname:arm64 (241-7~deb10u6) ...
Setting up device-tree-compiler (1.4.7-4) ...
Setting up armbian-firmware (21.02.1) ...
Setting up linux-headers-current-rockchip64 (21.02.1) ...
Compiling headers - please wait ...
Setting up systemd-sysv (241-7~deb10u6) ...
Setting up libpam-systemd:arm64 (241-7~deb10u6) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.10.12-rockchip64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
    nor crypto modules. If that's on purpose, you may want to uninstall the
    'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
    integration and avoid this warning.
update-initramfs: Converting to u-boot format
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for cracklib-runtime (2.9.6-2) ...
Processing triggers for dbus (1.12.20-0+deb10u1) ...
Processing triggers for mime-support (3.62) ...
 

 

Link to post
Share on other sites

Thx @FloBaoti 

I had to remove openmediavault-zfs first....

 

Quote

apt remove openmediavault-zfs

apt remove dkms zfs-dkms

apt install dkms zfs-dkms

apt install openmediavault-zfs

 

 

root@helios64:/# zfs --version
zfs-2.0.1-1
zfs-kmod-2.0.1-1
root@helios64:/# uname -a
Linux helios64 5.10.12-rockchip64 #21.02.1 SMP PREEMPT Wed Feb 3 20:55:02 CET 2021 aarch64 GNU/Linux
root@helios64:/#
 

Now i have working ZFS again ;)

Link to post
Share on other sites

I don't understand, I have ZFS 2.0.1 on 5.10.16-rockchip64 :

 

root@helios64:~# uname -a
Linux helios64 5.10.16-rockchip64 #21.02.2 SMP PREEMPT Sun Feb 14 21:35:01 CET 2021 aarch64 GNU/Linux
root@helios64:~# zfs version
zfs-2.0.1-1
zfs-kmod-2.0.1-1

 

I just add to reinstall zfs-dkms (apt install --reinstall zfs-dkms) because it failed during upgrade.

Link to post
Share on other sites

5 hours ago, FloBaoti said:

I don't understand, I have ZFS 2.0.1 on 5.10.16-rockchip64

 

Armbian works. I am just bragging / saying that this doesn't go smoothly even on mainstream Linux distros. It doesn't work on Debian or Ubuntu, dunno for others. 

 

https://docs.armbian.com/#what-is-the-difference-between-armbian-and-debianubuntu

 

In case someone wants to use DEV kernel 5.11.y, it also builds:

 

modinfo zfs
filename:       /lib/modules/5.11.0-rockchip64/updates/dkms/zfs.ko
version:        2.0.1-1
license:        CDDL
author:         OpenZFS
description:    ZFS
alias:          devname:zfs
alias:          char-major-10-249
srcversion:     EAE2DB6FB7D7D7B1D4D10B6
depends:        spl,znvpair,icp,zlua,zzstd,zunicode,zcommon,zavl
name:           zfs
vermagic:       5.11.0-rockchip64 SMP preempt mod_unload aarch64

 

Link to post
Share on other sites

 Share

11 11