• Content Count

  • Joined

  • Last visited

About SvenHz

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. And I'm back, and back to square one. After 3 months of enjoying ZFS 0.7.13 on Helios4, I noticed that 0.8.2 was available in the backports. So, after doing apt-get update, I did apt-get upgrade and lost my ZFS. Basically I have spent the whole afternoon on this and I am fully stuck. If I use apt-get to try and reinstall ZFS, I end up with the "configure: error: *** Unable to build an empty module." If I manually use dkms to build the ZFS 0.8.2 from the sources left around by apt-get, I get a successful build, however "mobprobe zfs" gives me a Exec Format Error. dmesg shows: zlua: section 4 reloc 44 sym 'longjmp': unsupported interworking call (Thumb -> ARM) Does anyone have 0.8.2 succesfully running on Helios4? Update. If I remove the 90_zfs apt preference file, I can try to install 0.7.12. However that also breaks (luckily a lot faster so I can debug). The problem seems to be that my dkms is now broken. # more /var/lib/dkms/spl/0.7.12/build/make.log DKMS make.log for spl-0.7.12 for kernel 4.19.63-mvebu (armv7l) Sun Dec 22 22:32:42 CET 2019 make: *** No targets specified and no makefile found. Stop. Relevant bits from /var/lib/dkms/spl/0.7.12/build/config.log: configure:9294: cp conftest.c build && make modules -C /lib/modules/4.19.63-mvebu/build EXTRA_CFLAGS=-Werror-implicit-function-declaration M=/var/lib/dkms/spl/0.7.12/build/build Makefile:613: arch//Makefile: No such file or directory make: *** No rule to make target 'arch//Makefile'. Stop. I found and patched my common.postinst file. I have now been successful with 0.7.12 and have re-imported my pool. All seems fine. I would love to try 0.8.2 as soon as someone confirms that it works :-)
  2. @gprovost many thanks for sharing your full log. I have it working!!! I kept not doing an "apt-get upgrade" before doing the "apt-get update". On a clean image (dated 2 Aug 2019 on Kobol website) I can confirm I have successfully built the ZFS stuff, taking the above steps into account.
  3. Exactly the same issue with the image from Armbian ( downloaded yesterday) which was a few MBs different from the Kobol image. The problem is in the configure step of spl-dkms.
  4. @gprovost what image are you using exactly? I am using the ones from and still have the same issue, see transcript below. This is Armbian_5.91_Helios4_Debian_buster_next_4.19.63.7z from dated Aug 2, 2019.
  5. Unfortunately, on the Kobol supplied image Armbian_5.91_Helios4_Debian_stretch_default_4.14.135.7z, I get exactly the same problem: (clean install) root@helios4:~# apt-get install linux-headers-mvebu > works, headers for 4.14 root@helios4:~# apt-get install spl-dkms [...snip...] Loading new spl-0.7.12 DKMS files... Building for 4.14.135-mvebu Building initial module for 4.14.135-mvebu configure: error: *** Unable to build an empty module. Error! Bad return status for module build on kernel: 4.14.135-mvebu (armv7l) Consult /var/lib/dkms/spl/0.7.12/build/make.log for more information. root@helios4:~# I will try @gprovost 's steps now, just missed it, many thanks for sharing!
  6. @qstaq wow. I will try the Debian 9 Stretch 4.14 image (from tomorrow in the mean time (with backports) and will report here.
  7. Even with a clean image (downloaded from dated August 2nd) I still get the error in spl-dkms. Steps to reproduce: start with image #apt-get update #apt-get upgrade edit 90_zfs for backports #apt-get install linux-headers-next-mvebu #apt-get install spl-dkms > same error # more /var/lib/dkms/spl/0.7.13/build/make.log DKMS make.log for spl-0.7.13 for kernel 4.19.63-mvebu (armv7l) Tue Sep 10 14:52:48 UTC 2019 make: *** No targets specified and no makefile found. Stop. #
  8. Can't get it to work. I am starting with a fresh image and will report tonight.
  9. I am still stuck with spl-dkms. I am now on backports. #apt-get install -t buster-backports spl-dkms Loading new spl-0.7.13 DKMS files... Building for 4.19.63-mvebu Building initial module for 4.19.63-mvebu configure: error: *** Unable to build an empty module. Error! Bad return status for module build on kernel: 4.19.63-mvebu (armv7l) Consult /var/lib/dkms/spl/0.7.13/build/make.log for more information. dpkg: error processing package spl-dkms (--configure): installed spl-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: spl-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) Interestingly, at that point, I can successfully do a manual "dkms build spl/0.7.13" and "dkms install spl/0.7.13"...!! However if I then do "apt-get install zfs-dkms", it decides to de-install spl-dkms, reinstall it, and fail with the above error :-) Any ideas at this point? :-)
  10. Thank you all for chiming in. And yes my requirements are modest: 2x 3TB in mirror, no dedup. I got a bit further but the DKMS part is failing, any suggestions? EDIT: it looks like this is a common error, found some info elsewhere, still working on this...
  11. I am aware of the memory “challenge” but my sizing is modest, so thank you for the warning but I will handle that just fine. Anyone suggestions on how to get this to work?
  12. Hi all, I am trying to get ZFS up and running on my new Helios4. My apologies if I am overlooking something trivial. My assumption is that I need a different image? Steps taken: # apt-get install zfsutils-linux At the final stage of installation (configuration), the error output is: The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. zfs-share.service: Main process exited, code=exited, status=1/FAILURE zfs-share.service: Failed with result 'exit-code'. Image details: Helios4 provided Armbian image Debian 10 - Buster, 02/08/2019