ChrisO

Sorry, it will be quite long 🙂 I have three HC4 devices: odroid1: Linux odroid1 5.10.57-meson64 #21.05.8 SMP PREEMPT Mon Aug 9 12:44:31 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux ata-Samsung_SSD_870_QVO_1TB ata-Samsung_SSD_870_QVO_1TB odroid2: Linux odroid2 5.19.17-meson64 #22.08.7 SMP PREEMPT Thu Oct 27 18:34:08 CEST 2022 aarch64 aarch64 aarch64 GNU/Linux ata-Samsung_SSD_870_QVO_1TB ata-Samsung_SSD_870_QVO_1TB They run the kernel which recognized both discs AND there was ZFS support when I installed them. odroid3, currently used for some experimenting: Linux odroid3 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux odroid3 recognises those disks: ata-Samsung_SSD_840_EVO_120GB_S1D5NEAD710633R ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R I replaced the ata-Samsung_SSD_840_EVO_120GB_S1D5NEAD710633R by another Samsung SSD_860_EVO_250GB It is not recognized, and in the /var/log/kern.log I see this: odroid3 kernel: [ 2.692110] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 27 odroid3 kernel: [ 2.692124] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 27 odroid3 kernel: [ 3.005134] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.478833] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Disconnected the ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R and rebooted NO ssd! /var/log/kern.log: odroid3 kernel: [ 2.901128] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.213129] ata2: SATA link down (SStatus 0 SControl 300) Tried both SATA slots, same results. Tried another Samsung SSD_860_EVO_250GB, same results, no SSD. The same "SATA link down" message. I bought a Crucial 1TB just to change manufacturer: ata-CT1000MX500SSD1_2249E68F3955 Works in both SATA slots. Rebooted again with ata-Samsung_SSD_750_EVO_250GB_S33SNWAH687472R and ata-CT1000MX500SSD1_2249E68F3955 The last one in not there, the same messages in /var/log/kern.log. Two days later I rebooted it to try libata.force=noncqtrim kernel parameter and both disks are there. Removed libata.force=noncqtrim from armbianEnv.txt rebooted again, both disks are there. Then shutdown, power off/on and boot, no CT1000MX500SSD1. I tried the SD-card from odroid3 in the odroid2 and there both Samsung_SSD_870_QVO_1TB are there. Rebooted few times, just in case 😉 they were always there. Then disconnecte those two disks and connected the CT1000MX500SSD one: no disk after reboot. Put the SD-card in odroid1, only one disk, Samsung_SSD_870_QVO_1TB, is there. Replaced one of Samsung_SSD_870_QVO_1TB by CT1000MX500SSD, both are not there: kern.log: odroid3 kernel: [ 2.940933] ata1: SATA link down (SStatus 0 SControl 300) odroid3 kernel: [ 3.252903] ata2: SATA link down (SStatus 0 SControl 300) I like the HC4 (when it works 😉 so I ordered another one hoping it will not have any problems. Got it today (I must be one of the best HK's custommers: H3, H3+, 4 x HC4 🙂 booted with a EVO 860 250GB SSD: uname -a Linux odroid4 6.1.63-current-meson64 #1 SMP PREEMPT Mon Nov 20 10:52:19 UTC 2023 aarch64 GNU/Linux No SSD there. Re-plug it (I know the riscs) and lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232.9G 0 disk Rebooted. lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 232.9G 0 disk Rebooted again and the SSD is there. Aha, rebooted, not powered off/on. init 0 remove power 10 seconds connect power The SSD is there. init 0 Connected the CT1000MX500SSD, boot. lsblk -> no SSD. Somehow it doesn't make any sense, I don't see any regularity in all this. Did again hotplug ~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 931.5G 0 disk Some time ago I already reported the problem with SSD's not being recognized. And the strange thing is, some of the events are quite random. The SSD is there, than not there. Now I would say: HC4 and kernels newer than 5.19.17-meson64 don't want to cooperate correctly. Who is the culprit? I don't know, don't have the necessary skills to debug it. However, I would love to provide all infos needed which HK needs to analyze the problem. Screenshots, etc. BTW, rebooted odroid4 again, no SSD. Regards, Chris

