Random shut-downs since OMV 7 upgrade

Hello forum!

As per the title of the thread, I am experiencing random shut downs since I upgraded from OMV 6 to OMV 7. Before you suggest to check the logs, I did, but they are gone. After each shut down, the logs seem to reset. In other words, I can only see logs back to the point when the server was restarted. Anything before that is gone. For example, the last shut down happened somewhere between 21.08 and 22.08. The logs start at 22.08 at 18:01, when I manually turned on the server. I also get no notifications regarding high usage or high system load. I also checked under /var/log/syslog and got exactly the same.

Some additional notes:

1. Regarding my hardware, see my signature.
2. The hardware has not changed from OMV 6 to OMV 7.
3. The upgrade process went without issues.
4. The problem did not happened before. The server ran for months without interruptions.
5. All the drives are healthy. Smart reports no errors.
6. Temperatures are all OK (drives at ~29°C, CPU idling at 40°C)
7. I have no clue when the shut down happens. I only notice it because a. Wireguard does not work or b. I cannot reach my Plex server. Hence, I have no idea if something in particular triggers the shut down.
8. It happens randomly.
9. Plug-ins installed: Docker, mergerfs, snapraid, Rsync, flash memory, UPS, wireguard.
10. Auto shut down plug is is not installed

So, that's pretty much it. Are any other logs hidden somewhere, or is it normal that the logs reset after an abnormal shut down?

Any help or advice is appreciated.

I am really confused as to why my signature is not visible. I see it on Firefox on windows, but not in my phone.

I am running a X86 system, kind of old one (third generation core I7).

The only thing that could produce such a load is Plex. But then again, that happens only when new files are added to the library and the music fingerprints are calculated. Or perhaps Snapraid? But even if that's the case, the system managed it without issues with OMV 6.

Also, when the load reaches such a point, a message is generated and I receive a notification. Hence, I am not really sure that the problem has something to do with it.

Quote from votdev

OMV is using a watchdog to restart systems automatically when they are in a dead situation.

If your system is under heavy load, it might happen that the watchdog restarts the system because due the load it can’t be updated in time. I have to say that the system must be under very very very heavy load in that case.

You need to check the journal for messages before the system is restarted.

I checked the messages journal, and as said before, the messages start at the time when the server was last started. Everything before is not available. The messages are also sent to my email account, but until now I have not received anything unusual.

Hello again!

I have an update on the random shut-down issue. After upgrading my server to OMV 7, I had also planned to upgrade several hardware components (read new motherboard, a CPU 4 generations newer, and a new OS SSD). The migration was very painless I have to say, and the server has been online for the last 7 days without a hiccup.

If the system remains without issues, I would then conclude that it could have been one of 3 things:

- Although the upgrade to OMV 7 went smooth, perhaps something got corrupted during the update, triggering the shut downs?

- The hardware was on the old side (3rd generation Intel CPU). Perhaps the new Debian version was not happy with one of the old hardware components? (

- Despite 4 to 5 years of continuous use on the server, the old OS SSD showed no signs of wear and its SMART values were all OK. Perhaps the OS drive started kicking the bucket? But then, why only after upgrading?

I believe that one of the first two options could have been the culprit. I'll report back if the system shuts down again.