• Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by bunducafe

  1. Just a quick question: Is there any community related development regarding the helios64? I know there is no official support but I am curious where to look whether there are some coders who do so. When setting up the helios from scracth I found the archived download page that contain the old images and of course I can use them. But I just wonder if there is any form of development. Otherwise I also will have too look into compile kernels myself
  2. Since the emmc bug I am kind of reluctant to put the OS again on that device. I have gone back with SD Cards that I can easily backup once in a while. That said I always have a running backup.
  3. I am working with: Linux helios64 5.10.63-rockchip64 #21.08.2 SMP PREEMPT Wed Sep 8 10:57:23 UTC 2021 aarch64 GNU/Linux I have snapraid configered via the OMV interface but MergerFS and LUKs manually because the plugins were not present at the time but I am not sure if this really does any difference. Beyond that I am using some Dockers like Airsonic, Jellyfin, Nextcloud. And the ondemand governor is now between 400-1800MHz and runs all the tasks (Snapraid + rsync + smart on a weekly basis) smoothly. My current uptime now is 21 days.
  4. Since 4 weeks now I am runnign the helios64 together with OpenMediavault 6 with the full CPU capacity and ondemand governor. Before I had always problems when doing an scheduled task but with OMV6 the problem seems to be solved. I am quite pleased now with the performance and a rocksolid NAS.
  5. @Amix73 What a spirit! That is really great! I am kind of the same as you with not too much experience in coding and debuggind and time to do everything... so I will do a donation next week (is there a Link somewhere to be found how to do this?). And: I don't really understand why people here selling there units
  6. Hm, that always depends on the setup. I am in the Apple universe and I find that SMB works a bit faster on OMV6 but as you can edit the preferences yourself there should not be too much of an issue to modify this to your needs.
  7. Go ahead, OMV6 works fairly well with the Helios64... there are some bits and pieces that are not completely ported (plugins for example) and some need a bit of adjustment whatsoever. But all in all it is okay. I am running OMV6 together with SnapRaid. MergerFS and Luks I am running outside of OMV as I do find it easier to customize for my needs.
  8. Okay, my bad. I just should think a little bit more beforehand then I could solve things myself. Well, as I was affected by the malfunction of the eMMC after having upgraded the Linux kernel i did format the eMMC but did not pay attention that it still able to boot from that partition. A look into the Troubleshooting section would have solved everything within minutes: https://wiki.kobol.io/helios64/troubleshoot/ Anyhow. I can now turn off the machine as expected and everything's fine.
  9. @Heisath Yes, that's exactly why I am "puzzled". I have to get the console going then which in the past did not work well together with my MacBook Air. Anyhow, let's give it another try... Beyond that: I did a fresh install with armbian and further with a fresh OMV. WOL is not enabled nor is the GPIO Auto-Power On. I will report once I found the culprit or if I need any further assistance
  10. I'd love to bump this thread one more time as it really annoys me. I was reinstalling OMV but it seems that it is not the culprit of the unwanted boot after a shutdown. Yesterday I installed the alpha OMV6 and it ran fine. I shut it down over night and ejected also the sdcard but this morning the blue leds a are flushing again I did format the eMMc, too beforehand so I have absolutely no idea why the helios64 repeatedly comes up again. Why does it not stay shut down? And: Where do I have to look in order to get the server to behave like I want it to?
  11. I am currently away from the office, so I can only verify that once I am back in a week or so... But as I did not encounter that issue beforehand I wonder if it can occur "just" out of the blue...?! Okay, just connected via VPN: No alarm set, so RTC is not the culprit.
  12. Hi folks, I am puzzled. When I am away for a few days I usually shut down my nas. It does indeed shut down but over night comes up again. Now I would like to know what triggers that unwanted restart here... I am currently on 21.08.3 Buster with Linux rockchip64 5.10.63 and do have OMV running... I could unplug the battery next time but I'd rather solve the issue the correct way. It's strange to me because I did not change any system parameters in OMV or via SSH. I do believe that an update to the latest kernel did mess things up. Where do I have to have a look?
  13. Hi folks, I am wondering if somebody with a mac enviroment has a decent / performant samba connectivity? After I upgraded to Big Sur I have severe issues with the samba protocol when accessing my shares on the helios running openmediavault. I know that Apple had made some changes with samba but there might be some users that dug a little bit deeper and could give me a hint. I did try it with different settings in the extra options over the past weeks but with no luck so far. Sidenote: Also NFS is terribly slow and laggy. I am back with AFP connection now that does the job perfectly and fast.
  14. Thanks @SIGSEGV for your post. I do very much appreciate it because at the end it comes down to exactly that: There are a few very keen developers and a bunch of users who like to use the software with their units - in that case the Helios64. But in return are not really willing to contribute. To be a bit more subjectively: I would love to contribute and I do so once in a while if I stumble upon some problems I could solve myself. Mostly related to a running system with OMV and Armbian If it comes to testing kernels and debug I am out of the game because I did not even manage to get the console working. That's mainly because I am with MACs here at the office and I simply could not get the console running on none of my machines. So on this side I would consider myself a complete noob which makes debugging kind of impossible to me. I might get a separate laptop with a non-mac unix system in the future just for this purpose. Meanwhile I am a bit far off in giving support on that kind of level unfotunately. That's also a reason why I am rather reading through the forum and usually not be one of the complainers as I know how much work the devs put in here and how good it usually works. A hickup from time to time is totally fine with me.
  15. If you do fiddle around keep us posted, would be great to know if it works... I am somehow reluctant to try it at the moment as I need a running system. Because the mentioned workaround (updating bootloader) does not make the emmc fully writeable I would rather stick to the sd card at the moment.
  16. Is there any need to format the emmc and do a rsync? I mean, if I roll back and the i/o errors on the emmc are gone shouldn't it boot flawlessly again and preserves the exact same state as before the update?
  17. Thanks. As the sd card is working flawlessly I am not in need to do so right now. And with the emmc issue I cannot write on that thing anyway. But just in case: It's done with "dpkg -i" I suppose. No specific order, right?
  18. Uh, I should have followed this thread a little bit earlier as I ran into the emmc issue (no write permission) and the system does not come up and I cannot manipulate anything. For now I am back with sd cards and will probably stick to it as I can make clones from the sdcard a bit easier with my setup here. Is there an easy way to roll back the actual kernel?
  19. I am with Buster, but regarding the ondemand governor: I have set them from the very beginning from 400 and 1400 and the system has been running rocksolid after this.
  20. Yes, just received that email, too. What a pity. I am quite satisfied with my Helios64 and I do hope it will last quite a bit... in the meantime I do hope that this forum remains the best source for trouble shooting. Thank you guys for your beautiful machines. Maybe it's there is a way to revive everything in the (not too far) future. Would be great!
  21. bunducafe

    Random reboots

    I had a similar issue with random reboots. Did DM @axelroy directly and also "tweaked" the system. I am running the helios now for almost 2 weeks without issues with the following settings: Min CPU speed = 400 MHz Max CPU speed = 1400 MHz CPU governor = on demand So it seems that the helios was rebooting when having to deal with intensive tasks - in my case: performing a SnapRAID scrub. Anyhow: Now I am at maximum speed of 1400MHz whereas the helios could perform even on 1800MHz. The question is if this is a problem by design? Or is there a way to fix it in order to let the machine run full CPU speed and performance governor? I am happy with the machine, no doubt, at the end this is rather a question of how I can achieve the maximum speed if needed.
  22. I was just wondering, which would be the most elegant way to get the system backed up if everything resides within the eMMC. If I would not have moved the eMMC route and still use the SD card as my OS I would just clone the SD card. Hence this is not possible is there any tutorial to get a bootable clone of the eMMC?
  23. After fiddeling aroud I finally have the helios64 also running solid. I never had any freezes before just some problems with getting the system to boot from the emmc device and, see other thread, with setting up OMV - LUKS - Snapraid - UnionFS I am currently under: Linux helios64 5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 GNU/Linux OMV Version 5.6.2-1 (Usul) So I would say that OMV is not the culprit out of the box. The system works fine but it always depends on what kind of plugins you are using etc. So far I have no docker installed here but I certainly will do that again. I do recommend the OMV Backup Plugin so I can boot from the latest stable release via SDcard if I mess up with something. That's also nice.
  24. Hi folks, just a heads up in this thread (maybe related to others experiencing boot issues with Helios64 and OMV5): If you use the setup: OMV5, Multiple Hdds, LUKS encryption + UnionFS then it is very likely that the machine does not come up instead is booting into revocery mode. That's because it cannot find any mountpoints because of LUKS. In order to get the helios booting again you have to add a "nofail" into the mergerfs option. Unfortunately the merferfs pool does not getting mounted automatically once you decrypted the hdds within LUKS Plugin. That's a bit of a nuisance but it is bearable if you do not boot your machine every day. In my case I had to remove the nofail, the mergerfs did mount immediately and then I did put the nofail in again. There might be a more elegant possibility but at least it is a remedy to get the helios working again. Jump over to the OMV-forums and do a search for LUKS + UnionFS + nofail and you find several threads about that issue. I have no idea if it is better to swith to the merferfsfolder plugin because I have no knowledge so far if I just can change the plugins without any errors.
  25. At least I could get it booted again. I did a clean install onto a fresh SD card with the latest Armbian-Image kernel 5.10. It did boot up but of course I am losing all my configs with OpenMediavault etc. That's the output of the dmesg, there seems something wrong with both mmc and sd. How can I solve that issue in order to get a system that works and where I can then do all the config with OMV and after that reboot / shutdown and boot again...?!