Posts by votdev

You can change the UUID of one filesystem according to https://askubuntu.com/a/642627.

Quote from mbox5

So I have Pi 4 running just fine. When I tried to install OMV like I've done now I don't know how many times via

Code

wget -O - https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/installScript/master/install | sudo bash

I get this error:

Code

OMV 6.x on RPi is waiting for a fix. Exiting...

Anyone know what this is about?

I think this is releated to this pull request: https://github.com/openmediavault/openmediavault/pull/1187

• You can not install OMV in a graphical environment, you need to install OMV on a dedicated system.
• Use a new disk for the root filesystem. Plug your old disk as data disk after the first installation (so no data will get lost on accident).

According to https://github.com/openmediava…system/Filesystem.js#L548 the only possible reason can be that there are file systems with duplicate UUIDs.

Please run omv-rpc -u admin 'FileSystemMgmt' 'getList' '{"start":0,"limit":-1}' | jq and post the output here.

The problem appeared in the past if there is a duplicate entry of the column used to order. The ExtJS framework then simply filters the duplicate entries. But this should not happen, otherwise this would mean that there is a duplicate device file which is not possible.

Are you using the folder2ram plugin?

Quote from TOMillr

Interesting! Do you have to manually enable this automatic update for security?

No. Security updates are installed automatically. If email notification is enabled, you'll also get an notification if 'normal' updates are available.

Quote from TeWuEs

Greetings.

The problem is that under "Secure connection -> Certificate"

there's noting to chose from, only "None".

As a result "Secure connection" can not be enabled!

I can access OMV GUI but with unsecure http://host.domain

Ping is O.K.

Tom

Display More

Quote from Zoki

I googled quite a bit, but found no clear answer. To me it looks like the mad-card is not meant as a wrapper to input elements. Form the docs:

"<mat-card> is a content container for text, photos, and actions in the context of a single subject."

and at least angular material is not using it like this on their web page.

Don't wont to bother, but this one struck me , after installing OMV6, but I seem to be the only one, so just ignore it.

And thanks for the nice product, I have been using it for several years now.

Display More

But it is nowhere forbidden. TrueNAS for example is also using forms inside mat-card.

- https://github.com/truenas/web…references.component.html

- https://github.com/truenas/web…m-embedded.component.html

I am sure there are more projects using it the same way.

- https://github.com/cloudnc/ngx…sting-form.component.html

- https://gist.github.com/EmpeRo…3af84b15f5c386261e6e9ab19

- ...

A mat-card is a styling component to show the user that this is a form. Why reinventing the wheel when mat-card can be used to separate a form from the rest of the page?

Please have a look into /var/log/nginx/openmediavault-webgui_error.log.

Quote from Zoki

The font size if overwritten by the omv-form-checkbox-wrapper

This is done to adapt the look of the checkbox field hint to the default look of all other form field hints. It does not make sense to define a different font size for checkbox hints when all other form field hints are using a different one which is defined by the Material framework.

I think this is a bug in the Material framework because all form field hints are reducing their font size if they are embedded in a mat-card.

Quote from benzino77

2. Correct me if I'm wrong: omv-env unset OMV_COLLECTD_HOSTNAME removed OMV_COLLECTD_HOSTNAME from /etc/default/openmediavault permanently and It will persist between restarts.

Yes. If you want to set a different value use omv-env set foo=bar. See https://openmediavault.readthe…l#environmental-variables for more information.

Quote from benzino77

I found this in /etc/default folder:

Code

