Posts by Frepke

You can drag your log into ChatGPT, it gives you useful hints and advice.
With your log it points for the most of the time to your network (or your docker network or compose settings).

The compose plugin (8.0.2) sets the max size wrong in the daemon.json.

In my case it writes "max-size": "50" in the daemon.json which represents bytes, for MB's it should be "max-size": "50m"

Quote from votdev

No, the login process does not generate a process that is running as a "background" process.

Thanks,

My memory has let me down

If I remember correctly, I’ve had this before on a very slow system. I believe the process that briefly ran at that time was simply the GUI login. Perhaps votdev can confirm whether this is possible.

You could also try Arcane sometime: Arcane
It looks modern and promising.

Quote from macom

Looks like daily flush is unmounting the filesystems of the data drives.

Code

Aug 23 03:45:07 omv7 systemd[1]: Unmounting srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount - /srv/dev-disk-by-uuid-985a9ff6-d6bb-406a-bdd9-a1260e1fe4e9...
Aug 23 03:45:07 omv7 systemd[1]: Unmounting srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount - /srv/dev-disk-by-uuid-da927c35-368c-44dc-97dc-cf277f839eb8...
Aug 23 03:45:07 omv7 systemd[1]: Unmounting tmp.mount - Mount /tmp as tmpfs to reduce write access to the root device...
Aug 23 03:45:07 omv7 systemd[1]: Unmounting var-log.mount - /var/log...
Aug 23 03:45:07 omv7 systemd[1]: Starting omv-writecache-flush.service - OMV WriteCache: flush overlay changes to disk...
Aug 23 03:45:07 omv7 kernel: EXT4-fs (vdc1): unmounting filesystem da927c35-368c-44dc-97dc-cf277f839eb8.
Aug 23 03:45:07 omv7 systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount: Deactivated successfully.
Aug 23 03:45:07 omv7 systemd[1]: Unmounted srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount - /srv/dev-disk-by-uuid-985a9ff6-d6bb-406a-bdd9-a1260e1fe4e9.
Aug 23 03:45:07 omv7 systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount: Deactivated successfully.
Aug 23 03:45:07 omv7 systemd[1]: Unmounted srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount - /srv/dev-disk-by-uuid-da927c35-368c-44dc-97dc-cf277f839eb8.
Aug 23 03:45:08 omv7 umount[31018]: umount: /tmp: target is busy.
Aug 23 03:45:07 omv7 systemd[1]: tmp.mount: Mount process exited, code=exited, status=32/n/a
Aug 23 03:45:08 omv7 umount[31019]: umount: /var/log: target is busy.
Aug 23 03:45:07 omv7 systemd[1]: Failed unmounting tmp.mount - Mount /tmp as tmpfs to reduce write access to the root device.
Aug 23 03:45:08 omv7 systemd[1]: var-log.mount: Mount process exited, code=exited, status=32/n/a
Aug 23 03:45:08 omv7 systemd[1]: Failed unmounting var-log.mount - /var/log.
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - SCRIPT_START: omv-writecache flush
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - FLUSH_CMD: Starting flush command
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - CONFIG: Loaded from /etc/omv-writecache/config.yaml
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - FLUSH_START: Beginning flush operation
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - SKIP_MODE: /var/cache/apt/archives mode=drop
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - SKIP_MODE: /var/cache/samba mode=drop
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - SKIP_MODE: /var/lib/apt/lists mode=drop
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - NO_UPPER: /var/lib/dpkg/updates
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - NO_UPPER: /var/lib/openmediavault/rrd
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - NO_UPPER: /var/lib/rrdcached
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - NO_UPPER: /var/lib/monit
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - NO_UPPER: /var/log
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - SKIP_MODE: /var/tmp mode=drop
Aug 23 03:45:08 omv7 omv-writecache[31020]: 2025-08-23 03:45:08 - FLUSH_COMPLETE: Success
Aug 23 03:45:08 omv7 systemd[1]: omv-writecache-flush.service: Deactivated successfully.
Aug 23 03:45:08 omv7 systemd[1]: Finished omv-writecache-flush.service - OMV WriteCache: flush overlay changes to disk.
Aug 23 03:45:08 omv7 systemd[1]: Reached target umount.target - Unmount All Filesystems.

