How to setup hardware watchdog?

[Ranger21]

How do i setup hardware watchdog on tos6? im using T4-424

[Ranger21]

My Nas was unavailable by network, ssh port 22 connection refused, web page of tos was giving error 504 and it was using unusually more power 34 watts instead of "idle" 24 watt. Luckily i have smart plug to remotely shutdown power and boot nas again.

[Ranger21]

Oh, i forgot that i had to use port 9222 for ssh, so maybe it would be possible to Access nas by ssh.

But neither of my docker containers were running and tos webpage were giving error 504 gateway timeout

[Ranger21]

Now my nas is doing something, consuming a lot of power (37w instead of 24w), webpage gives 502 error, ssh doesn't connect. Planned shutdown beeped beeper but for 3 hours Nas didn't shutdown.
I can't know what is nas doing, I'll try to wait until its finished what is doing.

[Ranger21]

And i have awful hard drive noises, so it's doing something with hard drives.

[Gremlin]

The 'automatic switch' shutdown has probably had a bad side effect. These devices do not really like a sudden power off from the mains side. If you read around these forums you will find several examples of issues after mains power failure.

[TMroy]

Using a smart power socket to control the power on/off of a NAS device is a very risky practice. Suddenly cutting off the power supply can lead to damage to the system, file system, and even the hard disks.

[Ranger21]

Using a smart power socket to control the power on/off of a NAS device is a very risky practice. Suddenly cutting off the power supply can lead to damage to the system, file system, and even the hard disks.

My nas again got stuck with 502 error and no access on ssh port and it was using more power than usual. I left it for 24 hours, but it didn't recover from this hangup, so I had to do power reboot.

Is there a way to setup hardware watchdog on this nas? Does motherboard support something like that?

[TMzethar]

There is currently no way to support your idea.
It looks like the reason you're trying to implement a remote on/off switch is because the power consumption is higher than expected. It is possible that you are running processes with higher occupancy, about this you can go to TOS - Resource Monitor - Processes and check the status.
If you want to use remote switching, you can perform a shutdown through the remote TOS web page first, wait a few minutes for the TNAS to finish shutting down smoothly and then use remote switching.
According to your description, it looks like the shutdown process is stuck on something. please generate and download the log report in TOS > Technical Support > Report Issues after the next startup, and then send it to us through our official website customer service window or technical support email for inspection .

[TMroy]

I'm afraid the file system on your disk might be corrupted.