root@openmediavault:/etc/default# ls -la
razem 212
drwxr-xr-x   3 root root  4096 sty 14 11:32 .
drwxrwxr-x 113 root root 12288 sty 14 11:32 ..
<snip>
-rw-r--r--   1 root root  2704 gru 18  2020 openmediavault
-rw-r--r--   1 root root  1831 lis 17  2020 openmediavault.dpkg-dist
<snip>
root@openmediavault:/etc/default# diff openmediavault openmediavault.dpkg-dist
1,20d0
< # This file is part of OpenMediaVault.
< #
< # @license   http://www.gnu.org/licenses/gpl.html GPL Version 3
< # @author    Volker Theile <volker.theile@openmediavault.org>
< # @copyright Copyright (c) 2009-2018 Volker Theile
< #
< # OpenMediaVault is free software: you can redistribute it and/or modify
< # it under the terms of the GNU General Public License as published by
< # the Free Software Foundation, either version 3 of the License, or
< # any later version.
< #
< # OpenMediaVault is distributed in the hope that it will be useful,
< # but WITHOUT ANY WARRANTY; without even the implied warranty of
< # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
< # GNU General Public License for more details.
< #
< # You should have received a copy of the GNU General Public License
< # along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>.
<
< # Default values
27a8,9
> OMV_SHAREDFOLDERS_DIR="/sharedfolders"
> OMV_SHAREDFOLDERS_DIR_ENABLED="NO"
39c21
< OMV_MKCONF_SCRIPTS_DIR="/usr/share/openmediavault/mkconf"
---
> OMV_SALT_SCRIPTS_DEPLOY_DIR="/srv/salt/omv/deploy"
46,47c28,29
< OMV_INITSYSTEM_SCRIPTS_DIR="/usr/share/openmediavault/initsystem"
< OMV_INITSYSTEM_FILE="/var/lib/openmediavault/initsystem.req"
---
> OMV_INITDB_SCRIPTS_DIR="/usr/share/openmediavault/initsystem"
> OMV_INITDB_FILE="/var/lib/openmediavault/initsystem.req"
50a33,34
> OMV_WEBGUI_ADMINUSER_NAME="admin"
> OMV_WEBGUI_ADMINGROUP_NAME="openmediavault-admin"
56,59d39
< OMV_COLLECTD_HOSTNAME=`uname -n`
< OMV_SHAREDFOLDERS_DIR="/sharedfolders"
< OMV_WEBGUI_ADMINUSER_NAME="admin"
< OMV_WEBGUI_ADMINGROUP_NAME="openmediavault-admin"

Display More

So it looks like an update change the default settings. Removing OMV_COLLECTD_HOSTNAME=`uname -n` from the file DOES NOT change the situation. After reboot and run omv-salt deploy run collectd rrdcached there is still strange entry in /etc/collectd/collectd.conf and the "uname -n" catalog name.

ps.

I found that old domain name was stored in /etc/salt/minion_id - after changing it omv-salt command shows correct FQDN of my OMV installation.

Display More

It seems so, but i didn't find it in the file that is installed by the package.

Doesn't matter, we need to fix it either way.

Please run omv-env get and verify that there is no OMV_COLLECTD_HOSTNAME listed.

Force Salt to update its internal pillar data: omv-salt stage run prepare

Finally rebuild ALL configurations: omv-salt stage run deploy

OK, at some time you have tried to customize the environment variable OMV_COLLECTD_HOSTNAME because uname -n outputs the hostname. Please execute omv-env get | grep HOSTNAME and something like OMV_COLLECTD_HOSTNAME=`uname -n` should be displayed.

Please run omv-env unset OMV_COLLECTD_HOSTNAME and omv-salt stage run prepare; omv-salt deploy run collectd to fix the issue.

Quote from mes mariusz

Now @ OMV 5 I se something really, really stupid... Someone has decided the drives added by GUI are called by uuid. What a stupid idea...

Because labels have caused dozens of user request here in the forum and GitHub issue because users have plugged in multiple USB devices with the same label which broke their configuration. The main reason is that they are not that predictable like UUID. The forum moderators and devs were just tired of wasting our time with such support requests. The now used solution also enhanced the user experience because of less troubles. Finally the way how the mount path looks like is totally irrelevant for the end user because they should not get in contact if they use OMV via UI. The backend of OMV is implemented that way which makes less troubles because it uses predictable device names. They are not human friendly, but OMV is no human, and the UI provides human friendly information by trying to hide the predictable devices files wherever possible.

Quote from mes mariusz

I want to have clear (by label) content of my /etc/fstab: (again, like I had @ OMV4)

In that case OMV is not the right solution for you. If you want to have full control over such things that are normally unimportant for the end user, then maintain your system via CLI manually.

Quote from mes mariusz

This is just awfull...

I really think you should try another product like FreeNAS or XigmaNAS, maybe they fit your needs better.

And finally i forbid myself this way of expression that you are using here. You are using an open source product that is made available to you free of charge and is maintained by people in their free time. Use it as it is offered to you or find something else.

I know this is a often asked feature, but be sure that it would have been already implemented if it would be simple. You all should also know that i hate to implement immature implementations in OMV. I do the complete project in my spare time, so i can only say that features are done when they are done.

Please run omv-salt deploy run collectd rrdcached and check if the file looks different.

Please see https://github.com/openmediavault/openmediavault/pull/1175

According to https://github.com/openmediava…collectd_collectd.conf.j2 the “Hostname” line should contain “localhost” by default. Is it possible that you customized the environment variable erroneously?

These are all defaults of the Angular Material framework the OMV UI relies on. It does not make sense to tweak these settings because it might break the UI proportions and other things.