NZJon
-
Posts
7 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by NZJon
-
-
You absolute legend, ebin-dev, for replying to my message 🙌.
I don't appear to have a MergerFS "service" as such -- the mounting, I guess, is handled by FUSE...?
So, I don't have a solution yet, but, I've been doing a lot of reading up on SystemD, so I'm beginning to understand how this might all hang together.
Cheers,
Jon
-
Howdy.
I m running a Helios64 on Armbian 21.02.1 Buster with Linux 5.10.63-rockchip64. I realise this is somewhat old, but it works for me.
I have been using MergerFS to present a big "vritual" storage area on my server:
jon@OXYGEN:~$ more /etc/fstab UUID=a79a14c0-3cf4-4fb9-a6c6-838571351371 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 # "Disk 2" = /dev/sda3 = 8d360e1c-1908-4d8d-8289-2b1c83604950 UUID=8d360e1c-1908-4d8d-8289-2b1c83604950 /srv/mnt/disk2 btrfs defaults,noatime,nodiratime,nofail,subvol=@data 0 2 # "Disk 3" = /dev/sdb2 = eceee45f-5be5-48ba-a928-8f61686923b0 UUID=eceee45f-5be5-48ba-a928-8f61686923b0 /srv/mnt/disk3 btrfs defaults,noatime,nodiratime,nofail,subvol=@data 0 2 # "Disk 4" = /dev/sdc3 = 8ba04a0d-92eb-44e5-a4f0-99ebe2431b22 UUID=8ba04a0d-92eb-44e5-a4f0-99ebe2431b22 /srv/mnt/disk4 btrfs defaults,noatime,nodiratime,nofail,subvol=@data 0 2 # "Disk 5" = /dev/sdd3 = c3f0e61b-67af-4b35-acb8-e6698f8c9f64 UUID=c3f0e61b-67af-4b35-acb8-e6698f8c9f64 /srv/mnt/disk5 btrfs defaults,noatime,nodiratime,nofail,subvol=@data 0 2 # MergerFS - aggregate the mounted disks together /srv/mnt/disk2:/srv/mnt/disk3:/srv/mnt/disk4:/srv/mnt/disk5 /srv/mnt/virtual fuse.mergerfs defaults,allow_other,use_ino,fsname=/srv/mnt/virtual 0 0
I have recently begun exporting this virtual disk via nfs. Nice! It relly is easy to set up, and it does "just work":
jon@OXYGEN:~$ more /etc/exports /srv/mnt/virtual/oxygen/media 192.168.2.0/24(rw,sync,insecure,no_root_squash,no_subtree_check,nohide,fsid=0)
But, when my server is rebooted, the nfs-server.service fails to start:
_ _ _ _ __ _ _ | | | | ___| (_) ___ ___ / /_ | || | | |_| |/ _ \ | |/ _ \/ __| '_ \| || |_ | _ | __/ | | (_) \__ \ (_) |__ _| |_| |_|\___|_|_|\___/|___/\___/ |_| Welcome to Armbian 21.02.1 Buster with Linux 5.10.63-rockchip64 No end-user support: work in progress System load: 3% Up time: 9 min Memory usage: 17% of 3.77G IP: 172.19.0.1 172.22.0.1 172.21.0.1 192.168.2.105 CPU temp: 43°C Usage of /: 41% of 15G [ General system configuration (beta): armbian-config ] Last login: Thu May 23 16:18:16 2024 from 1975:1976:1977:e00:dead:beef:0000:1111 jon@OXYGEN:~$ sudo service nfs-kernel-server status [sudo] password for jon: ● nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2024-05-25 15:36:31 NZST; 10min ago Process: 1210 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Process: 1218 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 1219 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) May 25 15:36:31 OXYGEN systemd[1]: Starting NFS server and services... May 25 15:36:31 OXYGEN exportfs[1210]: exportfs: Failed to stat /srv/mnt/virtual/oxygen/media: No such file or directory May 25 15:36:31 OXYGEN systemd[1]: nfs-server.service: Control process exited, code=exited, status=1/FAILURE May 25 15:36:31 OXYGEN systemd[1]: nfs-server.service: Failed with result 'exit-code'. May 25 15:36:31 OXYGEN systemd[1]: Stopped NFS server and services.Running "$ sudo service nfs-kernel-server start" manually, however, gets it going:
jon@OXYGEN:~$ sudo service nfs-kernel-server start jon@OXYGEN:~$ sudo service nfs-kernel-server status ● nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2024-05-25 16:03:04 NZST; 1s ago Process: 7428 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Process: 7429 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS) Main PID: 7429 (code=exited, status=0/SUCCESS) May 25 16:03:03 OXYGEN systemd[1]: Starting NFS server and services... May 25 16:03:04 OXYGEN systemd[1]: Started NFS server and services.So, to me, it seems that the MergerFS-provided "virtual" filesystem at /srv/mnt/virtual is not ready at the time that the NFS service is starting up.
Does anyone know:
1. whether I can modify the definition of the NFS Service, within systemd, so that it starts up later in the boot process? Am I able to define a dependency on some other filesystem service that has yet to be started?
2. whether I can define something else that gets kicked off late in the boot process, which simply attempts to restart the NFS Server service, in the hope that by this late stage in the boot process the MergerFS location is "ready"?
Many thanks,
Jon
-
Many thanks!
-
Kia ora.
I am aware that the external USB ports on the Helios are able to deliver up to 900mA per port. I am wondering whether it is possible to find a power source inside the Helios64 that would be able to deliver, say, 2.5A at 5v? Maybe somewhere quite soon after the 12v power in...?
🤔
Jon
-
Kia ora, oksion,
Many thanks! That is just awesome 🙏 I now just need to wait the 2-8 weeks for delivery to Aotearoa New Zealand 😉
Jon
-
Hello.
So, really sorry to hear that Team Kobol are disbanding. Many thanks to all who worked so hard to put the Helios64 together. I am really pleased with my Helios64, and am grateful for being able to get hold of one of these. Thank you! 🙏
What with one thing an another, I never got hold of a UPS battery; the battery couldn't be shipped with the original shipment, due to restrictions on shipping Li-Ion batteries; and then the additional postage costs for sending the battery seperately were prohibitive for Team Kobol, which I completely understand, so I chose not to pay the extra for the battery. However, it would be really useful for me to build one of these, from locally sourced components (I live in New Zealand).
The wiki page here (https://wiki.kobol.io/helios64/ups/) mentions that it is possible for users to build their own battery if they keep the specifications correct. I want to give this a go, so that I can get the UPS working on my box.
So. I can source Panasonic NCR18650BD cells here in New Zealand. So that's step one done.
The protection IC, HY2120, is a little vague. The Hycon website here (https://www.hycontek.com/en/products-en/3180) lists several variants of the IC. And while sellers on AliExpress list these as being available, I don't know the exact spec to select. Does anyone know?
Tthen, there is mention of a thermistor to monitor the cells temperature. Here, I don't know where to begin. What temperature is regarded as the threshold? What particular thermistor should I be looking for...? Many questions.
And then, finally, there is getting the correct connector, to plug the home-made UPS battery onto the board. I assume it's a Molex type connector, but again, I don't kow enough in order to get the correct one.
I am more than happy to give this a go myself, if anyone is able to give me a few specifics about what I should be purchasing.
Many thanks to you,
Jon
How to fix nfs-server.service failing to start on boot, due to slow MergerFS folder being exported
in Rockchip
Posted
Kia ora ebin-dev,
Just dropping by to say, again, a big thank you for helping me out. 🙌
I ended up writing a "dummy service" that the nfs-server depended on. I had noticed that it took about 15-20 seconds for a simple `ls -al` to produce an output on the nfs-shared location, so the dummy servce I wrote simply performs a `ls -al` and waits 5 seconds, until a successful output is produced. Then, the nfs-server service is able to STAT the file location... and it starts up properly.
Probably not the most elegant way of getting things to work... but at least it works for me!
Thanks again,
Jon