How to prevent NAS from rebooting

  • Hi all,


    when I came home from work today, I realized, that my NAS had rebooted.

    I first suspected some power outage, but then I found this in my mails:


    Code
    [...]
    Description: unable to read filesystem '/srv/dev-disk-by-uuid-5079354d-773d-46e7-9703-a89333548b89' state
    
    This triggered the monitoring system to: restart
    [...]


    This is clearly something I don't want.

    It ok, do be informed or alerted.

    I would even expect (and like) to see this information, when I log into the Web-UI.

    And then it's me to decide that I do a reboot (or maybe not).

    But I don't want the NAS to boot automatically.


    Where can I disable this?


    Many thanks,

    quack

    TerraMaster T6-423

    Qnap TS-853A

    Qnap TS-451+

    Qnap TS-259 Pro+

  • ok, then I might have misunderstood that mail notification.


    But my system was indeed rebooted.

    I had several remote sessions open, which are now not existing any longer.

    As well as the job that I had running, which I estimated to run for at least 12h maybe 24h -- no longer there.

    The NAS has currently an uptime of about 5 hours, which by coincidence matches with the time of the above mail...


    So if it wasn't the monitoring system that restarted my NAS, how do I find out, what restarted it and why ?

    TerraMaster T6-423

    Qnap TS-853A

    Qnap TS-451+

    Qnap TS-259 Pro+

  • looking into the systemd journal and searching for the last boot I found several entries before the reboot, which from my judgement are not directly related to the reboot. Seems more like it might have crashed...

    (not sure about that - it's the first time I have a look in that kind of log)


    first of all the NUT service is restarted every few seconds

    about every minute I see: CRITICAL - Unable to load wakealarm table.

    From time to time I see error messages that seem to come from smartmontools


    Based on that I wanted to at least get rid of some of those messages and disabled UPS in the Web-UI.


    That gave this error which seems to be OMV-specific:



    Any idea, what might be the problem?



    (The system was installed from scratch a few days / weeks ago. It is still not in day by day usage. I'm still in the process of transferring all my data to it.)

    TerraMaster T6-423

    Qnap TS-853A

    Qnap TS-451+

    Qnap TS-259 Pro+

  • seems like I have a similar problem at various places.

    I tried a few things just to see, where the problem is...


    For example, when I try to change monitoring / notifications at System / Notification / Events I get:



    When I try to create an Wakealarm at Services / Wakealarm I get:



    So it's always ERROR: The state 'xyz' does not exist


    Anybody knows what this is about and what I can do now?


    TerraMaster T6-423

    Qnap TS-853A

    Qnap TS-451+

    Qnap TS-259 Pro+

    • Official Post

    Do you have installed the mdadm and wakeslarm plugins?

  • just out of curiosity I did apt list --installed | grep openmedia before reinstalling.

    Output was:


    I assume instead of openmediavault-mdadm I should reinstall openmediavault-md.


    I did reinstall both modules and after that the above errors disappeared.

    Thanks for the suggestion.


    Should I maybe do a reinstall for all of the omv modules?

    Or asked the other way round:

    Can I check which salts states are available on my system (as-is list) and can I compare that to a to-be list?


    Any idea how that could have been disappeared?



    TerraMaster T6-423

    Qnap TS-853A

    Qnap TS-451+

    Qnap TS-259 Pro+

    • Official Post

    Any idea how that could have been disappeared?

    An package update process that was broken/interrupted somehow or a corrupted file system.

    Can I check which salts states are available on my system (as-is list) and can I compare that to a to-be list?

    There is a command that is listing all available commands, but that does not help. I suggest to wait until another error occurs; in that case you know what to do. Until then i think it is not necessary to do any additional action.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!