Jump to content

n3o

Members
  • Posts

    127
  • Joined

  • Last visited

Everything posted by n3o

  1. I have still the same errors when I run "sudo apt install zfsutils-linux" The following packages have unmet dependencies: zfsutils-linux : Depends: libnvpair3linux (= 2.1.6-3~bpo11+1) but 2.0.3-9 is to be installed Depends: libuutil3linux (= 2.1.6-3~bpo11+1) but 2.0.3-9 is to be installed Depends: libzfs4linux (= 2.1.6-3~bpo11+1) but 2.0.3-9 is to be installed E: Unable to correct problems, you have held broken packages.
  2. If I run "apt install linux-headers-current-rockchip64" I'll get "linux-headers-current-rockchip64 is already the newest version (22.11.1)." . What kernel version do You have fixed?
  3. image 21.05.1 in kobol site is old... I have a backup image (made with Win32DiskImager) with omv5 (before update to omv6) but also that image, with omv5, when I have tried to install ZFS plugin I have got the same error. Moreover, omv5 has been deprecated and when I update omv to release 6 automatically the kernel is being updated, so I have still the issue. So the best thing is add header to current kernel...
  4. If I have understood ... I should follow this tut https://docs.armbian.com/Developer-Guide_Build-Preparation/ running "./compile.sh BOARD=helios64.csc BRANCH=current KERNEL_ONLY=no RELEASE=buster" to make a bootable image such images listed here https://wiki.kobol.io/download/ ... but in that way I should make a clean install? There isn't another way to update current installation ?
  5. Last official armbian image for Helios64 is 21.08.2... what do You mean for fresh image?
  6. Thank You for the answer...the problem is that sometimes (so not always) I hear a cute sound from hdd. I have 2 hdd WD60EFRX, at one of two, I have disabled the parking heads after idle timer. When I will have possibility, I'll disable the idle timer also for the other hdd. However, the next time that I turn-off helios64, I'll make a video and I'll share it here.
  7. Dear to all, I'm not expert. How can I add kernel header of zfs to linux kernel 5.15.80-rockchip64? I have run the command "apt install dkms zfs-dkms" and I've got the following output: Reading package lists... Done Building dependency tree... Done Reading state information... Done dkms is already the newest version (2.8.4-3). Suggested packages: debhelper Recommended packages: zfs-zed zfsutils-linux linux-libc-dev The following NEW packages will be installed: zfs-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2297 kB of archives. After this operation, 18.0 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://httpredir.debian.org/debian bullseye-backports/contrib arm64 zfs-dk ms all 2.1.6-3~bpo11+1 [2297 kB] Fetched 2297 kB in 0s (5427 kB/s) Preconfiguring packages ... Selecting previously unselected package zfs-dkms. (Reading database ... 78864 files and directories currently installed.) Preparing to unpack .../zfs-dkms_2.1.6-3~bpo11+1_all.deb ... Unpacking zfs-dkms (2.1.6-3~bpo11+1) ... Setting up zfs-dkms (2.1.6-3~bpo11+1) ... Loading new zfs-2.1.6 DKMS files... Building for 5.15.80-rockchip64 Building initial module for 5.15.80-rockchip64 Done. zavl.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ znvpair.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ zunicode.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ zcommon.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ zfs.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ icp.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ zlua.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ spl.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ zzstd.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.15.80-rockchip64/updates/dkms/ depmod...... DKMS: install completed. Processing triggers for initramfs-tools (0.140) ... update-initramfs: Generating /boot/initrd.img-5.15.80-rockchip64 update-initramfs: Converting to u-boot format if I try to execute "apt install zfsutils-linux" I've got 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.6-3~bpo11+1) but 2.1.2-1~20.04.york0 is to be installed Depends: libuutil3linux (= 2.1.6-3~bpo11+1) but 2.1.2-1~20.04.york0 is to be installed Depends: libzfs4linux (= 2.1.6-3~bpo11+1) but 2.1.2-1~20.04.york0 is to be installed Depends: libzpool5linux (= 2.1.6-3~bpo11+1) but 2.1.2-1~20.04.york0 is to be installed E: Unable to correct problems, you have held broken packages. Moreover here https://forum.openmediavault.org/index.php?thread/45376-zfs-version/ ryecoaaron has told me "you really need to make sure the kernel headers are installed first. Then install zfs-dkms. Then install the plugin." How can I install prerequisite so after I can install omv6 zfs plugin also? p.s.1: omv6 zfs-armhf should be installed only in 32 bit instruction set of arm? p.s.2: to mod: if section if thread is wrong please move to right section.
  8. nobody can answer me?
  9. So now I can make image following this tut https://docs.armbian.com/Developer-Guide_Build-Preparation/ ?
  10. Dear to all, I'm new on linux environment so be patience with me. I have a helios64 unit with installed Openmediavault 6. When I reboot or turn-off helios64 (both from webgui interface that from power button) the hard disk ( 2 wd60efrx) make a cute sound from head. How can I check that heads are parked correctly? I don't want damage my hard disks Best regards
  11. @BinaryWaves Luckily I have upgraded to OMV6 and, almost SMB, still work fine... Do You have NUT plugin? I don't have more notifactions when I turnon Helios from UPS plugin... You can confirm me that the switch from buster to bullseye don't reduce stability? I have choose buster image when I have made clean install of armbian, but for the upgrading to OMV 6 automatically has switched to bullseye
  12. @iav What are bootable images? What is u-boot?
  13. if I follow your steps here isn't necessary made a build such here https://docs.armbian.com/Developer-Guide_Build-Options/ ? if however I want compile a build , I should just only execute the following command ./compile.sh BOARD=helios64 BRANCH=current KERNEL_ONLY=no RELEASE=buster ? the main scope that I'm interested, as well as the updates of omv and plugin, is the support of ZFS filesystem even with previous build, build 2.1.5 ( https://github.com/openzfs/zfs/releases ), I can't install it on my system and I get the following error modprobe: FATAL: Module zfs not found in directory /lib/modules/5.15.52-rockchip64 How can I solve ? @Daniel Helios64 and @greg396 do You get some issue with omv 6 and linux kernel 5.15.52 ? p.s.: if we want continue to support helios64 hardware, what it's needed? the source code of driver of the various peripherals and what other? if there is an issue with omv 6, it should be related only between linux kernel and omv 6, why helios hardware should be involved? p.s. 2: somebody has tried kernel 5.19.15?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines