New image: OMV_3_0_70_Odroidxu4_4.9.23.7z
Problem is that monitoring is not disabled since the RPC calls running in the chroot environment failed:
Code
{"response":null,"error":{"code":0,"message":"Failed to connect to socket: No such file or directory","trace":"exception 'OMV\\Rpc\\Exception' with message 'Failed to connect to socket: No such file or directory' in \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc:140\nStack trace:\n#0 \/usr\/sbin\/omv-rpc(107): OMV\\Rpc\\Rpc::call('perfstats', 'set', Array, Array, 2)\n#1 {main}"}}
{"response":null,"error":{"code":0,"message":"Failed to connect to socket: No such file or directory","trace":"exception 'OMV\\Rpc\\Exception' with message 'Failed to connect to socket: No such file or directory' in \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc:140\nStack trace:\n#0 \/usr\/sbin\/omv-rpc(107): OMV\\Rpc\\Rpc::call('config', 'applyChanges', Array, Array, 2)\n#1 {main}"}}
So I move those 'omv-rpc' calls either to Armbian's firstrun function or you might tell me how I could achieve the same by fiddling with config files (XML?) again?
Wrt consumption numbers unfortunately I mixed two measurement setups: those numbers on Github in Armbian's documentation repo are without PSU (I used a Banana Pro as 'measuring PSU') and the XU4 numbers were done at the wall (so including the PSU which can make a huge difference). Let's not focus on that now, I already ordered another cable I need to measure XU4 consumption more reliable (and between PSU and board).
To sum it up:
- the above image should be fine but monitoring has to be disabled in the UI
- I/we need a way to reliably disable monitoring at image creation time (or in firstrun function -- this is the next thing I'll test now)