Jump to content

freed00m

Members
  • Posts

    13
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I think shutdowns will always be noisy, because the script ends and there is a TRAP signal that turns it to 100% . But not sure if MAXPWN affects the AFCPWM values in that script. Just look at the `/usr/sbin/fancontrol` ``` function restorefans() { local status=$1 fcvcount pwmo echo 'Aborting, restoring fans...' let fcvcount=0 while (( $fcvcount < ${#AFCPWM[@]} )) # go through all pwm outputs do pwmo=${AFCPWM[$fcvcount]} pwmdisable $pwmo let fcvcount=$fcvcount+1 done echo 'Verify fans have returned to full speed' rm -f "$PIDFILE" exit $status } trap 'restorefans 0' SIGQUIT SIGTERM trap 'restorefans 1' SIGHUP SIGINT ```
  2. Oh it's not nanoITX, nvm.. I just had a look and it wouldn't fit the case.
  3. I think there are open schematics for the boards. What batch your helios comes from? The first batch was in my personal opinion less stable and the other batches had something fixed. Don't have schematics myself I should look for them too. Also Debian? Or Amrbian, I think you should use the Armbian kernel with the patches for uboot, the think that it boots doesn't mean it has everything OK.
  4. Ok, I will drop here one suitable yet ridiculously expensive replacement. Overkill I know. HoneyComb LX2 Workstation. https://www.solid-run.com/arm-servers-networking-platforms/honeycomb-servers-workstation/#honeycomb-workstation My friend got one and very satisfied and he is also underwhelmed Helios64 user. I would get that one too, but I am cheap not gonna lie. I talked with him and he likes the board, the u-boot runs quite OK (maybe upstreamed even) + he tried to compile u-boot for helios64 to boot something else than amrbian kernel without much success. It has 4x SATA 3.0 even some 8xPCI-e with standalone 4xPCI-e for M2-slot. But I think no UPS support + it is probably more power hungry than helios64. Also I've seen power supplies so small and mountable without case shielding (made in china), maybe it could fit inside also.
  5. So far so good on my side. Though I use only plain setup, mdadm 2 drives mirror raid + extra 3 satas for transmission downloading. And just transferred 1TB via Rclone on another over the internet NAS that took 8h and have not observed a fail. Running OS from emmc and I don't write often as apt cache moved to SATA drive. Didn't test speeds prior upgrade. I have helios64 from the last latest batch, those with 2.5gbit fixed.
  6. Have you pinned it down @Karol ? I am suffering also a transmission not working at all. Daemon is running and active yet the connection to the web interface is killed after several seconds of transmission running. EDIT: Nevermind, I pinpointed the issue on the transmissions's blocklists. Due to upstream went under paywall, the hosted github file was returnint 404. Yes! transmission should not have fail in that case but it did. Other thing that is unrelated that I change the bind address from 0.0.0.0 to the actual one the armbian helios64 device has.
  7. @allen--smithee Thx for the mod tip, I'll do it when I move and have more time. For the time being I will writte myself a systemd service that apply patch (uncomment the script's traps) and when need for quite termintion, I will comment out the lines to have quite halt).
  8. @gprovost - Thx that indeed acomplish what I want. Question, what purpose does it serve? Making loud halting seems like a unwanted behavior. Also what side effects can I expect? the script is at /usr/sbin/fancontrol .
  9. Hi, I want to ask, if there's a way how to turn off Helios64 without the 100% fan spin. It only takes 1 second but it's very annoying when I want to turn it off during the night. Looking https://github.com/armbian/build/blob/master/packages/bsp/helios64/fancontrol.conf and https://wiki.kobol.io/helios64/pwm/ No luck :Z
  10. kobol:~:% sudo hdparm -I /dev/sd[a-e] | grep level [sudo] password for frdm: Advanced power management level: 254 Advanced power management level: 254 Hi, the levels ar 254, which is by that APM value list @clostro posted a reserved value. Maybe if I set a non spindown value it might solve the testing issue, I might try next time I want to run longtest.- It was just Armbian 21.02.1 Buster with Linux 5.10.12-rockchip64 image installed recently, so everything is somewhat default.
  11. Mystery solved! After I discovered that smart tests succeeds in Windows WD WinDTF tool and fail the same manner on different machine with Archlinux I knew the drives are the incompatibility with smartctl. The issue with while true; do dd if=/dev/sda of=/dev/null count=1; sleep 60; done was that it did not prevent the disk from sleep due to WD Gold drives having 256MB of buffer ssd cache. To prevent this the dd has to have iflag=direct so it wont go to sleep and really don't understand why. But even better solution is to query smartctl -a periodicaly to prevent it from sleep. Running this will let my tests to complete. # watch -n 60 /usr/sbin/smartctl -a /dev/sda Anyhow, is this solvable on the smartctl part? Should I open a issue on smartmontools or is this common behavior?
  12. Hi, sorry to reply after such long time, the forum rules allows newbies to make 2nd post after 24h. @Gareth Halfacree thx for tip, there was no DRDY event in dmesg after running the test. I've also tried to move /dev/sdb from SATA 2nd position to SATA 3rd possition. No effect. @gprovost yes I'ved added the line, and this is how the ambianEnv.txt looks like at /boot now The test are still being interrupted. ``` verbosity=1 bootlogo=false overlay_prefix=rockchip rootdev=UUID=e4e3bcd6-3f03-4362-bbe0-f1654138c5d8 rootfstype=ext4 extraargs=libata.force=noncq usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u ``` usbstoragequirks? how did that get there does that mean the drive atatched them selves as UAS and could make the test fail? I've never formatted and used the drives, I wanted to have successful longtest before using them daily. I will do some more testing and troubleshooting. I really hope the SATA Harness cable is not damaged. Will post more. ---- Fun, reading threads like these https://community.synology.com/enu/forum/1/post/123516 makes me think the problem is very common for some drives.
  13. Hello, I've bought 3 new identical drives and put 2 of them in the Helios64 and 1 onto my desktop. I ran smartctl longtest+shortest on both drives simultanously but all of them were aborted/interupted by host. `# /usr/sbin/smartctl -a /dev/sda` Output: http://ix.io/2OLt On my desktop the longtest from smartctl succeeds without error and all 3 drives received the same care, I just bough them and installed them, so unlikely the drives are physically damaged. The complete diagnostic log: http://ix.io/2OBr So anyone got an idea why are my SMART extended tests being canceled? Note: I've tried even the trick with running background task to prevent drives from some vendor sleep `while true; do dd if=/dev/sda of=/dev/null count=1; sleep 60; done`
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines