18 18

About This Club

Dedicated section for talk & support for the Helios4 and Helios64 open source NAS. Lead and moderated by the Kobol Team.
  1. What's new in this club
  2. This issue reoccurred after upgrading from Armbian 21.02.3 to 21.05.1 with today's updated packages On 21.02.3 with kernel 5.10.21-rockchip64, everything worked flawlessly for months. On Armbian 21.05.1 Buster with kernel 5.10.35-rockchip64, whenever I try and stress the 2.5gbps port, it crashes immediately and results in the following dmesg output: May 11 08:52:14 helios64 kernel: ------------[ cut here ]------------ May 11 08:52:14 helios64 kernel: NETDEV WATCHDOG: eth1 (r8152): transmit queue 0 timed out May 11 08:52:14 helios64 kernel: WARNING: CPU: 4 PID: 0 at net/sched/sc
  3. Hi, First using my Helios4 after I left her in my storage room. I have installed and running open media vault. I sometimes wanted to shutdown the NAS. I shutdown using sudo poweroff. Is the a soft method to turn it on again? I currently turn it on using the power switch. Regards,
  4. I'm running a Helios4 NAS with OMV 5.6.6-1 and ZFS 2.0.3. After running for approximately a week it becomes unresponsive - OMV login shows a blue screen but doesn't get to login page, SSH timeout and serial login just keeps going back to the login prompt without asking for the password. Repowering the unit (physically disconnecting the power because there is no way to shut it down gracefully) brings it back to life and it runs again for a week or so before the same thing happens again. I'm not quite sure where to start troubleshooting this. Any ideas ?
  5. I'm using both the 1g and 2.5g nics. Before my recent reinstall, using OMV, the 2.5g NIC would constantly drop, and after a while it just stopped working completely. After reinstall without OMV it has been solid. Not sure if it was OMV causing the issue, but its the largest difference between my 2 installs.
  6. ...now i got the same .... 5 SDD SanDisk SDSSDH3 2T00 but yet only with one disk. no zfs but snapraid with daily check and scrub [Sat May 8 20:16:25 2021] ata4.00: exception Emask 0x10 SAct 0x80000 SErr 0xb80100 action 0x6 [Sat May 8 20:16:25 2021] ata4.00: irq_stat 0x08000000 [Sat May 8 20:16:25 2021] ata4: SError: { UnrecovData 10B8B Dispar BadCRC LinkSeq } [Sat May 8 20:16:25 2021] ata4.00: failed command: READ FPDMA QUEUED [Sat May 8 20:16:25 2021] ata4.00: cmd 60/00:98:40:0d:fa/04:00:56:00:00/40 tag 19 ncq dma 524288 in
  7. For people running fine, are you using 2.5G NIC ? I do, and this interface crashes every few days. I setup a cron to check every minute and down&up it if necessary.
  8. had to install kernel headers and reinstall zfs and then it worked! thanks! let's see how it goes now...
  9. dmitri don first of all thanks so much sharing the third command this fixed my ZFS in OMV5!! I installed omv https://www.youtube.com/watch?v=M_oxzpvMPTE and also the extras as per the video above. https://wiki.omv-extras.org/ commands: wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash nano /etc/apt/sources.list #add these lines to your file. #---------------------------------------------------------------------------------------------------- deb http://deb.debian.org/debian bu
  10. @hartraft Yeah you could try to update the uboot on the microSD card using your spare linux computer.(Note: This can mess up your sdcard if you do it wrongly) You will need again to mount the microSD. cd <sdcard-mount>/usr/lib/linux-u-boot-current-helios64* dd if=idbloader.bin of=<sd-card device> seek=64 conv=notrunc dd if=uboot.img of=<sd-card device> seek=16384 conv=notrunc dd if=trust.bin of=<sd-card device> seek=24576 conv=notrunc where <sd-card device> is something like /dev/mmcblk1
  11. Did you follow https://wiki.kobol.io/helios64/software/zfs/install-zfs/ and also installed zfs-dkms ?
  12. Hello, Followed instructions and installed zfs, rebooted, installed all updated via apt update and apt upgrade, rebooted and situation is like this: root@helios64:~# zpool status The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. root@helios64:~# modprobe zfs modprobe: FATAL: Module zfs not found in directory /lib/modules/5.10.21-rockchip64 root@helios64:~# apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done zfsutils-linux is already the
  13. @gprovost I took a quick look at your previous reply in the thread. It looks like I have the Rockchip blob (line "DDR Version 1.24 20191016") since I haven't updated since 2020.07 LK 5.9.X and initially my LK 5.10.X upgrades had issues. Is there a way to update the UBoot without losing the rest of the system? Perhaps that was my issue and since I didn't reboot in a while, I avoided that scenario...? Modified the armbianEnv.txt on a spare Linux machine. Output below:
  14. Just a heads up that I reinstalled my Helios 64 with the latest armbian buster (currently running from SD) and it has been running solid as a rock for 7 days. No longer using OMV and I don't really miss it
  15. @hartraft Could you modify /boot/armbianEnv.txt and add/modify following lines: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel If you are booting from eMMC, you will need to first boot from a fresh image on microSD, then mount the eMMC to modify /boot/armbianEnv.txt
  16. Okay... So I had to jinx it... After 100 days of uptime, I had to do some electricity work in the house. Either the Helios64 shut-down after the UPS was spent or it rebooted / shut-down. Now I can't boot the thing back up anymore. Connected through picocom and it doesn't get past "Starting kernel". Tried without any disks attached, same thing. Similar to another thread, the LAN LEDs don't light up (obviously). Any ideas?
  17. Mine is running just fine for months now. Just upgraded it (kernel 5.9... to 5.10..) and it's still running fine. openmediavault 5.6.5-1 Mirror Raid with XFS and 2 disks NFS, SMB Shares Welcome to Armbian 21.02.3 Buster with Linux 5.10.21-rockchip64
  18. 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.
  19. Maybe check if on Infuse app has some settings to tweak the caching. Did you check on Helios64 if something is happening while streaming those MP4 file ? (use dmesg -w to see if anything wrong happen). You could also try with the 1GbE (eth0) interface this way you can narrow down the issue.
  20. 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.
  21. Dear all, I am highly interested in the Helios64 and registered for the next batch. Here are a few questions, I hope that your guys can answer. The OS is Embedded Debian I assume. Questions are quite simple: 1) Hard drive numbering on startup Under Debian, the hard drives in a RAID array are renumbered on each startup by random: /dev/sda, /dev/sdb, etc ... This means that if drive /dev/sdb fails ... it is not necessarily the second hard drive in the bay. I already lost a RAID server extracting the wrong disc in an array. Then
  22. Hi folks I'm running a fresh install of the Debian branch with 5.X Kernel branch. I got 2 new 4TB HD setup with MDAM in RAID 1 mode to store my photo and documents with Syncloud also running on the HELIOS64. I Got also a 2,5 Sata drive mount and share via Samba to my home network. My Helios64 is plugged via the 2,5GB Ethernet port directly to my Router on the 2,5GB port. I didn't fix the hardware bug, but if I understood it's not necessary in my case ( 2,5GB Ethernet on a 2,5GB Ethernet Router) My problem is that on the same router I got an Apple TV (on e
  23. Wanted to extend another gesture of support for taking a break. Hopefully the market will be more flexible to enable you guys to push a new product in the coming months.
  24. current rating != startup current. elementary electronics knowledge
  25. As i said in the original post, I tried 2 hard drives, the first one being rated for 700mA.