Page 1 of 1

TOS webui won't load after power failure

Posted: 01 May 2023, 01:55
by ByteJunk
Hey,

After a series of power loss events in my house, my TOS web ui won't load.

I SSH'ed into the machine and nginx is failing to start, with a warning about invalid conf.

I inspected the conf files, and it looks like nginx.conf contained what's usually in nginx-http.conf, and nginx-http.conf was a truncated version of nginx.conf?
After restoring nginx.conf and nginx-http.conf from the install image, it's working again.

Since these files are so critical, maybe there's some way they can be better protected during the boot sequence so that they don't written to during boot, to prevent corruption?

Re: TOS webui won't load after power failure

Posted: 04 May 2023, 00:00
by epsilonion
you have to do the following:

power off the NAS.
pull the drives.
Power it back on.

then on your computer go to the NAS IP address and eventually after counting down it will tell you to replace the drives.

when you have replaced the drives you have to go through the installation procedure again.

I get this every time I shut it down via the TOS menu, I have to reinstall the TOS again.

Re: TOS webui won't load after power failure

Posted: 04 May 2023, 03:07
by crisisacting
epsilonion wrote: 04 May 2023, 00:00get this every time I shut it down via the TOS menu, I have to reinstall the TOS again.
If that's the case, there's something wrong with your configuration.

A fresh installation on clean drives will resolve that, however reconfiguration and restoring data from backups would likely be necessary, depending on use case.

Re: TOS webui won't load after power failure

Posted: 04 May 2023, 15:17
by epsilonion
It's done it since I got the nas, restored backups twice and still does the same.

I think the answer is don't turn it off lol

Re: TOS webui won't load after power failure

Posted: 04 May 2023, 23:25
by RyanYang
We need to find ways to optimize. If you still encounter this situation, perhaps you can refer to the following content to reset the nginx configuration file first: viewtopic.php?f=81&t=2872