Display More

this is from starting the flush service from CLI

Code

Aug 23 08:41:08 omv7 systemd[1]: Unmounting run-user-0.mount - /run/user/0...
Aug 23 08:41:08 omv7 systemd[1]: Unmounting srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount - /srv/dev-disk-by-uuid-985a9ff6-d6bb-406a-bdd9-a1260e1fe4e9...
Aug 23 08:41:08 omv7 umount[34499]: umount: /run/user/0: target is busy.
Aug 23 08:41:08 omv7 systemd[1]: Unmounting srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount - /srv/dev-disk-by-uuid-da927c35-368c-44dc-97dc-cf277f839eb8...
Aug 23 08:41:08 omv7 systemd[1]: Unmounting tmp.mount - Mount /tmp as tmpfs to reduce write access to the root device...
Aug 23 08:41:08 omv7 systemd[1]: Unmounting var-log.mount - /var/log...
Aug 23 08:41:08 omv7 systemd[1]: Starting omv-writecache-flush.service - OMV WriteCache: flush overlay changes to disk...
Aug 23 08:41:08 omv7 systemd[1]: run-user-0.mount: Mount process exited, code=exited, status=32/n/a
Aug 23 08:41:08 omv7 systemd[1]: Failed unmounting run-user-0.mount - /run/user/0.
Aug 23 08:41:08 omv7 systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount: Deactivated successfully.
Aug 23 08:41:08 omv7 systemd[1]: Unmounted srv-dev\x2ddisk\x2dby\x2duuid\x2d985a9ff6\x2dd6bb\x2d406a\x2dbdd9\x2da1260e1fe4e9.mount - /srv/dev-disk-by-uuid-985a9ff6-d6bb-406a-bdd9-a1260e1fe4e9.
Aug 23 08:41:08 omv7 kernel: EXT4-fs (vdc1): unmounting filesystem da927c35-368c-44dc-97dc-cf277f839eb8.
Aug 23 08:41:08 omv7 umount[34503]: umount: /var/log: target is busy.
Aug 23 08:41:08 omv7 umount[34502]: umount: /tmp: target is busy.
Aug 23 08:41:08 omv7 systemd[1]: var-log.mount: Mount process exited, code=exited, status=32/n/a
Aug 23 08:41:08 omv7 systemd[1]: Failed unmounting var-log.mount - /var/log.
Aug 23 08:41:08 omv7 systemd[1]: srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount: Deactivated successfully.
Aug 23 08:41:08 omv7 systemd[1]: Unmounted srv-dev\x2ddisk\x2dby\x2duuid\x2dda927c35\x2d368c\x2d44dc\x2d97dc\x2dcf277f839eb8.mount - /srv/dev-disk-by-uuid-da927c35-368c-44dc-97dc-cf277f839eb8.
Aug 23 08:41:08 omv7 systemd[1]: tmp.mount: Mount process exited, code=exited, status=32/n/a
Aug 23 08:41:08 omv7 systemd[1]: Failed unmounting tmp.mount - Mount /tmp as tmpfs to reduce write access to the root device.
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - SCRIPT_START: omv-writecache flush
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - FLUSH_CMD: Starting flush command
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - CONFIG: Loaded from /etc/omv-writecache/config.yaml
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - FLUSH_START: Beginning flush operation
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - SKIP_MODE: /var/cache/apt/archives mode=drop
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - SKIP_MODE: /var/cache/samba mode=drop
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - SKIP_MODE: /var/lib/apt/lists mode=drop
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - NO_UPPER: /var/lib/dpkg/updates
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - NO_UPPER: /var/lib/openmediavault/rrd
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - NO_UPPER: /var/lib/rrdcached
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - NO_UPPER: /var/lib/monit
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - NO_UPPER: /var/log
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - SKIP_MODE: /var/tmp mode=drop
Aug 23 08:41:08 omv7 omv-writecache[34504]: 2025-08-23 08:41:08 - FLUSH_COMPLETE: Success
Aug 23 08:41:08 omv7 systemd[1]: omv-writecache-flush.service: Deactivated successfully.
Aug 23 08:41:08 omv7 systemd[1]: Finished omv-writecache-flush.service - OMV WriteCache: flush overlay changes to disk.

