Disk doesn't mount automatically and docker doesn't start after updates and reboot.

When I do update and I reboot OMV my disk doesn't mount automaticaly, I need to mount it manualy. And Docker doesn't restart, nore if I restart it manually by the GUI.
What is the good way to restart Docker manualy ?

And, there is a configuration in order to have not to mount disk and start docker manualy when I reboot?

Thank you

Thank you. The job works well to mount dickt after a reboot

But the docker solution doesn't work. The docker status stays at "Installed and not running". And when I try to restart it manualy by the GUI i have the error message:

>>> *************** Error ***************

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; echo "Restarting docker ..." && systemctl restart docker.service ': Restarting docker ...

<<< *************************************

I did, this is logs I can see when I do journalctl -u docker

-- Logs begin at Sat 2020-10-10 18:01:46 CEST, end at Sun 2020-10-11 18:48:01 CEST. --

Oct 10 18:06:55 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Oct 10 18:07:13 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Oct 11 18:45:51 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Oct 11 18:45:52 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Oct 11 18:45:54 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Oct 11 18:45:55 odroid systemd[1]: docker.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing.

Yes I did. I have followed the post you shared Is your docker also corrupt after a reboot? (OMV5, Pi4) This might fix it!

Yes! Docker is now running after a reboot. Thank you.

But I have an other problem, now with Portnainer. Its status stay on "restarting". Then it's not running and I can't access to the web interface.

Zitat von macom

How do you know it is not running?

I said that because on the OMV web interface, the Portainer's status is always "Restarting" and I can't access to the web interface of Portainer.

Here the output of docker ps -a

Zitat von macom

docker logs --tail 50 --timestamps portainer

2020-10-16T15:41:39.017289324Z 2020/10/16 15:41:39 invalid character '\x00' after top-level value

2020-10-16T15:41:41.297527385Z 2020/10/16 15:41:41 invalid character '\x00' after top-level value

2020-10-16T15:41:43.423543658Z 2020/10/16 15:41:43 invalid character '\x00' after top-level value

2020-10-16T15:41:45.689125483Z 2020/10/16 15:41:45 invalid character '\x00' after top-level value

2020-10-16T15:41:47.943309203Z 2020/10/16 15:41:47 invalid character '\x00' after top-level value

2020-10-16T15:41:50.985192190Z 2020/10/16 15:41:50 invalid character '\x00' after top-level value

2020-10-16T15:41:55.672752426Z 2020/10/16 15:41:55 invalid character '\x00' after top-level value

2020-10-16T15:42:03.659010337Z 2020/10/16 15:42:03 invalid character '\x00' after top-level value

2020-10-16T15:42:18.496471201Z 2020/10/16 15:42:18 invalid character '\x00' after top-level value

2020-10-16T15:42:45.853785506Z 2020/10/16 15:42:45 invalid character '\x00' after top-level value

2020-10-16T15:43:38.704388086Z 2020/10/16 15:43:38 invalid character '\x00' after top-level value

2020-10-16T15:44:40.286004846Z 2020/10/16 15:44:40 invalid character '\x00' after top-level value

2020-10-16T15:45:41.950314594Z 2020/10/16 15:45:41 invalid character '\x00' after top-level value

2020-10-16T15:46:43.572425555Z 2020/10/16 15:46:43 invalid character '\x00' after top-level value

2020-10-16T15:47:45.279701883Z 2020/10/16 15:47:45 invalid character '\x00' after top-level value

2020-10-16T15:48:46.966312006Z 2020/10/16 15:48:46 invalid character '\x00' after top-level value

2020-10-16T15:49:48.557301066Z 2020/10/16 15:49:48 invalid character '\x00' after top-level value

2020-10-16T15:50:50.140957886Z 2020/10/16 15:50:50 invalid character '\x00' after top-level value

2020-10-16T15:51:51.799549298Z 2020/10/16 15:51:51 invalid character '\x00' after top-level value

2020-10-16T15:52:53.428425283Z 2020/10/16 15:52:53 invalid character '\x00' after top-level value

2020-10-16T15:53:55.076965517Z 2020/10/16 15:53:55 invalid character '\x00' after top-level value

2020-10-16T15:54:56.633405600Z 2020/10/16 15:54:56 invalid character '\x00' after top-level value

2020-10-16T15:55:58.261692024Z 2020/10/16 15:55:58 invalid character '\x00' after top-level value

2020-10-16T15:57:00.420454804Z 2020/10/16 15:57:00 invalid character '\x00' after top-level value

2020-10-16T15:58:02.265423171Z 2020/10/16 15:58:02 invalid character '\x00' after top-level value

2020-10-16T15:59:04.374252568Z 2020/10/16 15:59:04 invalid character '\x00' after top-level value

2020-10-16T16:00:06.893799099Z 2020/10/16 16:00:06 invalid character '\x00' after top-level value

2020-10-16T16:02:49.306068116Z 2020/10/16 16:02:49 invalid character '\x00' after top-level value

2020-10-16T16:02:52.499501018Z 2020/10/16 16:02:52 invalid character '\x00' after top-level value

2020-10-16T16:02:54.788205129Z 2020/10/16 16:02:54 invalid character '\x00' after top-level value

2020-10-16T16:02:57.032422618Z 2020/10/16 16:02:57 invalid character '\x00' after top-level value

2020-10-16T16:02:59.423007620Z 2020/10/16 16:02:59 invalid character '\x00' after top-level value

2020-10-16T16:03:02.750032804Z 2020/10/16 16:03:02 invalid character '\x00' after top-level value

2020-10-16T16:03:07.461849184Z 2020/10/16 16:03:07 invalid character '\x00' after top-level value

2020-10-16T16:03:15.470653174Z 2020/10/16 16:03:15 invalid character '\x00' after top-level value

2020-10-16T16:03:29.887497432Z 2020/10/16 16:03:29 invalid character '\x00' after top-level value

2020-10-16T16:03:57.023157972Z 2020/10/16 16:03:57 invalid character '\x00' after top-level value

2020-10-16T16:04:49.781452867Z 2020/10/16 16:04:49 invalid character '\x00' after top-level value

2020-10-16T16:05:51.404241633Z 2020/10/16 16:05:51 invalid character '\x00' after top-level value

Ok thank you, I will take a look if I can find something on Google.

What would be the proper way to reinstall Portainer? Because I tried to delete it and install it again from the OMV web interface, but the problem is still there.

Yes it's what I did but the problem persist

I found a solution here in this thread 🙂