alban

  • Posts

    3
  • Joined

  • Last visited

alban's Achievements

  1. Since I got my Helios64 : I had an hadrware problem (voltage on some disk drop too low : it ended : replace MB) But I had many panic/ freeze since first days. I was never able to pass 10 days without problems until I read this topic : Last month I decided to set freq policy as read here : root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_max_freq 1416000 1416000 root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/scaling_min_freq 1416000 1416000 root@helios64:~# cat /sys/devices/system/cpu/cpufreq/policy*/cpuinfo_cur_freq 1416000 1416000 And I have a much more stable system root@helios64:~# uptime 18:35:42 up 30 days, 1:34, 1 user, load average: 0.01, 0.03, 0.00 root@helios64:~# uname -a Linux helios64 5.10.60-rockchip64 #21.08.1 SMP PREEMPT Wed Aug 25 18:56:55 UTC 2021 aarch64 GNU/Linux root@helios64:~# cat /etc/issue Armbian 21.08.1 Buster \l
  2. UPDATE : Slot 1 & 2 won't start anymore with many tests : Battery connected or not doesn't change anything I tried with external power and brand new sata 6Gbit cable : it's working fine I tried with sata power splitter Y from Solt1 or slot2 line : disks doesn't start with external Sata cable : It seems there are trouble with power lines from stock harness I tried with sata power splitter connected from Slot 3 powering slot 1 & 2 : drives 1 / 2 / 4 / 5are working : seems OK I will try with 2 sata splitter Y (delivery planned for tonight) Conclusion for now : Seems power isn't properly achieved through stock harness : I was thinking trouble with sata data cables but problem for my unit seems mainly from power sata connectors I will keep you update
  3. Hello, I'm getting same issue : [ 3613.284995] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0xb80100 action 0x6 [ 3613.285019] ata4.00: irq_stat 0x08000000 [ 3613.285035] ata4: SError: { UnrecovData 10B8B Dispar BadCRC LinkSeq } [ 3613.285053] ata4.00: failed command: READ DMA EXT [ 3613.285081] ata4.00: cmd 25/00:40:f0:a9:36/00:05:04:00:00/e0 tag 26 dma 688128 in res 50/00:00:f0:a9:36/00:00:04:00:00/e0 Emask 0x10 (ATA bus error) [ 3613.285092] ata4.00: status: { DRDY } [ 3613.285113] ata4: hard resetting link [ 3614.116878] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3614.117787] ata4.00: configured for UDMA/133 [ 3614.117946] ata4: EH complete I was runing Armbian 20.11 with 5.9 kernel since first install on sdcard and this problem occured during last days I tried to install a new system from last image Armbian 21.02 on emmc to be sdcard independant The error occur within hours after boot It ends to reduce ata link speed and finally to disable the first 2 drives (corressponding to sda and sdb in my case) : LED were off when I noticed problem I'm using 5 WDC WD30EFRX as Raid6 array I tried NCQ disable tonight and I'm getting error not long after boot : I forced array recheck and as I'm wrriting this article, I'm getting an other error : [ 4003.337231] ata4.00: exception Emask 0x10 SAct 0x0 SErr 0xb00100 action 0x6 [ 4003.337248] ata4.00: irq_stat 0x08000000 [ 4003.337256] ata4: SError: { UnrecovData Dispar BadCRC LinkSeq } [ 4003.337265] ata4.00: failed command: READ DMA EXT [ 4003.337278] ata4.00: cmd 25/00:40:80:41:09/00:05:09:00:00/e0 tag 7 dma 688128 in res 50/00:00:80:41:09/00:00:09:00:00/e0 Emask 0x10 (ATA bus error) [ 4003.337283] ata4.00: status: { DRDY } [ 4003.337298] ata4: hard resetting link [ 4004.169150] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 4004.170064] ata4.00: configured for UDMA/133 [ 4004.170222] ata4: EH complete If this is sata cable related I don't get why this problem come a few month after non stop working fine. Any other idea ? In case here my serial : cat /proc/device-tree/serial-number 000100001235 Regards