Posts by ulrich.w

Inspecting the file /var/log/omv-writecache.log I noticed:

2025-12-26 19:05:42 [DEBUG] CMD: mount -t overlay overlay -o lowerdir=/run/omv-writecache/var_cache_apt_archives/lower,upperdir=/run/omv-writecache/var_cache_apt_archives/upper,workdir=/run/omv-writecache/var_cache_apt_archives/work,metacopy=off,redirect_dir=off,index=off /var/cache/apt/archives

2025-12-26 19:05:42 [ERROR] CMD_FAILED: mount -t overlay overlay -o lowerdir=/run/omv-writecache/var_cache_apt_archives/lower,upperdir=/run/omv-writecache/var_cache_apt_archives/upper,workdir=/run/omv-writecache/var_cache_apt_archives/work,metacopy=off,redirect_dir=off,index=off /var/cache/apt/archives (exit 32)

2025-12-26 19:05:42 [ERROR] OUTPUT: mount: /var/cache/apt/archives: unknown filesystem type 'overlay'.

dmesg(1) may have more information after failed mount system call.

2025-12-26 19:05:42 [ERROR] MOUNT_FAILED: /var/cache/apt/archives

As I didn't see it in recent starts, I guess it had been fixed meanwhile.

Also I could not look up the kernel messages, because it seems the journal is not persistent (I can only see the current boot).

Quote from ryecoaaron

I don't see any problems that need to be fixed.

So that's all expected?

Hi!

This is here for others and the maintainers to inspect. I'll add some parts of the logs from updating OMV7 (was up-to-date) to OMV8 (not beta!) on my< Raspberry Pi 4B recently:

omv-release-upgrade

...

The following packages will be REMOVED:

bsdmainutils cpufrequtils g++-12 libabsl20220623 libaio1 libasound2

...list truncated, because message was too long...

wpasupplicant xauth xdg-user-dirs xfsprogs xkb-data xml-core xmlstarlet

xz-utils zip zlib1g zstd

...

dpkg: php8.2-cgi: dependency problems, but removing anyway as you requested:

openmediavault depends on php-cgi; however:

Package php-cgi is not configured yet.

Package php8.4-cgi which provides php-cgi is not configured yet.

Package php8.2-cgi which provides php-cgi is to be removed.

openmediavault depends on php-cgi; however:

Package php-cgi is not configured yet.

Package php8.4-cgi which provides php-cgi is not configured yet.

Package php8.2-cgi which provides php-cgi is to be removed.

Removing php8.2-cgi (8.2.29-1~deb12u1) ...

dpkg: php8.2-cli: dependency problems, but removing anyway as you requested:

openmediavault depends on php-json; however:

Package php-json is not installed.

Package php8.4-phpdbg which provides php-json is not configured yet.

Package php8.4-fpm which provides php-json is not configured yet.

Package php8.4-cli which provides php-json is not configured yet.

Package php8.4-cgi which provides php-json is not configured yet.

Package php8.2-fpm which provides php-json is not installed.

Package php8.2-cli which provides php-json is to be removed.

Package php8.2-cgi which provides php-json is not installed.

openmediavault depends on php-cli; however:

Package php-cli is not installed.

Package php8.4-cli which provides php-cli is not configured yet.

Package php8.2-cli which provides php-cli is to be removed.

openmediavault depends on php-json; however:

Package php-json is not installed.

Package php8.4-phpdbg which provides php-json is not configured yet.

Package php8.4-fpm which provides php-json is not configured yet.

Package php8.4-cli which provides php-json is not configured yet.

Package php8.4-cgi which provides php-json is not configured yet.

Package php8.2-fpm which provides php-json is not installed.

Package php8.2-cli which provides php-json is to be removed.

Package php8.2-cgi which provides php-json is not installed.

openmediavault depends on php-cli; however:

Package php-cli is not installed.

Package php8.4-cli which provides php-cli is not configured yet.

Package php8.2-cli which provides php-cli is to be removed.

...

Removing python3-py (1.11.0-1) ...

dpkg: php8.2-mbstring: dependency problems, but removing anyway as you requested:

openmediavault depends on php-mbstring; however:

Package php-mbstring is not configured yet.

Package php8.4-mbstring which provides php-mbstring is not configured yet.

Package php8.2-mbstring which provides php-mbstring is to be removed.

Removing php8.2-mbstring (8.2.29-1~deb12u1) ...

dpkg: php8.2-xml: dependency problems, but removing anyway as you requested:

openmediavault depends on php-xml; however:

Package php-xml is not configured yet.

Package php8.4-xml which provides php-xml is not configured yet.

Package php8.2-xml which provides php-xml is to be removed.

...

Installing new version of config file /etc/init.d/fake-hwclock ...

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

Created symlink '/etc/systemd/system/sysinit.target.wants/fake-hwclock-load.service' → '/usr/lib/systemd/system/fake-hwclock-load.service'.

