Yes, I'm sure I removed the right disk. I double-checked by excluding all other disks in the /srv/ directory per CLI. I've tried to delete the pool as well, but unsuccessfully. I can "delte" the pool, but it throws another error message when applying the new configuration. I've attached it as a screenshot:
For some reason I cannot copy the error message to the clipboard from the message center. And when I undo the changed configuration, the error messages in the message center disappear, too.
That is the fourth bullet in my initial post. If I try it, OMV throws the error message I shared there.
ryecoaaron As you have been working on the mergerfs add-on, may I ask you whether you have any idea how to fix the above?
I'm not sure, but the issue may also be related to my OMV5 -> 6 upgrade, as the mergerfs was set up on OMV5, then converted during the upgrade process. Then I changed it from fstab to systemd in the OMV6 web interface. Still, I don't know how to get out of this...
One of my hard disks died. It was part of a MergerFS. No big deal, but it left my OMV 6 in an inconsistent state:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': MyRS.lan:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment: The directory /srv/mergerfs is in the correct state
Started: 21:46:06.129989
Duration: 4.553 ms
Changes:
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: []
Started: 21:46:06.135068
Duration: 3.09 ms
Changes:
----------
file.find:
----------
ID: configure_mergerfs_MyFarm
Function: file.managed
Name: /etc/systemd/system/srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: True
Comment: File /etc/systemd/system/srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount is in the correct state
Started: 21:46:06.138260
Duration: 56.44 ms
Changes:
----------
ID: systemd-reload_MyFarm
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 21:46:06.195900
Duration: 274.351 ms
Changes:
----------
pid:
3792668
retcode:
0
stderr:
stdout:
----------
ID: enable_MyFarm_mergerfs
Function: service.enabled
Name: srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: True
Comment: Service srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount is already enabled, and is in the desired state
Started: 21:46:06.484267
Duration: 18.166 ms
Changes:
----------
ID: restart_MyFarm_mergerfs
Function: cmd.run
Name: systemctl restart srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: False
Comment: Command "systemctl restart srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount" run
Started: 21:46:06.502678
Duration: 8.519 ms
Changes:
----------
pid:
3792700
retcode:
5
stderr:
Failed to restart srv-38e633b3x2d0da4x2d40fax2d96a2x2d8680e8063df3.mount: Unit srv-38e633b3x2d0da4x2d40fax2d96a2x2d8680e8063df3.mount not found.
stdout:
Summary for MyRS.lan
------------
Succeeded: 5 (changed=3)
Failed: 1
------------
Total states run: 6
Total run time: 365.119 ms
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color mergerfs 2>&1' with exit code '1': MyRS.lan:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment: The directory /srv/mergerfs is in the correct state
Started: 21:46:06.129989
Duration: 4.553 ms
Changes:
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: []
Started: 21:46:06.135068
Duration: 3.09 ms
Changes:
----------
file.find:
----------
ID: configure_mergerfs_MyFarm
Function: file.managed
Name: /etc/systemd/system/srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: True
Comment: File /etc/systemd/system/srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount is in the correct state
Started: 21:46:06.138260
Duration: 56.44 ms
Changes:
----------
ID: systemd-reload_MyFarm
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 21:46:06.195900
Duration: 274.351 ms
Changes:
----------
pid:
3792668
retcode:
0
stderr:
stdout:
----------
ID: enable_MyFarm_mergerfs
Function: service.enabled
Name: srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: True
Comment: Service srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount is already enabled, and is in the desired state
Started: 21:46:06.484267
Duration: 18.166 ms
Changes:
----------
ID: restart_MyFarm_mergerfs
Function: cmd.run
Name: systemctl restart srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount
Result: False
Comment: Command "systemctl restart srv-38e633b3\x2d0da4\x2d40fa\x2d96a2\x2d8680e8063df3.mount" run
Started: 21:46:06.502678
Duration: 8.519 ms
Changes:
----------
pid:
3792700
retcode:
5
stderr:
Failed to restart srv-38e633b3x2d0da4x2d40fax2d96a2x2d8680e8063df3.mount: Unit srv-38e633b3x2d0da4x2d40fax2d96a2x2d8680e8063df3.mount not found.
stdout:
Summary for MyRS.lan
------------
Succeeded: 5 (changed=3)
Failed: 1
------------
Total states run: 6
Total run time: 365.119 ms in /usr/share/php/openmediavault/system/process.inc:197
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(170): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusac...', '/tmp/bgoutputbk...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(192): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}It seems, there are circular references in the logic, which do not allow me to solve the problem. Any idea what I could do to regain a consistent state on my system?
*Lol* Same here. Your server really has a beautiful layout! My 2U server was more expensive and can only host 8 drives. Hotswap, though, but I've never used it and it's not critical for my usecase. Congrats on your foresight!
I've never intended to install a desktop environment on my OMV system and never used it, but remember that it was installed as a dependency while I was experimenting with something else. No guarantees for anything, but I've successfully purged the desktop environment using the following command and have been able to upgrade from OMV5 to 6 afterwards.
apt purge task-desktop hyphen-en-us libglu1-mesa libreoffice-* libu2f-udev mythes-en-us x11-apps x11-session-utils xinit xorg xserver-* desktop-base task-german task-german-desktop totem gedit gedit-common gir1.2-* gnome-* gstreamer* sound-icons speech-dispatcher totem-common xserver-* xfonts-* xwayland gir1.2* gnome-*Source: unix.stackexchange.com
Hope this helps. But as always: Backup FIRST!
Not sure this will help everyone in this thread, but maybe some: I've had loads and loads of RPC errors and could neither see my RAID5, nor my mergerfs nor my filesystems anymore. In my case the solution was very simple: I only had to go to the extensions and remove the old mergerfsfolder plugin I was using. As soon as that was purged, my RAID and mergerfs miraculously reappeared.
I think, I've got it! 
Here what I've done now:
3. Reactivated the missing extensions/plugin via
/usr/sbin/omv-mkaptidx
dpkg-divert --remove --rename /usr/sbin/omv-mkaptidx
omv-mkaptidx...as described in many other places on this forum
4. Received loads and loads of RPC errors when looking for my RAID and mergerfs. The solution was very simple. I only had to remove the old "version 5.x" mergerfs plugin. After I've purged it, Raid and mergerfs reappeared. No RPC errors anymore...
It seems everything is working now! YIKES!!!
I've been able to solve two issues:
Running omv-upgrade succeeded now. YAY! I could also log into the OMV6 GUI and "apply changes" as requested.
Now my Raid, my mergerfs and my extensions are not showing, but it seems I've advanced...
root@MyRS:/# dpkg -l | grep openmed
ii omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault
ii openmediavault 6.0.27-1 all openmediavault - The open network attached storage solution
ii openmediavault-backup 6.0.4 all backup plugin for OpenMediaVault.
ii openmediavault-clamav 6.0-9 all openmediavault ClamAV plugin
ii openmediavault-diskstats 6.0-6 all openmediavault disk monitoring plugin
ii openmediavault-fail2ban 6.0.2 all OpenMediaVault Fail2ban plugin
ii openmediavault-flashmemory 6.1 all folder2ram plugin for openmediavault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-mergerfsfolders 5.1.4 all mergerfs folders plugin for openmediavault.
ii openmediavault-omvextrasorg 6.0.8 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-resetperms 6.0 all Reset Permissiondpkg -C does not return any errors anymore.
It seems the old unionfs and mergerfs extensions have not migrated correctly, probably because the migration was interrupted by the collectd error. Is there any way to migrate those "after the fact"? As I'm on OMV6 already omv-release-upgrade obviously does not longer exist...
Done. Thanks...
Just tried to omv-release-upgrade from OMV5 to OMV6, but the upgrade errors out with the following message:
Errors were encountered while processing:
collectd-core
collectd
openmediavault
openmediavault-fail2ban
openmediavault-diskstats
openmediavault-flashmemory
openmediavault-backup
openmediavault-omvextrasorg
openmediavault-resetperms
openmediavault-clamav
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: Sub-process /usr/bin/dpkg returned an error code (1)Looking into dpkg -l, I get:
root@MyRS:~# dpkg -l | grep openmed ii omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault
iU openmediavault 6.0.27-1 all openmediavault - The open network attached storage solution
iU openmediavault-backup 6.0.4 all backup plugin for OpenMediaVault. iU openmediavault-clamav 6.0-9 all openmediavault ClamAV plugin
iU openmediavault-diskstats 6.0-6 all openmediavault disk monitoring plugin
iU openmediavault-fail2ban 6.0.2 all OpenMediaVault Fail2ban plugin
iU openmediavault-flashmemory 6.1 all folder2ram plugin for openmediavault
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
ii openmediavault-mergerfsfolders 5.1.4 all mergerfs folders plugin for openmediavault.
iU openmediavault-omvextrasorg 6.0.8 all OMV-Extras.org Package Repositories for OpenMediaVault
iU openmediavault-resetperms 6.0 all Reset Permissionsdpkg -C yields:
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure menu option in dselect for them to work:
collectd statistics collection and monitoring daemon
openmediavault openmediavault - The open network attached storage soluti
openmediavault-backup backup plugin for OpenMediaVault.
openmediavault-clamav openmediavault ClamAV plugin
openmediavault-diskstats openmediavault disk monitoring plugin
openmediavault-fail2ban OpenMediaVault Fail2ban plugin
openmediavault-flashmemory folder2ram plugin for openmediavault
openmediavault-omvextrasorg OMV-Extras.org Package Repositories for OpenMediaV
openmediavault-resetperms Reset Permissions
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
collectd-core statistics collection and monitoring daemon (core system)
The following packages have an unknown foreign architecture, which will
cause dependency issues on front-ends. This can be fixed by registering
the foreign architecture with dpkg --add-architecture:
cupswrappermfc7360n:i386 Brother MFC7360N CUPS wrapper driver
mfc7360nlpr:i386 Brother MFC-7360N LPR driver Any advice to resolve this, or should I restore my backup or install cleanly?
Sorry, didn't want to hijack the thread. Do you want me to open a new one?
Looking for advice on whether to upgrade or restart with a clean install...
The last clean install was OMV4, which I upgraded to OMV5 (the hard way) when OMV4 went EOL.
All extensions I'm using have been migrated, so I'm not worried there.
I also understood that docker and docker containers should not be an issue as they are not really touched.
I'm wondering about my disk setup though:
My system SSD and some, but not all HDDs of a RAID5 have been installed under OMV4 and are still mounted by label, not by UUID.
I also have MergerFS with 5 internal SATA HDDs and 1 external USB HDD (installed under OMV5, mounted by UUID)
I understand that I was never supposed to upgrade OMV4 -> 5. Therefore my questions:
1) Is the OMV5 -> 6 upgrade correctly handling "by-label-mounts" or not?
2) Would you recommend me upgrading or clean installing this time?
3) If the latter, is there some step-by-step guide you'd recommend to install the new system while keeping the RAID5 intact?
Any advice appreciated...
Thanks, macom . Never realized there were different sources behind the extensions. But I can see it now, as I activiated the "homepage" column in the extension section!
Just to make sure: That means I do NOT have to deinstall those plugins before upgrading, right?
Thinking about upgrading from OMV5 to OMV6 within the next couple of weeks. I'm currently using OMV-diskstats and OMV-ClamAV as extensions, but understand they have been integrated into "base" OMV6 in the meantime.
Does that mean that I should deinstall them as omv-extras extensions before upgrading or can I just keep them, so that settings are migrated?
Any advice appreciated...
Agreed. Just checked my average CPU usage over the last year (Intel i3-8100):
- Most of the time idling at 5% with peaks at about 20%
- Three months at ~70% while I was plotting Chias (waste of time and resources)
- Two weeks at ~40% while Frigate ran AI algorithms on my webcams.
- After I installed a Coral TPU to handle the AI I'm back at ~20% now.
No video encoding involved though...
I like your thinking! Most DIY NAS builders completely overpower their servers (like me!!!). I'd stick with Intel or Ryzen as that gives you best compatibility for linux-based server systems. Even if you are fed up with your QNAP box (same with me with Syno some years ago), I'd still look at what CPUs are built into QNAP and Synology servers and take that as reference. They usually optimize for power consumption in light of typical user performance requirements (which are less than you'd think, no, but at least what I thought at the time).
I'm more familiar with Syno. They don't even consider Intel or Ryzen for their "value" NASs, but offer Realtek stuff. But their recent + NAS series (which is for "advanced" NAS needs) comes with an Intel Celeron J4025, which should be plenty for your needs AND pretty power-efficient. Not sure whether QNAP servers give you better references, but whatever you choose, it should consume less or equal power than that...
Very interesting! Installed docker scan as per the docker link provided above, logged into the docker environment, registered with snyk and scanned my container images. Apparently I'm log4j safe. However, docker scan found several other vulnerabilities based on outdated, unpatched linux images in some of the containers. One of the downsides of docker containers apparently, especially if they are not updated regularly. Perfectly logical, but I wasn't aware. Learned something...
Thanks for sharing chente. Cloned the git repo. Ran without problems. Updated my router as well. So far, so good...
Answering my own questions:
Marking as solved...