58 very impressive!
Did you install Docker on OMV6 via the GUI fresh or did you re-use a Docker installation from previous versions (OMV5)?
58 very impressive!
Did you install Docker on OMV6 via the GUI fresh or did you re-use a Docker installation from previous versions (OMV5)?
Hi MarcS
On a fresh OMV6
I read that OMV6 is still beta.
It is not beta and docker has nothing to do with OMV. omv-extras installs docker on OMV 6 just like it did on OMV 5. I also wouldn't use a mergerfs pool for your docker path.
I had to de-install Docker and install new. Luckily de-installing via OMV does not delete my containers.
After re-install Docker is now up and running. And yes, I am pointing the docker folder to a device path and not a mergerfc pool. thanks for the tip.
Hi,
I wanted to upgrade from OMV6 but this line is stopping me:
Zitatopenmediavault-unionfilesystems - moving to openmediavault-mergerfs - done
I'm currently using unionfilesystems so that I can see my two disks as unique one.
Before upgrading I need to uninstall it? If yes, do I need to do anything?
Also, what about diskstats? I can't see it in the list
I'm currently using unionfilesystems so that I can see my two disks as unique one.
Before upgrading I need to uninstall it? If yes, do I need to do anything?
You don't have to do anything. The upgrade process should install openmediavault-mergerfs, migrate your unionfilesystems pool (which is mergerfs too), and remove unionfilesystems.
Also, what about diskstats? I can't see it in the list
That is a core omv plugin not an omv-extras plugin. And it is available on omv6.
ZitatYou don't have to do anything. The upgrade process should install openmediavault-mergerfs, migrate your unionfilesystems pool (which is mergerfs too), and remove unionfilesystems.
Thanks! From the post I didn't have clear if I had to it manually.
Also thanks again for the diskstats answer
I didn't have clear if I had to it manually.
I changed the first post to make that more clear.
Sorry to disturb so soon but after the upgrade I got this error:
Preparing to unpack .../libarchive-zip-perl_1.68-1_all.deb ...
Unpacking libarchive-zip-perl (1.68-1) ...
Selecting previously unselected package openmediavault-mergerfs.
Preparing to unpack .../openmediavault-mergerfs_6.3.2_all.deb ...
Unpacking openmediavault-mergerfs (6.3.2) ...
Replacing files in old package omvextras-unionbackend (5.0.2) ...
Setting up libarchive-zip-perl (1.68-1) ...
Setting up openmediavault-mergerfs (6.3.2) ...
Updating configuration database ...
debian:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment:
Started: 14:47:59.079158
Duration: 4.866 ms
Changes:
----------
/srv/mergerfs:
----------
directory:
new
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: []
Started: 14:47:59.084611
Duration: 2.801 ms
Changes:
----------
file.find:
----------
ID: systemd_remove_dead_symlinks
Function: cmd.run
Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete
Result: True
Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run
Started: 14:47:59.087991
Duration: 5.026 ms
Changes:
----------
pid:
6065
retcode:
0
stderr:
stdout:
/etc/systemd/system/multi-user.target.wants/php7.3-fpm.service
----------
ID: configure_mergerfs_Data
Function: file.managed
Name: /etc/systemd/system/srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount
Result: False
Comment: Unable to manage file: none of the specified sources were found
Started: 14:47:59.093235
Duration: 20.6 ms
Changes:
----------
ID: systemd-reload_Data
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 14:47:59.113958
Duration: 210.814 ms
Changes:
----------
pid:
6066
retcode:
0
stderr:
stdout:
----------
ID: enable_Data_mergerfs
Function: service.enabled
Name: srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount
Result: True
Comment: Service srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount is already enabled, and is in the desired state
Started: 14:47:59.339162
Duration: 18.009 ms
Changes:
Summary for debian
------------
Succeeded: 5 (changed=4)
Failed: 1
------------
Total states run: 6
Total run time: 262.116 ms
ERROR: Failed to create the default configuration: Command '['/usr/share/openmediavault/confdb/create.d/conf.service.mergerfs.sh']' returned non-zero exit status 1.
dpkg: error processing package openmediavault-mergerfs (--configure):
installed openmediavault-mergerfs package post-installation script subprocess returned error exit status 1
Processing triggers for openmediavault (6.0.38-1) ...
Updating workbench configuration files ...
Restarting engine daemon ...
Errors were encountered while processing:
openmediavault-mergerfs
Log ended: 2022-09-08 14:48:00
Log started: 2022-09-08 14:48:02
(Reading database ...
(Reading database ... 100%
(Reading database ... 34909 files and directories currently installed.)
Removing omvextras-unionbackend (5.0.2) ...
Setting up openmediavault-mergerfs (6.3.2) ...
Updating configuration database ...
debian:
----------
ID: configure_pool_dir
Function: file.directory
Name: /srv/mergerfs
Result: True
Comment: The directory /srv/mergerfs is in the correct state
Started: 14:48:04.656559
Duration: 4.759 ms
Changes:
----------
ID: remove_mergerfs_mount_files_/etc/systemd/system
Function: module.run
Result: True
Comment: file.find: []
Started: 14:48:04.661910
Duration: 2.814 ms
Changes:
----------
file.find:
----------
ID: systemd_remove_dead_symlinks
Function: cmd.run
Name: find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete
Result: True
Comment: Command "find /etc/systemd/system/multi-user.target.wants -xtype l -print -delete" run
Started: 14:48:04.665299
Duration: 5.801 ms
Changes:
----------
pid:
6328
retcode:
0
stderr:
stdout:
----------
ID: configure_mergerfs_Data
Function: file.managed
Name: /etc/systemd/system/srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount
Result: False
Comment: Unable to manage file: none of the specified sources were found
Started: 14:48:04.671331
Duration: 20.551 ms
Changes:
----------
ID: systemd-reload_Data
Function: cmd.run
Name: systemctl daemon-reload
Result: True
Comment: Command "systemctl daemon-reload" run
Started: 14:48:04.691999
Duration: 219.16 ms
Changes:
----------
pid:
6329
retcode:
0
stderr:
stdout:
----------
ID: enable_Data_mergerfs
Function: service.enabled
Name: srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount
Result: True
Comment: Service srv-714c279e\x2d21ec\x2d45bc\x2da8cb\x2d767c97096d69.mount is already enabled, and is in the desired state
Started: 14:48:04.925390
Duration: 18.342 ms
Changes:
Summary for debian
------------
Succeeded: 5 (changed=3)
Failed: 1
------------
Total states run: 6
Total run time: 271.427 ms
ERROR: Failed to create the default configuration: Command '['/usr/share/openmediavault/confdb/create.d/conf.service.mergerfs.sh']' returned non-zero exit status 1.
dpkg: error processing package openmediavault-mergerfs (--configure):
installed openmediavault-mergerfs package post-installation script subprocess returned error exit status 1
Processing triggers for openmediavault (6.0.38-1) ...
Updating workbench configuration files ...
Restarting engine daemon ...
Errors were encountered while processing:
openmediavault-mergerfs
Log ended: 2022-09-08 14:48:06
Alles anzeigen
I went into the new OMV webUI and in mergeFS I had nothing.
It's not an issue if I have to create manually a new pool, but I fear that there might some dirt in the system. Do i need to check anything in particular?
After the update i didn't touch anything, in the webui I have a pending configuration change but I was waiting before give an ok.
It might have failed because your pool is already mounted. What is the output of: dpkg -l | grep openme
root@Delibird:~# dpkg -l | grep openme
rc omvextras-unionbackend 5.0.2 all union filesystems backend plugin for openmediavault
ii openmediavault 6.0.38-1 all openmediavault - The open network attached storage solution
ii openmediavault-autoshutdown 6.0.9 all OpenMediaVault AutoShutdown Plugin
ii openmediavault-diskstats 6.0-6 all openmediavault disk monitoring plugin
ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive
iF openmediavault-mergerfs 6.3.2 all mergerfs plugin for openmediavault.
ii openmediavault-omvextrasorg 6.1.1 all OMV-Extras.org Package Repositories for OpenMediaVault
ii openmediavault-sharerootfs 6.0-4 all openmediavault share root filesystem plugin
ii openmediavault-symlinks 6.0.4 all OpenMediaVault symlinks plugin
rc openmediavault-unionfilesystems 5.1.4 all Union filesystems plugin for OpenMediaVault.
ii openmediavault-wakealarm 6.0.1 all wakealarm plugin for OpenMediaVault.
Alles anzeigen
I also noticed that the pool is still avaible from windows, even if it's not the file system tab:
I just uploaded a new version of the mergerfs plugin. So,
sudo apt-get update
sudo apt-get install openmediavault-mergerfs
if that goes well:
sudo apt-get purge openmediavault-unionfilesystems
My "special" ability in finding bugs in open source projects strikes again T_T
I feel you! The list of issues I opened on GitHub is fairly long
The list of issues I opened on GitHub is fairly long
This usually means you use plugins in strange ways that my brain doesn't think of lol
This usually means you use plugins in strange ways that my brain doesn't think of lol
Your plugins are great, I am referring to open source software in general. I opened a couple of issues to your repos but were actually requests more than issues. I reported a couple of real issues to OMV itstelf though.
This usually means you use plugins in strange ways that my brain doesn't think of lol
Hi ryecoaaron , can you add swap file usage data to the "Memory Usage" plugin, or make it a separate plugin?
can you add swap file usage data to the "Memory Usage" plugin, or make it a separate plugin?
Memory usage is a core OMV widget. Wondering if it would look better as a second ring on the current memory widget?
Memory usage is a core OMV widget. Wondering if it [swap file usage] would look better as a second ring on the current memory widget?
Since they're both memory related, I think that's a very good idea.
Memory usage is a core OMV widget. Wondering if it would look better as a second ring on the current memory widget?
Yes, second circle in the widget "Memory Usage" is better than the separate widget.
Can you also combine widgets CPU Temp and CPU Utilization into one widget?
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!