Maybe 20-30 days ago, I can't remember.
Loosing everything after power loss
-
- OMV 5.x
- Nabukodonosor
-
Have you checked the config.xml file?
There is still your claim araumd it has been reset to initial state.
-
This does not look like a freh install, it has the network set up, one data disk mounted, several shared folders defined and some smb shares configured, but only one user
Docker storage on: /var/lib/docker (not moved to a data disk)
-
A friend of mine has an OMV 5 system running, without a UPS, and last night there was a power outage at his place, and he lost every single setting on his OMV. His media is still there, all data etc, every docker container, but it's like everything was just installed a minute ago. Is it possible that linux is this crappy?
the issue has nothing to do with Linux, but unless Docker gets told to persist changes, everything will be reset to default when a reboot occurs.
RTFM (read the fine manual) on Docker configuration would be the recommendation to your friend.
Assuming your friend did the configuration, he should write the forum post with all details too! Providing second hand information wont allow to fix this issue from my view because too many assumptions and interpretations will prevent finding the root cause reliably.
-
I don't think this is true, that you have to tell Docker to persist changes
Using volumes (path or actual docker volume) is how you persist changes or make permanent. If the volume was wrong in the compose file or run command, the data would only exist in the container. A power outage would "reset" the container to default.
-
If docker started the containers before the data disks where mounted this is the effect you will see.
check the directories while data disks are unmounted too. -
So, after I turned on the machine, it was all set to defaults, like I said. But then, I started OMV dashboard, and I got that yellow button at the top, saying that some changes occured, and if I wanted to apply them. I clicked the Apply button, and after that everything went back to normal.
-
I do not understand how omv settings relate to docker container not being there except for a not mounted disk.
-
This is a bizarre thread.
It's either a poltergeist has taken up residence in your machine.
OR
You have drives not mounting correctly and the system is working on data underlying the mount point possibly an original installation.
Anytime you have power outage that appears to reset machines you need to immediately suspect dead CMOS battery for one possibility.
This will cause your BIOS to reset to default values and possibly different boot order.
Beyond that, a lot of the things that have been described in this thread are just not possible.
-
What is happening to the ports? Is it 83 or 80 you are trying to access?
And regarding the "reset", check partitions and the external disk. If docker root is moved to the external disk and it boots without this disk, docker will still use the directory defined, but on the os disk.
If the external disk is mounted, try unmounting it and check the directory in /srv/dev-disk-by-... if anything is there. If yes, you have the explanation.
-
In your screenshot you are accessing heimdall (port 83( and ask for a file/path 192.168.0.22:80 which is abviously not there, hence the 404 aka HTTP not found.
Have you tried the correct url http://192.168.0.222?
-
The question is: Is it only heimdall or is OMV not available?
You can check what heimdall is doing if you open the web developer console and switch to the networks tab.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!