manman

Hello, I have the same issue, when I've plugged into a APC powersuply that send a more reliable power the Helios64 was running pretty stable. But now I'm starting to have some disks not turning ON. Some of the system messages: [...] ata2: SATA link down (SStatus 0 SControl 300) ata2: limiting SATA link speed to 1.5 Gbps ata3: COMRESET failed (errno=-32) [...] the sata 4 and 5 turns ON correctly with 6Gbs

UPDATE: Even changing the cables, the disks keep failing over time. I wasn't able to have my NAS running more than a day or two without a failure on the disks. After buying an APC UPS with Boost and Trim Automatic Voltage Regulation (AVR), my NAS is now running without any failure over more than a week! So the problem was the unstable energy in my house. Maybe I'll try to put back the original ones to see if it works.

I've bought a molex power cable to use with the new sata cable. But i've not found a sata power cable 8pin(6+2) with the capacitors that came with Helio64. Do you think that will work? or It's better to destroy the sata data cable of original cable as @meymarce described? I'm hoping that this will work. It's sad that we cannot have some spare basic parts of the Helios64 I've bought the following expansion cable to use with the original Helio64 power molex cable 8pin(4+4) Now my helios64 came back to life =D I was able to complete rebuild the Raid6 and it's working like a charm. The problem is that now I have a lot of cables on the case that was difficult to find an arrangement in a way that I was able to close the case with the fans. The @meymarce solution on splitting the cable is better if you are able to do with confidence not to destroy the power cable.: Thanks!

Hello, I have the same problem with the SATA 3, 4 and 5. They where failing very often and the RAID 6 was falling and I had to rebuild. But on the last days they don't even powerup. I've tried repluging everything with no success. I'm using 4 new seagate's Red 4TB with Raid6 ext4 and one M2 SSD WD Blue. [ 2.986119] ahci 0000:01:00.0: version 3.0 [ 2.986158] ahci 0000:01:00.0: enabling device (0000 -> 0002) [ 2.986781] ahci 0000:01:00.0: SSS flag set, parallel bus scan disabled [ 2.986883] ahci 0000:01:00.0: AHCI 0001.0301 32 slots 5 ports 6 Gbps 0x1f impl SATA mode [ 2.986896] ahci 0000:01:00.0: flags: 64bit ncq sntf stag pm led clo pmp fbs pio slum part ccc apst boh [ 2.990725] scsi host0: ahci [ 2.991508] scsi host1: ahci [ 2.992139] scsi host2: ahci [ 2.992767] scsi host3: ahci [ 2.993387] scsi host4: ahci [ 2.993618] ata1: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010100 irq 91 [ 2.993629] ata2: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010180 irq 92 [ 2.993639] ata3: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010200 irq 93 [ 2.993649] ata4: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010280 irq 94 [ 2.993659] ata5: SATA max UDMA/133 abar m8192@0xfa010000 port 0xfa010300 irq 95 ... [ 4.280968] ata3: SATA link down (SStatus 0 SControl 300) [ 4.592768] ata4: SATA link down (SStatus 0 SControl 300) [ 4.904777] ata5: SATA link down (SStatus 0 SControl 300)

@ShadowDance I've got an error when I was trying to build the 2.0.0 release using your instructions, getting the following error on "make deb" : kmodtool error: Don't know how to handle 5.9.11 -- /lib/modules/5.9.11/build/Makefile not found I've tried to change the kernel version to "5.9.11-rockchip64" directly on the Makefile but the build it fails anyways. the right PATH should be /lib/modules/5.9.11-rockchip64/build/Makefile