Haven't got any help in HardKernel Forum: https://forum.odroid.com/viewtopic.php?f=205&t=45941&p=366587#p366587 As I said, I just want to find out what is the cause of the problem, the few $ for the now useless hc4 is not the problem. I don't have the skills to do necessary diffs on some kernel versions to find out what and when originated the problem. If anybody feels like challenged, let me/us know 🙂

Thanks! 👍

The zfs-dkms included in Armbian_22.11.1_Odroidhc4_jammy in version 2.1.4 is to old for 5.19.17 kernel. It should be 2.1.6 like in Armbian_22.08.7. Loading new zfs-2.1.4 DKMS files... Building for 5.19.17-meson64 Building initial module for 5.19.17-meson64 configure: error: *** None of the expected "blk_queue_discard" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 http://paste.debian.net/1267188/

There is no BIOS or such there, I couldn't find nothing like a serial number using lshw/hwinfo. On the boards themselves there some numbers. Both boards are Rev 10.020200807, however another numbers I found on them differ, on the old one there is a E257384 2034, on the newer one E257384 2214. Go figure out. From HK didn't get any clear answer, even if people there in the forum seam nice and helpful. As for what you wonder about: don't think so, I might be wrong, though 🙂

Again, I have two HC4 boards, the newer one runs now: Linux 5.19.17-meson64 As for the older one: every kernel newer then 5.13.12 incl. 6.x I tried gives me the same problem: only one disk visible. As for the boot loader, both boots from a SD card. Yesterday I put Armbian_21.08.6_Odroidhc4_jammy_edge_5.15.4.img on the SD card, newer HC4 OK, older one bootet from the _same_ SD card: only one disk there. If a NON self modifying software behaves differently on two pieces of HW, they must, IMHO, differ, no? HardKernel means they don't. I guess I'm stuck 😞

As the original thread, which was closed by moderator for obvious reason, did attract attention of few peoples having the same problem as me, it would be a waste not to follow up on this, I think. Let me sum up: I have two HC4, one bought in 8.2021 and other one 11.2022, both have two SSDs each. The older one after a kernel upgrade didn't see a second disk any more. I've just tried few kernels I could find with the following results: OK: Linux odroidhc4 5.12.10-meson64 #21.05.4 SMP PREEMPT Wed Jun 16 08:19:35 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux OK: Linux odroidhc4 5.13.12-meson64 #21.08.1 SMP PREEMPT Wed Aug 25 19:35:13 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Not OK:Linux odroidhc4 5.15.4-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:46:10 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Couldn't find any kernel between 5.13.12 and 5.15.4, so it's not clear which is exact the version where the problem started. Here is what I found in /var/log/syslog: Nov 22 14:40:46 odroidhc4 kernel: [ 2.355049] ata1: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700100 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.355060] ata2: SATA max UDMA/133 abar m512@0xfc700000 port 0xfc700180 irq 38 Nov 22 14:40:46 odroidhc4 kernel: [ 2.358363] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.564017] libphy: mdio_mux: probed Nov 22 14:40:46 odroidhc4 kernel: [ 2.830521] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830799] ata1.00: FORCE: horkage modified (noncq) Nov 22 14:40:46 odroidhc4 kernel: [ 2.830854] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.830860] ata1.00: ATA-11: Samsung SSD 870 QVO 1TB, SVQ02B6Q, max UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.830865] ata1.00: 1953525168 sectors, multi 1: LBA48 NCQ (not used) Nov 22 14:40:46 odroidhc4 kernel: [ 2.832778] ata1.00: Features: Trust Dev-Sleep Nov 22 14:40:46 odroidhc4 kernel: [ 2.833128] ata1.00: supports DRM functions and may not be fully accessible Nov 22 14:40:46 odroidhc4 kernel: [ 2.835140] ata1.00: configured for UDMA/133 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835408] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 870 2B6Q PQ: 0 ANSI: 5 Nov 22 14:40:46 odroidhc4 kernel: [ 2.835890] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.836066] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) Nov 22 14:40:46 odroidhc4 kernel: [ 2.836102] sd 0:0:0:0: [sda] Write Protect is off Nov 22 14:40:46 odroidhc4 kernel: [ 2.836108] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 Nov 22 14:40:46 odroidhc4 kernel: [ 2.836159] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 22 14:40:46 odroidhc4 kernel: [ 2.850916] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.872432] sda: sda1 sda9 Nov 22 14:40:46 odroidhc4 kernel: [ 2.872842] ata1.00: Enabling discard_zeroes_data Nov 22 14:40:46 odroidhc4 kernel: [ 2.886688] sd 0:0:0:0: [sda] Attached SCSI disk Nov 22 14:40:46 odroidhc4 kernel: [ 3.148738] ata2: SATA link down (SStatus 0 SControl 300) The newer HC4 doesn't show this problem which leads me to the conclusion: their hardware (firmware?) must differ. Asked about it on the HardKernel Forum, didn't get a clear answer (yet?). I don't know how to proceed i.e. where to look for further help. Any idea anyone? I'm to old for an advanced GIT class 😉 Thanks for your time. Chris

