Posts by votdev

What is /dev/mapper/vmstore-vm--100--disk--0? It's not a software RAID because /proc/mdstat has no output according to the report.

According to the error message

stderr:
File "/usr/lib/python2.7/site.py", line 1
(c
^
SyntaxError: invalid syntax

you or someone else must have modified the file manually. The first line looks like a copyright to me. Seems the comments are not set correct. Fix this and it should work.

Oh, it seems proftpd does not enable mod_tls.c by default in Debian 11. Will be fixed in openmediavault 6.0-26, see https://github.com/openmediava…bbf13d79f2639be52f1f49b7b.

Please post the output of the CLI command blkid or better go to the UI and download the report in the diagnostic section and attach it here or at the GitHub issue.

Any information how to reproduce this? An exact step-by-step instruction would be helpful.

Will be fixed in openmediavault 5.6.16, see https://github.com/openmediavault/openmediavault/pull/1096.

P.S.: The SMART attributes page is always empty for NVMe devices.

Quote from antsh

and done

Debugging with real hardware is much easier Thx.

Could you please give this command line a try? It worked for me on OMV5. According to a bugreport for smartmontools this will not be necessary anymore for the smartctl used in OMV6.

$ smartctl -d nvme,0xffffffff -x /dev/nvme0n1

Delete the file /var/cache/salt/minion/roots/mtime_map. The bug https://github.com/saltstack/salt/issues/60535 should be fixed in the next SaltStack version.

Quote from Shalak

So this is its only purpose? Can I safely disable this and I'll only lose the welcome message on TTY?

Yes, you can disable it. The openmediavault-issue unit file is only responsible for generating the welcome message.

Please make sure that you have installed the latest version (5.6.15), then run omv-salt deploy run cronapt. This should fix your issue.

Are you using the openmediavault-flashmemory plugin?

The NUT plugin can't be used in OMV6 because the Debian collectd package does not provide the necessary NUT plugin. Please see https://github.com/openmediavault/openmediavault/issues/1065. Debian must fix the problem upstream to get the OMV plugin working again. There are no plans (and time) to integrate a workaround in the OMV plugin until upstream is fixed.

According to the source code smartctl is executed with smartctl--xall --device=nvme /dev/nvme0n1. Without having such hardware i can not do anything else, sorry.

Fixed in openmediavault 5.6.15 and 6.0-24, see https://github.com/openmediava…56453b810a8f67634ea2dc400.

Please clear your browser cache.

Will be fixed in openmediavault 6.0-23.

Great idea. I've added this feature to openmediavault 6.0-23. See https://github.com/openmediavault/openmediavault/pull/1088.

According to the man pages the directory should be /var/run/faillock. Please check if this exists and create it if necessary.

I've added an environment variable for this in openmediavault 6.0-23. See https://github.com/openmediava…c301aca8292ac04d4faa15b23.

Delete the file /var/cache/salt/minion/roots/mtime_map. This is a bug in Salt that i've reported, see https://github.com/saltstack/salt/issues/60535.

If you upgrade to openmediavault 6.0-22, then Salt is patched and the problem shouldn't appear again.