Is there some reason you can not add external storage?
Posts by gderf
-
-
This what I see when I ssh in - there is no mention of OMV - /etc/issue is not being displayed
Code
Display MoreLinux omv 6.14.8-3-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-3~bpo12+1 (2025-09-12T11:29Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You do not have any new mail. Last login: Sun Dec 28 14:54:35 2025 from 192.168.1.50 fred@omv:~$If I take an IPMI console I get this and then the expected screen after logging out.
Code
Display Morefred@telescope ~ $ ipmi [SOL Session operational. Use ~? for help] omv login: fred Password: Linux omv 6.14.8-3-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-3~bpo12+1 (2025-09-12T11:29Z) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. You do not have any new mail. fred@omv:~$ exit logout openmediavault 8.0-12 (Synchrony) omv ttyS0 Copyright (C) 2009-2025 by Volker Theile. All rights reserved. To manage the system visit the openmediavault workbench: br-2418a40832e0: 172.24.0.1 br-4781f1039f4d: 172.29.0.1 br-75610e35226a: 172.28.0.1 br-a8136fa38e02: 192.168.16.1 enp101s0np0: 192.168.1.51 By default the workbench administrator account has the username 'admin' and password 'openmediavault'. It is recommended that you change the password for this account within the workbench or using the 'omv-firstaid' CLI command. For more information regarding this appliance, please visit the web site: https://www.openmediavault.org omv login: -
"Surprisingly smooth" seems a bit rude to votdev and other contributors, as well as all the Debian maintainers. Anyway, my two upgrades also went well. Thanks!
It's honest, given the difficulties I and others have had with the upgrades.
-
Regarding /etc/sysctl.conf, from ChatGPT:
-
The price on the Tyan I bought in September 2025 for $184 rose to $232 before completely selling out on eBay.
There are still some Chenbro NR12000 units available. Not a bad second choice.
-
-
Hi everyone,
I just noticed today that the permissions of /srv might have changed, but not sure if it was intended (perhaps by some update?).
Right now I cannot cd into /srv with my personal user, while some weeks ago I could for sure.
here are the current permissions:
The + indicates that ACLs were applied to that directory, but not what they are. My /srv doesn't have this.
-
The admin user has no shell assigned so it can't login via a terminal or ssh. This is standard OMV default behavior .
-
Once upon a time there was the usbmount package available for Debian that auto mounted and auto dismounted USB drives. I used to use it with OMV 5. However it became unmaintained and eventually withdrawn from the distribution.
-
-
Makes sense if your compose files are using restart: unless-stopped. If you use restart: always, I would guess they would start.
Probably. But that can make debugging a container difficult if it is problematic and it gets into a crash -> restart loop.
-
No shutdown hang when running the suggested commands.
But when the machine came back up none of the dockers were running.
-
I assume you a leaving the docker storage field blank to customize your daemon.json? Otherwise, the checkbox is there to disable it.
I left that field blank to make custom changes in the file. I did not realize that the checkbox would do the same thing. I have since then restored the docker storage field as it was and am using the checkbox.
Very powerful checkbox that is. Having it enabled cost me an additional 90 seconds to reboot

-
sudo shutdown -r now vs sudo reboot makes no difference in the hang time.
I also tried setting "live-restore": false, in /etc/docker/daemon.json. This eliminated this shutdown hang but when the machine restarted none of my dockers were running.
I then ran docker start $(docker ps -aq) to start all the dockers and shutdown -r now again. No shutdown hang and when the machine cam back up all dockers were running.
I rebooted a few more times without any hangs and all my dockers were running when the machine came back up.
In my case setting "live-restore": false in /etc/docker/daemon.json seems to have solved it.
Thanks for the hint where to look.
-
You might want to change the Subject of the thread to something that is more suggestive of what it has drifted into.
-
Could be a lot of work if you have many containers, but one way to find the causing ones is to stop all of them then reboot. It shouldn't hang at all. Then start them one at a time and reboot to see if that one causes a hang.
I've fooled with this long enough and I surrender for now.
-
I haven't run apparmor here for many years, making it a non issue for me.
So far my limited testing with the 19 containers I run shows that Plex is definitely a contributor to the problem.
-
I wonder what changed between OMV7/Debian 12 and OMV8/Debian 13 to cause this. I didn't change anything going from one to another.
-
What does the Plex application log say?
-
yeah that is what my research pointed to. I think this was not the case before the OMV upgrade. I will try to pinpoint the container that causes it.
Let us know what the culprit is. I am seeing a 90 second hang during shutdown since upgrading to OMV 8.