I truly think Nodes should fix themselves whenever possible.
Let’s take database corruption as an example: it is a common problem and is likely to keep happening in the future to many SNOs as a simple power outage can cause this issue.
There is a known procedure (https://support.storj.io/hc/en-us/articles/360029309111?_ga=2.6254707.1330931111.1590396912-5329027.1585062953) for fixing corrupted/malformed databases.
The Node could run a pragma check on its database files regularly (or when a Node just got started after a reboot, or an update), or whenever something goes wrong with it.
If a database file proves to be broken, the Node could pause (disconnect from the sat’) and take the time to check and repair what can be repaired.
If the repair fails, then the SNO should be warned, and the node suspended I guess.
More globally, I think that whenever a problem has a known solution that could be applied by the Node software itself automatically, this should be implemented.
That would greatly improve SNOs’ peace of mind, and also the STORJ network quality/reliability, I think
This is somehow related to Ability to recover part of lost data / restore the node from backup