SIGSEGV

  • Content Count

    21
  • Joined

  • Last visited

About SIGSEGV

  • Rank
    Member

Recent Profile Visitors

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

  1. @jbergler 5.8.x & 5.9.x are working here as well, but I'm not using ZFS, just plain vanilla mdadm RAID and LVM2 formatted as XFS. If you have an extra set of HDDs could you try building a new data pool with mdamd or LVM2 to test your setup? Since you're getting memory related errors, is there a way for you to run a memory test on your board? Have you checked if the heatsink is seated properly over the components of the board?
  2. @Protxch According to the documentation - SATA1 & the M.2 slot are mutually exclusive. Try connecting the HDDs to SATA 2 and 3 and restart your Helios64 as @Werner mentions, check that the board boots with only the microSD card connected (No HDDs or M.2 cards connected) to rule out an SD card gone bad during the flashing procedure.
  3. sda: Seagate BarraCuda ST2000DM006-2DM164 sd[b-e]: Toshiba DT01ACA100
  4. Can you guys share your experience with disk sleep on the Helios64 + Armbian. In my case I haven't seen the disks sleep - they are always spinning (or so they seem) and never on standby. I have a standalone /dev/sda and a RAID5 array with disks /dev/sd[b-e] (created with mdadm) - and XFS formatted logical volumes on top of these. 'iotop' says that nothing is accessing the disks: 'hdparm -B /dev/sd[a-z]' after each reboot is always: sudo hdparm -B /dev/sd[a-e] /dev/sda: APM_level = 254 /dev/sdb: APM_level = off /dev/sdc: APM_level = off /dev/s
  5. @SymbiosisSystems Since your system is crashing often, my guess is that you're not using it on a PROD environment yet. Have you tried the test builds at the bottom of the downloads page with the newer kernel? You might have better luck with those. I'm using the test build from Nov.13 and it has been very stable. I'm not using OMV just the OS and a few packages that I've configured manually to provide SMB, DLNA & iSCSI services.
  6. @barnumbirr Could you share your custom config for /etc/fancontrol?
  7. Now it makes sense why the fans ramp up when login into the system, hahaha. An algorithm that takes into account both the CPU and HDD temperatures would be a nice solution, prioritizing HDD temps since these need to lower than the temp for the SoC. That being said - is there a way to monitor if the HDDs are idle/sleep and the heads parked to save energy? There are periods of inactivity where it might make sense to stop the HDDs from spinning, I'm sure that this will add a bit of startup/lag when they are accessed after being idle, so far I haven't been able to tell if they are have s
  8. Thanks for the clarification @gprovost. Looking forward to storing the bootloader on SPI - I believe that looking for the 2nd stage bootloader on the microSD is a perfect way to rescue the system in cases it's needed.
  9. @jbergler It's called cockpit - it listens on port 9090 You can install it with: sudo apt -y install cockpit cockpit-networkmanager cockpit-packagekit cockpit-storaged
  10. For anyone looking to build an iSCSI target on their new Helios64, I can confirm that it's working correctly under the test builds for Armbian 20.11. Thanks to @aprayoga for his comment on the pull request, the kernels modules related to LinuxIO have been added to all boards in the Armbian project.
  11. @ShadowDance Thanks for the input regarding the fans. I'll give it a try if the noise goes up on my system once the ambient temperature starts to rise here in couple of months, for now I'm concerned about the dust.
  12. @Jaques-Ludwig, I'm using the default jumper configuration on the Helios64 board.
  13. @Jaques-Ludwig The following steps worked for me to boot from a USB stick. In order to boot from USB try this steps: Boot from the SD card Plug in the USB stick - use command 'lsblk' to see the device name and write it down. Choose option 3 from the main menu of 'nand-sata-install' tool Choose the right destination (device from step 2) Wait for writing to finish and reboot. It's part of the guide. If you did install on the eMMC, then you can write the image used for initial SD-Card to a USB drive and erase the partition table from the eMMC. The b
  14. Hi @Jaques-Ludwig, That page refers to booting once from the SD-Card to install the system onto the eMMC, with armbian-config or directly with the nand-sata-install tool. Afterwards your system should boot without the SD-Card, which is what you are looking to achieve, right?
  15. Yes, you can boot off USB. You need to either have a U-Boot image on the SD card or on the eMMC. From there, if the system partition is not found on the SD Card or the eMMC, it will try to look for it on the USB drives that are connected. My system is booting from a USB drive at the moment - the U-Boot is installed on the eMMC (I erased the partition table afterwards, but the bootloader is still there). If you zero out the eMMC, you loose the bootloader and you need to boot from an SD card. I belive that once we can install the bootloader to the SPI chip you would be