Alexander Eiblinger

Hi ... thanks for your hint. Actually I forced on the old system sata speed to 3.0 GB ... which I did not on the new installation. Setting also the link speed to 3.0 GB did however not solve the issue, I had to set it down to 1.5 GB. Now the issue seems to be gone. Performancewise it is not noticeable for harddisks, but for the SSD I have it is - need to look further into it. I'm just wondering what (still) the difference is. Forcing link speed down to 1.5 GB was not needed before ... I'm tending to exclude "hardware" as source of issues, as the hardware is in both cases identicial, no single cable touched. CU Alex

Servus! I'm running an "old" Helios64, still with debian buster and kernel 5.9.14-rockchip64 ... pretty much the same installation, as I had setup the Helios64 years ago. So far it is running great, with no real issues. I have ZFS running on it, with 3 disks. Today I decided to upgrade to something new - and installed Armbian 25.5.1 / Nobel - with kernel "6.12.32-current-rockchip64". Helios64 boots up and everything seems to work fine. I was able to import my ZFS pool and it was accessible - however, when I do heavy i/o, e.g. md5sum on a big file, I get a lot of these errors: Jun 08 20:06:36 helios64 kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 08 20:06:36 helios64 kernel: ata2.00: cmd 60/80:90:40:3a:2f/00:00:06:00:00/40 tag 18 ncq dma 65536 in res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x12 (ATA bus error) Jun 08 20:06:36 helios64 kernel: ata2.00: status: { DRDY ERR } Jun 08 20:06:36 helios64 kernel: ata2.00: error: { ICRC ABRT } Jun 08 20:06:36 helios64 kernel: ata2: hard resetting link Jun 08 20:06:36 helios64 kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Jun 08 20:06:36 helios64 kernel: ata2.00: configured for UDMA/133 Jun 08 20:06:36 helios64 kernel: ata2: EH complete Jun 08 20:07:04 helios64 kernel: ata2: limiting SATA link speed to 1.5 Gbps Jun 08 20:07:04 helios64 kernel: ata2.00: exception Emask 0x2 SAct 0x202003 SErr 0x400 action 0x6 Jun 08 20:07:04 helios64 kernel: ata2.00: irq_stat 0x08000000 Jun 08 20:07:04 helios64 kernel: ata2: SError: { Proto } Jun 08 20:07:04 helios64 kernel: ata2.00: failed command: READ FPDMA QUEUED Jun 08 20:07:04 helios64 kernel: ata2.00: cmd 60/00:00:98:55:7f/08:00:07:00:00/40 tag 0 ncq dma 1048576 in res 41/84:00:00:00:00/00:00:00:00:00/00 Emask 0x12 (ATA bus error) Jun 08 20:07:04 helios64 kernel: ata2.00: status: { DRDY ERR } Jun 08 20:07:04 helios64 kernel: ata2.00: error: { ICRC ABRT } This is for ata2, but this happens also for ata3 and ata4 - so all three disk of my ZFS. Interesting so, ZFS itself does not detect any read / write errors - but if you e.g. copy files, you see a noticeable drop in throughput, disk access hangs for a moment. I have installed 25.5.1 on SD card, so I was able to switch back to my original system ... and voilá, no such errors anymore. So it seems to be related to 25.5.1. Does anyone know this problem? Is there a solution or anything I'm missing? Thanks Alex

Hi. I'm in the process of preparing to sell my Helios64. If you interested let me know. (I'm selling it as one of the HD power rails does not bring the needed voltage anymore ... and I need more disks now).

I'm not an expert here, but I have struggled with "failed" disks quite some time meanwhile ... According to your dmesg you disk has no link 2.670580] ata1: SATA link down (SStatus 0 SControl 300) I'd interpret this as "there is no disk plugged in" ... so I'd guess it is more a cable topic. So I'd do the obvious: Make sure that the disk is properly plugged in and really reaches the connectors of the backplane. Inspect the cable harnes from the other side, is it really correctly installed. In worst case: remove the cable from the vaulty slot and plug it directly into the disc.

Hi there ... Not sure if anyone has an idea here, but I have the following topic: I have a helios64, equipped with 3 2.5" disk drives, running Debian 10 with Kernel 5.10.43. Usually the system runs stable ... even for days (24/7). But every now and then the disks "fail" - which means, during normal operation suddenly the disk turn of, linux reports "sata link down" ... and the disks are off. As if they were removed. If I reboot I usually here only some "klicks" ... I assume the disks try to spin up, but fail due to not enough power (?). To recover from that situation, I usually disconnect power (incl. the internal UPS) ... try a few times, and sooner or later disks power successfully up again. Then the system run's again for a while without any issues. I already tried to re-cable everything, trying to ensure that the cables are properly connected, but this does not seem to help. I assume that there is an hardware issue with the SATA power rails (both show the same effect). For that reason I'm looking for the schematics, to trace that a little deeper ... anyone an idea if they are somewhere available? Thanks!