meymarce

  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

meymarce's Achievements

  1. @RockBian yeah that is the set. However the seller I ordered from is no longer there. The best offer right now is this https://www.aliexpress.com/item/4000168090307.html However your error is a different one and I cannot see the reset of the SATA connection but if you FS goes into read-only that may indicate another issue. Did the drive in slot 4 work after all? Cause some people had slot 4/5 resp. 1/2 depending how you count (the two that share power) fail completely. If you wanna exchange the cables though: the power os from the original harness, I cut of the data connection part using a separation disk on a rotary tool (Dremel like).
  2. You can also try setting MAX_SPEED to 408000. However I have a stable system since I raised the voltage in /boot/boot.cmd
  3. I guess what he is after is having this sorted on your summary by problem and fixes. Also for the SATA issue the workaround that worked too is to exchange the SATA cabled. If someone wants to retain the hotplug connector I found something there that works
  4. You guys have tried the usual low CPU clock/ raise voltage things?
  5. The voltage thingy was not specific to the SATA issues but the general system stabilty. And may have not been specific enough, sorry. I meant the VDD fixes here: Before that my system would go into random panics regardless of frequencies and governor. However I never really checked the callstacks. This was also done upstream for the RockPro64 (same CPU) to improve general system stability. There was a post by @gprovostthough to try it with a new kernel and the VDD fix removed but I had no luck with that. VDD raised and I am all good.
  6. Just took a quick look at the ZFS sources (on master though) and the only place I can see where this would get called looking at the callstack is https://github.com/openzfs/zfs/blob/ba91311561834774bc8fedfafb19ca1012c9dadd/module/zfs/zio.c#L4772 So it must have hit an error at this point already. Are you running the modified SATA firmware? Also my system is still plagued by the panics on boot. Second attempt works like a charm then. The only fix I applied was raising the voltage and my custom SATA harness. However I right now have little to zero load. What distri are you running now? The other thread mentioned Buster and Focal (though iirc they run the same kernel). I am running Buster with 4 Seagate Ironwolf 10TB.
  7. @usefulnoise @ShadowDance Maybe this is interesting for you: As I had the same issue but did not wanna mess around too much and some where successful with 3rd party sata cables, I was looking for a way to get this done w/o loosing the HDD slides into the SATA slot option. I found this (hope this does not count as advertisement): https://www.aliexpress.com/item/1005002595620272.html which seems to be the general harness of a Lenovo X3100 M5 Server. I was also looking to get some screw-able SATA mounts, but could not find any that would not require me doing the cable works and soldering too. However the Lenovo cables looked promising and as it turns out, you just use this as a drop in replacement. The screws fit. However you have to mount them from the front side instead the back, but the case has enough space to do that. You do however need to push very hard, to get the screws to grip, but even the threads match. I did a bit of grinding on the metal frame though to reduce the tension on the plastic of the connector cause it is a bit thicker. Not sure that is required though (I think not). For the fifth slot some grinding will be inevitable though. Since that slot is not populated for me right now (and has to wait a bit on current pricing unless I find a bargain) and one cable set has 4 cables, this was no issue. Another two cable sets are on the way though (have another Helios64). I do not know how you cut the connectors of the original harness to get power only, but I used a separation disk on a Dremel like tool. Worked like a charm. The cables are all similar length so you need to do try a bit until you find a position that works and does not twist the cable too much but gets it to the ports on the board. Here what I ended up with (sorry for the sub-optimal quality but only saw this now on the PC and I do not want to disassemble the case again) Hope that is helpful for anyone. I am super happy with this solution I have not had any issues with my ZFS setup anymore since. Cheers
  8. Did you follow https://wiki.kobol.io/helios64/software/zfs/install-zfs/ and also installed zfs-dkms ?
  9. I am having the issue that after some time running (like a day). Rebooting results in crashing during kernel loading. Than I have to hardreset the system and it boots. If I reboot right away again, no issue. I used to have quite a few stability issues, which are now all solved with the voltage fix applied. Running stock frequencies with on-demand. Anyone having any ideas? I hope the Kobol team is enjoying some time off though I still see you around. Keep recharging, you really deserve it.
  10. for 1) I would not call it a debian issue. It is more like a general Linux issue and has been addressed in the way there is /dev/disk/by-{id,partuuid,path,uuid} to reliably address the disks. for 3) the 10s is if I'd guess, to spin up the disks. Quick research shows me hdparm should be helpful. Never use that myself though. if your board is running stable in stock settings, then all cores will go to the lowest clock possible. Overall consumption in idle will be dominated by the spinning disks if they are running. Also check the wiki on consumption: https://wiki.kobol.io/helios64/hardware/#power-consumption
  11. I am having the same issue: though I wanna mention that I use Seagate drives. So the issue is not restricted to WD. I can reliably get it using a zfs scrub. Currently 4 disks are in use and it always happens on /dev/sdd, so disk 4. Disk 5 is the empty slot. I have read most of the comments but did anyone really succeed with a new power harness or the new firmware? [16218.668509] ata4.00: exception Emask 0x10 SAct 0x1000084 SErr 0xb80100 action 0x6 frozen [16218.668523] ata4.00: irq_stat 0x08000000 [16218.668530] ata4: SError: { UnrecovData 10B8B Dispar BadCRC LinkSeq } [16218.668539] ata4.00: failed command: READ FPDMA QUEUED [16218.668551] ata4.00: cmd 60/b8:10:e0:43:37/07:00:11:03:00/40 tag 2 ncq dma 1011712 in res 40/00:38:98:4b:37/00:00:11:03:00/40 Emask 0x10 (ATA bus error) [16218.668556] ata4.00: status: { DRDY } [16218.668562] ata4.00: failed command: READ FPDMA QUEUED [16218.668574] ata4.00: cmd 60/b8:38:98:4b:37/07:00:11:03:00/40 tag 7 ncq dma 1011712 in res 40/00:38:98:4b:37/00:00:11:03:00/40 Emask 0x10 (ATA bus error) [16218.668578] ata4.00: status: { DRDY } [16218.668584] ata4.00: failed command: READ FPDMA QUEUED [16218.668595] ata4.00: cmd 60/b8:c0:58:53:37/07:00:11:03:00/40 tag 24 ncq dma 1011712 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x14 (ATA bus error) [16218.668600] ata4.00: status: { DRDY } [16218.668612] ata4: hard resetting link [16219.144463] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [16219.163619] ata4.00: configured for UDMA/133 [16219.164082] ata4.00: device reported invalid CHS sector 0 [16219.164110] sd 3:0:0:0: [sdd] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=31s [16219.164116] sd 3:0:0:0: [sdd] tag#2 Sense Key : 0x5 [current] [16219.164121] sd 3:0:0:0: [sdd] tag#2 ASC=0x21 ASCQ=0x4 [16219.164127] sd 3:0:0:0: [sdd] tag#2 CDB: opcode=0x88 88 00 00 00 00 03 11 37 43 e0 00 00 07 b8 00 00 [16219.164133] blk_update_request: I/O error, dev sdd, sector 13173736416 op 0x0:(READ) flags 0x700 phys_seg 125 prio class 0 [16219.164148] zio pool=r2pool vdev=/dev/disk/by-id/ata-ST10000VN0004-1ZD101_$serial-part1 error=5 type=1 offset=6744951996416 size=1011712 flags=40080cb0 [16219.164209] sd 3:0:0:0: [sdd] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=31s [16219.164213] sd 3:0:0:0: [sdd] tag#7 Sense Key : 0x5 [current] [16219.164218] sd 3:0:0:0: [sdd] tag#7 ASC=0x21 ASCQ=0x4 [16219.164222] sd 3:0:0:0: [sdd] tag#7 CDB: opcode=0x88 88 00 00 00 00 03 11 37 4b 98 00 00 07 b8 00 00 [16219.164227] blk_update_request: I/O error, dev sdd, sector 13173738392 op 0x0:(READ) flags 0x700 phys_seg 142 prio class 0 [16219.164235] zio pool=r2pool vdev=/dev/disk/by-id/ata-ST10000VN0004-1ZD101_$serial-part1 error=5 type=1 offset=6744953008128 size=1011712 flags=40080cb0 [16219.164286] sd 3:0:0:0: [sdd] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=31s [16219.164291] sd 3:0:0:0: [sdd] tag#24 Sense Key : 0x5 [current] [16219.164295] sd 3:0:0:0: [sdd] tag#24 ASC=0x21 ASCQ=0x4 [16219.164299] sd 3:0:0:0: [sdd] tag#24 CDB: opcode=0x88 88 00 00 00 00 03 11 37 53 58 00 00 07 b8 00 00 [16219.164304] blk_update_request: I/O error, dev sdd, sector 13173740376 op 0x0:(READ) flags 0x700 phys_seg 127 prio class 0 [16219.164311] zio pool=r2pool vdev=/dev/disk/by-id/ata-ST10000VN0004-1ZD101_$serial-part1 error=5 type=1 offset=6744954023936 size=1011712 flags=40080cb0 [16219.164339] ata4: EH complete