Thanks for your info. Glad you are back to normal. And I don't feel so alone anymore 🙂

Some time ago a I was desperate to have ZFS on an Odroid HC4 and after some trying found Armbian 21.05.8 Buster with Linux 5.10.57-meson64 on which I could compile ZFS module. Then I moved everything from the SD card to filesystems in a ZFS pool. It boots from SD card, though. And has been working fine for several months. Recently I bought another HC4 and took the current Armbian image for it: Armbian 22.08.8 Jammy with Linux 5.19.17-meson64 Everything works fine. Tried this image on the older HC4 and it doesn't see the second SSD. In the syslog I found this message: ata1: SATA link down (SStatus 0 SControl 300) Is it a firmware problem? Googling hasn't help. Any idea anyone? Thanks for your time. Chris BTW Does anybody know how to disable the "Clear Screen" after the "Starting kernel" message? I would like to see what u-boot has to tell me, especially if I have some problems.

Installed from scratch, Armbian_22.08.1_Odroidhc4_jammy_current_5.10.139.img apt update/upgrade apt install zfs-dkms zfsutils-linux Forgot the linux-headers. Started armbian-config, selected "Software", error message appears: grep: invalid max count Selected "Headers_install", again error message from grep. Headers not installed. Installed headers with: apt install linux-headers-current-meson64 then dpkg-reconfigure zfs-dkms Result: Loading new zfs-2.1.4 DKMS files... Building for 5.10.144-meson64 Building initial module for 5.10.144-meson64 configure: error: *** Unable to build an empty module. Error! Bad return status for module build on kernel: 5.10.144-meson64 (aarch64) Consult /var/lib/dkms/zfs/2.1.4/build/make.log for more information. root@odroidhc4:~# cat /var/lib/dkms/zfs/2.1.4/build/make.log DKMS make.log for zfs-2.1.4 for kernel 5.10.144-meson64 (aarch64) Wed Sep 28 12:44:00 PM CEST 2022 make: *** No targets specified and no makefile found. Stop. Thanks, ChrisO

Started armbian-config, selected "Software", error message appears: grep: invalid max count Selected "Headers_install", again error message from grep. Headers not installed. Installed headers with: apt install linux-headers-current-meson64 Result: Loading new zfs-2.1.4 DKMS files... It is likely that 5.19.10-meson64 belongs to a chroot's host Building for 5.10.144-meson64 Building initial module for 5.10.144-meson64 configure: error: *** Unable to build an empty module. Error! Bad return status for module build on kernel: 5.10.144-meson64 (aarch64) root@odroidhc4:~# tail /var/lib/dkms/zfs/2.1.4/build/make.log DKMS make.log for zfs-2.1.4 for kernel 5.10.144-meson64 (aarch64) Wed Sep 28 10:36:10 AM CEST 2022 make: *** No targets specified and no makefile found. Stop. Thanks ChrisO

Hi I was using: Title: Armbian 21.08.5 Odroidhc4 Debian buster legacy Then something bad pushed me to run apt update/upgrade No ZFS anymore. Installed 22.08.2, but, when tried to install kernel headers using armbian-config, result: "grep: invalid max count" message. What is the current correct way to install Armbian with ZFS? Thanks ChrisO

Computer said: "This item was deleted"