Post #6 is response to post #4 which talks about "file systems" tab and not about Dashboard
I didn't look at the code but I assume it is same thing that causes the root filesystem to be visible.
Hmm this will make every thing even more confusing.
How? It is required for these plugins. I'm not sure why this is a big deal. If you don't install the sharerootfs plugin, then you aren't using the root filesystem anywhere in the web interface. I was the one who asked for the root filesystem to be visible. So, I do think it is handy.
I'm using a laptop not a RPi.
System details are always helpful. Seems strange that your system even boots then. How did you install OMV? This is what you should see:Code
I also use a NTFS drive, although just for backup purposes.
How would it help you?
And you cannot change environment variables to use the new ntfs3 module. The bigwrites option does not work and the mount filesystem type needs to be changed from ntfs to ntfs3.
I have a HC2 which can house one 3.5" drive. But it seems it is discontinued by Hardkernel.
I think the HC4 was meant to replace it. The HC4 is another good system is you want two disks easily added.
Does anybody have experience with these boards?
I have lots of boards including the NanoPiM4 with sata hat. It is a great board. Same cpu as odroid-n2
My main goal is to exchange my current X86 setup with the most energy-efficient (low power consumption) and cheapest way possible without sacrificing too much performance regarding SMB transfers, download/upload and the docker containers, I mentioned before.
Most arm processors are going to use single digit watts. And there aren't a lot of cpus out there. Many boards use the same cpu. The RPi4 and nanopim4 are my top recommendations. The only reason I would recommend the nano pim4 over the odroid-n2+ is the sata hat is real sata - no usb involved.
I understand that OS filesystem should show without a plugin.
Read post #6 again.
doesn't tell that (or even hint it).
That isn't its real purpose. It just happens to work that way now. Most people don't need to see the root filesystem in the filesystem tab if they aren't going to use it. And to use it for sharedfolders, you have to have that plugin installed. But that is up to votdev if he wants to change the description. Quite a few omv-extras plugins depend on the sharerootfs plugin. So, it has a good chance of being installed automatically on most omv systems.
OMV does not use it because the 5.15 kernel is not the only kernel that OMV systems might be using. If you have backports disabled or use an arm board, most will not have the 5.15+ kernel. I would have to look to see if there is an environment variable that could be tweaked to use it. It might cause other issues though.
It looks like you are using an RPi? If so, an RPi does not use grub.
OMV directly as OS or Debian first and then OMV installed?
Those are the same thing. OMV is just a package that runs on Debian. And there is no OMV image for any arm board. So, you install Armbian first and then run the install script.
on an microSD card or eMMC?
How many HDDs/SSDs are connected?
I actually don't use it for OMV normally. I used it for a work from home desktop for a while. I just normally test OMV on it. So, I usually only have one hard drive connected.
mentioned that the more powerful Odroid N2+ uses less energy than the RPi 4. Can anybody confirm that?
It is going to be a single digit number either way. I guess the odroid n2+ has two big cores and four small cores that don't run at the same time. So, that probably makes sense.
I assume that both boards are powerful enough to handle the tasks, I mentioned, with ease. Right?
Yep, that is why I said you would be happy with either.
What are your opinions about my intention and are there any hiccups I might face or didn't take in consideration?
They are both great boards. I only have an odroid-n2 (not a plus) and many RPi4s. I would guess the n2 uses a tiny bit more energy but still a very stable board for me. I think you would be happy with either.
I have seen more than one upgrade which failed, because apt-get (in the omv-release-upgrade) will remove openmediavault before any plugins and the plugins souce /usr/shar/openmediavault/scripts/helper-functions. Getting this rigt is not so easy, as you can not run omv-release-upgrade (because of the missing packages, whic hwere to be reinstalled).
If you find something to add to the fix script, that would be great. I haven't used it much because I haven't tested a lot of upgrades and when I do, they haven't failed.
Mount and unmount now work fine, but deleting a repo still deletes the shared folder.
Your fix for removing the shared folder removed the rmdir call from the unmountRepo function, rather than the deleteRepo function - did you mean that?
The unmount was deleting the sharedfolder's folder as well. Unfortunately, the borg delete command is deleting the folder. I will have to look into this more.
Some of post scripts seem not apply correctly during the release-upgrade on my OMV. However, i manually fix them up now.
If the upgrade fails, they don't get run. I did write a small fix script for those cases. It obviously won't cover everything though. https://github.com/OpenMediaVa…lob/master/fix5to6upgrade
are backups implemented in gui now?
No. Between porting to OMV 6.x and trying to get things to work better (moving some actions to virsh) and VM creation using virt-install (to not have to maintain xml in the plugin), I haven't got to backups.
These issues should be fixed in 6.1.1 in the repo now.
Fix for removing the sharedfolder folder.
Fix for mounting a repo
Still looking at the unmount. That code hasn't changed in a long time and it is being passed the correct parameter.