Display More

No problem with flushing via the button in the GUI

+1

I run OMV on a t630 for years now without problems, so the device is compatible.

cd /srv than ls,

find the dev-disk-by-uuid-xxxx for your monyprintingmachine

cd /srv/dev-disk-by-uuid-monyprintingmachine

Quote from porg

Frepke: You propose to switch to a Dockerfile which is 32bit but still supports newer Plex so far?

• How would the migration from my existing Docker look like?
• This seems tailored for the RPi, will it also work fine for my Odroid HC2?
  (My video files are mostly H264 which need no transcoding for weaker mobile devices anyhow, so I usually do not need on the fly transcoding)
• I guess some tweaking for the new Plex will become necessary too. I recall that /tmp-plex:/tmpfs-host-plex was a tweaking that Plex writes the transcoded fragments into the RAM filesystem to avoid SD card wearing. So I would need to make sure to point the new Plex installation there too.

No, I'm not suggesting to continue using a 32-bit version at all, I'm just showing you where you might find a 32-bit version to test. Of course, you decide for yourself what you want to do, but because they're just Docker containers, it's all quite easy to test.

Or you can try this v7 one: https://hub.docker.com/r/green…ex-server-docker-rpi/tags

Did you try this?

Quote from Pillhuhn

Hallo,

An welcher Stelle kann ich das automatische Abmelden von der GUI abschalten bzw. die Zeit auf z.B. 2 Stunden ändern? Oben/rechts gibt es keine Auswahlmöglichkeit mehr

Schon 1x: Danke!

Help would be easier when you post your composefile, it should look similar to the code raulfg3 posted in post #2.

Please post the compose file you're using.

It looks like your /config/config.yml is a directory instead of a file. I think you have to create the config.yml file before running the container. An example file is on GitHub.

Quote from ct100

For the WebGUI it would be nice to have a combined and more compact widget for cpu usage and system memory. The round ones use too much space on devices with smaller screens. Maybe also an easier way to change the order of the widgets in dashboard settings.

Also get rid of this ugly thing:

That "ugly" thing is there for a reason, it's specially selected.

Quote from boelle

and how did you do that?

Followed the instructions on their website and created this compose file and opened the ports on the router (in this case 18080 and 18443):

version: '3.3'
services:
    speedtest-tracker:
        container_name: speedtest-tracker
        ports:
            - '18080:80'
            - '18443:443'
        environment:
            - PUID=1000
            - PGID=100
        volumes:
            - '/dockercfg/speedtest-tracker:/config'
            - '/dockercfg/speedtest-tracker/web:/etc/ssl/web'
        image: 'ghcr.io/alexjustesen/speedtest-tracker:latest'
        restart: unless-stopped

Quote from boelle

as in How to run network Speedtest from OMV?

i want to run some automated test but for INTERNET speed, so that i can hold what i get to the ISP in case that is not the case

i use https://github.com/alexjustesen/speedtest-tracker to do this, but i get a connection refused and i need to find PUID and PGID, but https://docs.speedtest-tracker…ting-started/installation does not say for which user but i will try with root first

I did a quick setup of your 1st option (speedtest-tracker), it runs without any issue (even hourly set with the build in crontab option).

Maybe this helps: RE: 5.19.17-2-pve = BEAUTIFUL. 6.2.9-1 = FREEZE at ramdisk and aint a THING I can do.