Jump to content

Search the Community

Showing results for tags 'helios64'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Khadas VIM4
    • Radxa Zero 2
    • Odroid M1
    • NanoPi R5S
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Discord


Location


Interests

  1. Hi there, I love my Helios64 to death. I'm running MooseFS CE and MooseFS PRO. The problem is I'm absolutely hammering it with I/O and it's consistently hard crashing, and no fix I've tried helps. Should I revert to the older kernel version or something? Or is this a useful test case...
  2. I'm experiencing a lot of issues on 5.10.x and thought a dedicated thread would make sense. I've posted some reports in other threads too. Note that 5.9.x is much more stable for me, but not without problems. I'm also experiencing what I can only refer to as boot stalls, i.e. nothing happens. Occasionally when these stalls happen there is a rcu: INFO: rcu_preempt detected stalls on CPUs/tasks trace printed. This happens on both 5.9 and 5.10. Looking at where it stalls it seems to be around the time the hardware optimizations are applied and/or graphics modules are loaded. I have currently blocked the graphics modules from loading and have moved hardware optimizations to initrd so that they will be performed earlier. Time will tell if this has an effect or not. Distro: Armbian Buster 21.02.3 Kernel: 5.10.21 /proc/cmdline: root=ZFS=rpool/ROOT/debian rootwait rootfstype=zfs earlycon console=ttyS2,1500000 consoleblank=0 loglevel=7 ubootpart=794023b5-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u libata.force=noncq earlyprintk ignore_loglevel cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 Filesystem: ZFS 2.0.3 (root on ZFS, boot from eMMC) LUKS: Yes, full disk encryption (HDD -> Partition -> LUKS -> ZFS) IO scheduler: None Panic during boot: Unable to handle kernel write to read-only memory at virtual address ffff8000100d3a54 Kernel bug (system left inoperable): Internal error: Oops - BUG: 0 [#1] PREEMPT SMP And the latest issue: WARNING: Pool 'rpool' has encountered an uncorrectable I/O failure and has been suspended. Note: The warning above was only printed the latter time, but the same symptom occurred two times within two days. I.e. everything is stuck in iowait and it's basically impossible to do anything with the system. This only happens on 5.10, and happened two times within two days. On 5.9 (ZFS 2.0.3 as well) there is no such issue. Anyway, I'm back on 5.9.14 for the time being. Just finished a full scrub of the ZFS filesystem as well, no issues or errors.
  3. I thought I'd rebuild the NAS with the latest image in the hope that it would be more stable. Unfortunately my hopes were in vain. I was in the middle of doing an rsync and it crashed with a kernel panic. Had a look on the forum and implemented the two suggestions of limiting the cpu to 1200MHz and tweaking the voltages. CPU @ 50c as reported in the login header. Anyway after updating the setting I reboot it and it crashed immediately ! The same SMP issue that seems to have been plaguing this board since release
  4. I’ve googled it but can’t decide, the drive works just fine (it’s the 1st of the three disks I have in the box), no performance issues when copying from/to the box. I’m currently on “Armbian 20.11”, barely get the time to play with the setup due to work assignments, plan to update soon. Thanks! (PS. Newbie here) [ 13.298079] ata1: softreset failed (1st FIS failed) [ 18.449169] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 18.467303] ata1.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 18.467315] ata1.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 18.470029] ata1.00: configured for UDMA/133 [ 18.470721] scsi 0:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 18.472237] sd 0:0:0:0: [sda] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 18.472247] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 18.472299] sd 0:0:0:0: [sda] Write Protect is off [ 18.472309] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 18.472393] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 18.580573] sda: sda1 [ 18.583350] sd 0:0:0:0: [sda] Attached SCSI disk [ 18.949151] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 18.959809] ata2.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 18.959822] ata2.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 18.962526] ata2.00: configured for UDMA/133 [ 18.963133] scsi 1:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 18.964436] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 18.964451] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 18.964520] sd 1:0:0:0: [sdb] Write Protect is off [ 18.964534] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 18.964651] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 19.017200] sdb: sdb1 [ 19.019847] sd 1:0:0:0: [sdb] Attached SCSI disk [ 19.441176] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 19.450989] ata3.00: ATA-10: ST6000VN0033-2EE110, SC60, max UDMA/133 [ 19.451001] ata3.00: 11721045168 sectors, multi 0: LBA48 NCQ (depth 32), AA [ 19.453715] ata3.00: configured for UDMA/133 [ 19.454064] scsi 2:0:0:0: Direct-Access ATA ST6000VN0033-2EE SC60 PQ : 0 ANSI: 5 [ 19.455164] sd 2:0:0:0: [sdc] 11721045168 512-byte logical blocks: (6.00 TB/5 .46 TiB) [ 19.455178] sd 2:0:0:0: [sdc] 4096-byte physical blocks [ 19.455248] sd 2:0:0:0: [sdc] Write Protect is off [ 19.455262] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [ 19.455378] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, does n't support DPO or FUA [ 19.507285] sdc: sdc1 [ 19.509063] sd 2:0:0:0: [sdc] Attached SCSI disk [ 19.767590] ata4: SATA link down (SStatus 0 SControl 300) [ 20.079588] ata5: SATA link down (SStatus 0 SControl 300)
  5. Hi, Is TrustZone being utilized at all? I can't seem to find any documentation on what execution level Kobal is running at during boot. I assume it's dropping the Kernel into EL2? Cheers
  6. Hi, I would like to make backup(s) of my system. The system (debian) is installed on sata SSD @ slot 1. I would like to have the backup of the system written to zfs pool on the other slots as an image. Which in case of system SSD failure, I could write back to a new SSD installed on the same slot 1, by booting to a rescue system from micro sd card. Have this kind of functionality already been implemented? Or parts of it? Linux has a bunch of backup solutions, but I suspect they might not work with the helios64 box (sd card, internal ssd). And my only helios64 box is in "production" use, so "trial and error" method is not the first option in my mind...
  7. Hi all. Some time ago, in the release notes of a past Armbian version, I remember reading that the network LED should now be enabled by default and associated with eth0. Despite always keeping my Helios64 as up-to-date as possible, mine never lit up, but I didn't think much of it. Today I decided to investigate why, and I'm not sure where to go from here. First things first, the LED works, it's not a hardware issue. I can echo 1 and 0 to the LED path (/sys/class/leds/helios64:blue:net/brightness) and it lights on and off as expected. From what I can tell, this LED, along with the heartbeat one, is enabled by the Systemd unit helios64-heartbeat-led.service. When I check for the status of the unit, I get the following output: ● helios64-heartbeat-led.service - Enable heartbeat & network activity led on Helios64 Loaded: loaded (/etc/systemd/system/helios64-heartbeat-led.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2021-03-13 00:30:52 GMT; 8min ago Process: 3740 ExecStart=/usr/bin/bash -c echo heartbeat | tee /sys/class/leds/helios64\:\:status/trigger (code=exited, status=0/SUCCESS) Process: 3744 ExecStart=/usr/bin/bash -c echo netdev | tee /sys/class/leds/helios64\:blue\:net/trigger (code=exited, status=1/FAILURE) Main PID: 3744 (code=exited, status=1/FAILURE) Mar 13 00:30:52 nas.lan systemd[1]: Starting Enable heartbeat & network activity led on Helios64... Mar 13 00:30:52 nas.lan bash[3740]: heartbeat Mar 13 00:30:52 nas.lan bash[3744]: netdev Mar 13 00:30:52 nas.lan bash[3744]: tee: '/sys/class/leds/helios64:blue:net/trigger': Invalid argument Mar 13 00:30:52 nas.lan systemd[1]: helios64-heartbeat-led.service: Main process exited, code=exited, status=1/FAILURE Mar 13 00:30:52 nas.lan systemd[1]: helios64-heartbeat-led.service: Failed with result 'exit-code'. Mar 13 00:30:52 nas.lan systemd[1]: Failed to start Enable heartbeat & network activity led on Helios64. Looking into the unit's source, I can see the line where this fails: ExecStart=bash -c 'echo netdev | tee /sys/class/leds/helios64\\:blue\\:net/trigger' And sure enough, there is no "netdev" inside /sys/class/leds/helios64:blue:net/trigger: $ cat /sys/class/leds/helios64:blue:net/trigger [none] usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport mmc1 mmc2 disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic stmmac-0:00:link stmmac-0:00:1Gbps stmmac-0:00:100Mbps stmmac-0:00:10Mbps rc-feedback gpio-charger-online tcpm-source-psy-4-0022-online I'm not sure why it's not there or how does that get populated. I'm running Armbian Buster 21.02.3 with LK 5.10.21-rockchip64. Any help will be much appreciated.
  8. Hi Folks I am about to set up my helios64 nas on an imac mini m1 or an older intel imac mini. Buying the NAS was risky for me as I am a newbie to Linux. Nevertheless fortune favours the brave and all that. I am having difficulty finding the optimal set up of my helios64 NAS Do I buy a m.2 sata ssd and 4 western digital red pro hard drives? Do the hard drives have to be identical? Assuming I am buying Western Digital WD Red Pro NAS 4TB HDD, WD4003FFBX whats the best m.2 sata to pair up with these? I do have the 2.5 inch adapter.
  9. Hi, i have successfully installed my new helios64 and enabled zfs. Everythings works so far, but it seems I'm missing something "important" in regards to ZFS. I did the following tests: I took one of my WD 4TB Plus drives (in slot 3) and formatted the disk with a) ext4 (mkfs.ext4 /dev/sdc) b) btrfs (mkfs.btrfs /dev/sdc) and c) zfs (zpool create test /dev/sdc). Based on these 3 formats I did a "dd if=/dev/zero of=test2.bin bs=1GB count=5" to measure write performance and a "dd if=test2.bin of=/dev/null" to get the read performance (all tests were done 3 times, results averaged) The results I got look like this: a) ext4 ... avg write 165MB/s - read 180MB/s b) btrfs ... avg write 180MB/s - read 192MB/s c) zfs ... avg write 140MB/s - read 45MB/s (!) So while ext4 and btrfs produce for sequential read / write pretty much the same (and expected) results, zfs seems to be significantly slower in write and dramaticially slower in read performance. I need to admit, I'm new to zfs ... but is this expected / normal? zfs has tonns of parameters to tune performance - are there any settings which are "needed" to achive almost the same values as e.g. with btrfs? (honestly, I expected to perform zfs equally to btrfs - as zfs should be the more "mature" file system ...) thanks! A
  10. My Helios64 has been booting from an M.2 drive since I got it, and while I've been doing regular apt-upgrades I've been ignoring the bootloader. This post suggests that could be a problem, so I figured I'd upgrade the bootloader through armbian-config. Trouble is, I can't. I can load armbian-config without error, but when I go into System there's no Install option any more. All I have are Freeze, Nightly, Lowlevel, Bootenv, CPU, Avahi, Hardware, Other, SSH, Firmware, ZSH, Default. Is there another way to ensure the bootloader is up-to-date?
  11. Thought I'd download the latest image in the hope that it might be more stable ... kernel panic on reboot, booted second time and then whlst trying to update kernel panic again. This board seems to be so unstable it's bascially unuseable
  12. Hello, i want use and control kodi on my Helios64 with the tv remote. Have someone experiance with that and a recommendation for cables or usb c dockingstation? thank you
  13. Curious if anybody else with tick-stop error? Not certain if this applies; the only change is installing Docker and Pi-Hole containerized. A quick read seems related to a soft interrupt of 8; - The only solution I could find by googling; is: "Add nohz=off to the kernel parameters during boot to disable it." Can I safely ignore this error message; or should I do this nohz=off to the kernel parms?
  14. FloBaoti

    Unable to boot

    Hi, On an up-to-date Helios64, around 50% of boots are stuck at "Starting kernel ...". As device is having kernel panics every day, it reboots and then sometimes can't start, stuck on this. When will we have a stable device ? I can't understand selling devices which just can't run !
  15. Hey there, so I was curious is there an easier way to make microSD take precedence in the boot order then having to futz with jumpers? Wanting to try out a new distro on microSD before deciding to make the switch and flash it to eMMC. If I do futz with jumpers I'll still be able to mount and write to the eMMC correct?
  16. I'm having an aggressive memory leak issue I can't place: Within 5 minutes the 4GB are full. htop and top don't show a massive program growing unbouded. `df` doesn't show a tmpfs that is too large. Only `slabtop` is imforative: OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 26638624 26638624 99% 0.12K 832457 32 3329828K kmalloc-128 So `kmalloc-128` is growing without bounds. As I understand it kmalloc is a collection of smaller memory allocations? I've tried using a previous kernel version (5.10.16 and 5.10.12) but nada. I've disabled docker, and that along with omv were the only services running. Any suggestions would be great!
  17. I have installed OMV via armbian-config (software). After that I tried to install Nextcloud the same way. In the process I noticed that Apache2 does not start due to a port mismatch (port 80). I was able to determine that obviously the web server nginx is already installed and used for OMV. Can someone please explain to me if this is intentional or if I made a mistake during the installation? Is it possible not to install OMV and Nextcloud in parallel? How can I solve this?
  18. Hello, After I first installed my Helios64, I feared the 16Gb eMMC would be quickly filled. So when I used nand-sata-install, I chose to boot from eMMC but to have the root filesystem on a 500Gb sata drive. I have now second thoughts about it, since I realized that the OS take less than 8Gb, AND I'd like to add a 5th disk to my raid Halas nand-sata-install doesn't seem to work on an already moved filsystem. lsblk show this for the eMMC and the root partition peyo@helios64:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465,8G 0 disk └─sda1 8:1 0 465,8G 0 part / ... mmcblk2 179:0 0 14,6G 0 disk └─mmcblk2p1 179:1 0 14,4G 0 part /media/mmcboot And /etc/fstab shows this UUID=f2d7d6e7-902c-44dc-bdae-aedeb4495385 /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=0fcd9a2c-9a46-4a5e-a0f5-e407bd34e8fb / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 ... And in /media I have this peyo@helios64:~$ ll /media/ total 8 drwxr-xr-x 3 root root 4096 déc. 6 11:31 mmcboot drwxr-xr-x 2 root root 4096 déc. 6 11:31 mmcroot Would it be so simple as 1 - rsync all that's on my present / (except for the NFS export and /tmp)? 2 - changin /etc/fstab to this UUID=f2d7d6e7-902c-44dc-bdae-aedeb4495385 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 3 - reboot (with crossed fingers) Thanks for you help
  19. I’m helping my friend set up Helios64 with OpenMediaVault as a media server. We’d manage to set it up as per your documentation mentioned on your wiki page but are stuck on SD-Card to eMMC migration. As after migrating with no error so far we’re still unable to boot the system without the SD-Card in Helios64. We still couldn’t figure out what could be the problem? Can you guys help?
  20. Hi all, i have install on armian buster 10 on my Helios64. After the installation and the first config OMV 5 i see only two plug ins with 0 Bytes??? I have no experience and I'm asking for help!
  21. 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
  22. kabo

    Helios64 won't boot

    Hi, For some reason my Helios64 took a nose dive today, so I hit the reset button and it wouldn't boot up. Plugged in to the serial console and this came out: I'm guessing the relevant lines are libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! ... ERROR: Did not find a cmdline Flattened Device Tree Loading Ramdisk to f4f09000, end f5ee4ba4 ... OK FDT and ATAGS support not compiled in - hanging Any ideas on what to do from here please? I'm booting from an SD card which I have checked that it's OK by plugging it into my stationary computer and checking the fs. Crossing my fingers that there's just some command I need to run to generate some file and it'll just work again...
  23. Dear H64-Friends, I've got the Armbian Debian installed with Linux Kernel 5.10 and Open Media Vault (OMV). I just use the basic functions for backing up files, nothing extraordinary. I am wondering what's the best strategy to update the Helios64 system concerning stability and getting no errors for backing up files (automatic USB-Backups). Keep it always up to date if there's an update available in OMV? Or just wait some weeks?
  24. When there is a kernel panic the fans stop which causes the HDD and CPU temperatures to rise unchecked. I've just come back to find my board has crashed again and the HDD temperatures had risen above 60c which is not good. Is there a watchdog or boot setting to automatically reset the processor after a kernel panic ?
  25. Just applied the latest update to my Helios64, here is what apt reported: The following packages will be upgraded: armbian-config armbian-firmware base-files device-tree-compiler file iproute2 libcairo2 libgnutls30 libgnutls30:armhf libmagic-mgc libmagic1 libnss-myhostname libpam-systemd libsystemd0 libudev1 linux-buster-root-current-helios64 linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-helios64-current systemd systemd-sysv udev unzip This went just fine until it tried to setup systemd, the Helios then lost all network connection: Tried rebooting, no luck. Can't get a serial console up and running as it won't go past 'Starting kernel...' The blue 'System' LED is on but doesn't blink. What can I do to help debug/fix this?
×
×
  • Create New...