Created symlink '/etc/systemd/system/shutdown.target.wants/fake-hwclock-save.service' → '/usr/lib/systemd/system/fake-hwclock-save.service'.

Created symlink '/etc/systemd/system/timers.target.wants/fake-hwclock-save.timer' → '/usr/lib/systemd/system/fake-hwclock-save.timer'.

...

Setting up ca-certificates (20250419) ...

Updating certificates in /etc/ssl/certs...

rehash: warning: skipping ca-certificates.crt, it does not contain exactly one certificate or CRL

21 added, 13 removed; done.

...

Setting up dbus (1.16.2-2) ...

A reboot is required to replace the running dbus-daemon.

Please reboot the system when convenient.

dbus.service is a disabled or a static unit, not starting it.

...

Setting up nfs-kernel-server (1:2.8.3-1) ...

Installing new version of config file /etc/init.d/nfs-kernel-server ...

Created symlink '/etc/systemd/system/nfs-mountd.service.requires/fsidd.service' → '/usr/lib/systemd/system/fsidd.service'.

Created symlink '/etc/systemd/system/nfs-server.service.requires/fsidd.service' → '/usr/lib/systemd/system/fsidd.service'.

nfs-mountd.service is a disabled or a static unit not running, not starting it.

nfs-server.service is a disabled or a static unit not running, not starting it.

nfsdcld.service is a disabled or a static unit not running, not starting it.

Replacing config file /etc/default/nfs-kernel-server with new version

A dependency job for nfs-server.service failed. See 'journalctl -xe' for details.

invoke-rc.d: initscript nfs-kernel-server, action "restart" failed.

○ nfs-server.service - NFS server and services

Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; preset: enabled)

Active: inactive (dead)

Docs: man:rpc.nfsd(8)

man:exportfs(8)

Dec 26 19:02:43 rp-das-nas systemd[1]: Dependency failed for nfs-server.service - NFS server and services.

Dec 26 19:02:43 rp-das-nas systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.

Failed to restart nfs-kernel-server, ignoring.

...

Setting up openmediavault-omvextrasorg (8.0.2) ...

Updating configuration database ...

1. Cleaning apt cache files...

E: Could not get lock /var/cache/apt/archives/lock. It is held by process 7336 (apt-get)

N: Be aware that removing the lock file is not a solution and may break your system.

E: Unable to lock directory /var/cache/apt/archives/

2. Clearing available dpkg packages...

3. Removing apt lists...

...

The following packages will be REMOVED:

folder2ram* openmediavault-flashmemory*

0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

...

stop /var/cache/samba

Warning: Can't execute disable on the unit file path. Proceeding with the unit name.

Removed '/etc/systemd/system/basic.target.wants/folder2ram_startup.service'.

Warning: Can't execute disable on the unit file path. Proceeding with the unit name.

Removed '/etc/systemd/system/multi-user.target.wants/folder2ram_shutdown.service'.

Removing folder2ram (0.4.2) ...

Warning: Can't execute disable on the unit file path. Proceeding with the unit name.

Warning: Can't execute disable on the unit file path. Proceeding with the unit name.

Created symlink '/etc/systemd/system/multi-user.target.wants/folder2ram_cleaner.service' -> '/usr/lib/systemd/system/folder2ram_cleaner.service'.

...

                                    ┌───────────┤ Release upgrade ├───────────┐

                                    │                                         │

                                    │ The upgrade has completed successfully. │

                                    │ Please reboot the system.               │

                                    │                                         │

                                    │                                  <Ok>   │

                                    │                                         │

                                    └─────────────────────────────────────────┘

So no failures, but some issues to look at.

Meanwhile I'm at OMV 8. The options are "defaults,nofail,big_writes".When I connect the device, the filesystems aren't mounted automatically, but they are listed as online like this:

And when I click on a line and try to get details, I see:

In the syslog I see:

Dec 31 17:45:22 rp-das-nas monit[757]: Lookup for '/srv/dev-disk-by-uuid-CC58217058215B0A' filesystem failed -- not found in /proc/self/mounts

Dec 31 17:45:22 rp-das-nas monit[757]: Filesystem '/srv/dev-disk-by-uuid-CC58217058215B0A' not mounted

When I try a "mount -va", I see:

The disk contains an unclean file system (0, 0).

Metadata kept in Windows cache, refused to mount.

Falling back to read-only mount because the NTFS partition is in an

unsafe state. Please resume and shutdown Windows fully (no hibernation

or fast restarting.)

Could not mount read-write, trying read-only

mount: (hint) your fstab has been modified, but systemd still uses

the old version; use 'systemctl daemon-reload' to reload.

/srv/dev-disk-by-uuid-CC58217058215B0A: successfully mounted

The disk contains an unclean file system (0, 0).

Metadata kept in Windows cache, refused to mount.

Falling back to read-only mount because the NTFS partition is in an

unsafe state. Please resume and shutdown Windows fully (no hibernation

or fast restarting.)

Could not mount read-write, trying read-only

