Posts by gderf

    This what I see when I ssh in - there is no mention of OMV - /etc/issue is not being displayed


    If I take an IPMI console I get this and then the expected screen after logging out.



    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.

    Mine are below and I do not recall ever touching them.


    Code
    fred@omv:~$ getfacl /srv
    getfacl: Removing leading '/' from absolute path names
    # file: srv
    # owner: root
    # group: root
    user::rwx
    group::r-x
    other::r-x

    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:

    Code
    drwxr-xr-x+   8 root root   4096 Dec  4 13:47 srv 


    The + indicates that ACLs were applied to that directory, but not what they are. My /srv doesn't have this.

    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.

    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.





    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.

    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.


    Code
    OMV 8 systemd-shutdown[1]: Waiting for process: 10046 (s6-svscan), 9988 (s6-svscan), 9965 (s6-svscan), 11948 (python3), 882573 (Plex Media Serv), 10031 (s6-svscan), 881402 (s6-svscan), 9984 (s6-svscan), 957120 (s6-svscan), 881448 (s6-supervise), 10737 (s6-supervise)