/srv/dev-disk-by-uuid-7682E56382E52877: successfully mounted

I doubt whether this is true, because I ejected the drive from Windows before shutting down Windows.

Anyway after the manual mount things looks like this:

Still, when I try to display "details" I get the same error. I guess it would be nice if the read-only status were visible.

Quote from Soma

And where did you read that?

I didn't read that; I *saw* it: OMV7 was mounting the NTFS with option "ro" (latest version a few days ago). Maybe the OS doesn't trust the NTFS Linux driver.

And when the filesystem is mounted read-only it makes little sense to try to export shares writable IMHO. So I din't try it.

Quote from ulrich.w

Can you give a reason also?

Answering my own question: OMV7 mounts NTFS as read-only by default, so there's not much use in most cases: Who will update the files then?

Quote from votdev

I consider this an unusual approach that is not worth integrating. (...)

OTOH it wouldn't be that hard to implement. A CSR (Certificate Signing Request) would be another thing one might ask for when using an external CA.

Quote from chente

(...) You've probably forgotten some of them.

Actually I found out that I can select the "offline" filesystem and delete it, but I could not delete the device (because it's not displayed).

Quote from chente

first unmount the services associated with that file system.

As can be seen in the screenshot I did that: It's not referenced any more.

And the "Storage" section should list the configured devices, not just the present ones; otherwise you cannot press any "remove" icon.

Just imagine some pendrive mounted by UUID broke permanently: You surely want to remove it, maybe just to silence the logs.

I've configured eth0 and wlan0 on my Raspberry Pi 4, and I've configured my DHCP server to assign a different hostname for each interface so that I can select the interface to connect using the hostname.

However https is available only for eth0 right now, because the certificate selected only has one hostname (subject) I guess.

I tried to add another certificate for the other hostname, but that one isn't selected.

Unfortunately I cannot create a self-signed certificate using multiple alternate subject names (typically I would add the IPs and the FQHNs of all interfaces as well as the hostname set in OMV).

Am I missing something, or is it a feature request?

Of course I could create the certificate externally with a tool like xca (X - Certificate and Key management), but I'd like to have a way built-in.

Quote from macom

A filesystem can be removed, once it is not referenced anymore.

The mounteditor plugin has a feature to remove orphaned filesystem.

But why isn't there simply a trashcan (remove) icon in the normal filesystem screen?

For monit: I still feel there should be a way to disable the checking: I think monit isn't needed to mount the filesystem once the device appears, so why continuing to monitor a device that isn't here? The OFFLINE status is sufficient IMHO.

Quote from raulfg3

Please DO NOT USE NTFS disk as data disk for OMV, ...

Can you give a reason also?

Quote from ryecoaaron

But the description states exactly what the plugin does. It creates a backup of the omv filesystem. Not sure what else it should say.

*When* does it create a backup, and *where* does it create a backup? And what can I do with such a "backup"?

Well I found this URL to be useful:

GitHub - xhente/omv-regen: Do you need to backup or restore the OMV configuration? This is the solution.

Do you need to backup or restore the OMV configuration? This is the solution. - xhente/omv-regen

github.com

Similar to File system cannot be removed from nonexistent hard drive for 7.7.24-1 (Sandworm):

I've unplugged a USB storage when OMV was down. When starting it again, I wanted to remove the device.

First thing I noted was that there isn't "delete cascade", i.e.: If you delete a device, all filesystems, shared folders and services related to that device are removed as well.

Next thing I did was removing "bottom-up", but still I cannot remove the filesystem, and I cannot remove the device (that isn't displayed even).

• I have no "Shared Folders" displayed
• I have one unused, unreferenced, missing filesystem:

  

• Likewise it's not being displayed under "Disks"
• 

Another thing is that monit still complains about the missing device every 30 seconds; shouldn't the service be disabled by OMV?

monit[1011]: 'filesystem_srv_dev-disk-by-uuid-f807ce5a-b92e-4dc5-8d45-899530093319' trying to restart

It would be nice if a missing device could be removed. In my case the device ws´as just a test to play with OMV as a beginner.

I'm new to OMV, and I tried to find out what "openmediavault-backup 7.1.5" is about.

However neither the description, nor the URL is really helpful (because the URL is generic).

I still have no idea how to use it.

The docs just state:

Can I backup or restore an existing openmediavault configuration?

Quote

There is no regular backup/restore procedure, but yes, in some way: keep the file /etc/openmediavault/config.xml for references purposes if the option is to go for a clean re-install.

Being lazy when just wanting to check connectivity over WLAN, I used my mobile phone's DuckDuckGo browser to log in and the created a filesystem.

I wanted to create "Test", but it had been added (name and directory) as "tseT" (all characters reversed, RTL (right to left) order?).

When I wanted to report that as a bug, the form suggested I'll have to discuss it here first, so here it is

I don't know which input fields are affected exactly, and when I tried to reproduce, I failed. However I discovered "How to avoid html input fields typing backwards in chromium browsers?" which sounds quite similar.