I updated my C-7 hub to 2.3.4.138 yesterday evening, and this morning the hub showed the "corrupted DB" message on the web interface (and wasn't controlling devices).
I had my pre-upgrade backup, so I just reverted to 2.3.4.134 and restored that backup.
The habitat is UPS connected, and I am not aware of any power other disruptions that could have triggered corruption.
I wonder if it's possible the upgrade exposed some corruption that was already there but not critical. Since the restore would have cleared any corruption up perhaps rolling forward again to .138 would work? You could try it and see, especially if it stays stable for a while. If it does happen again you might try tagging support and see if they can find anything in the engineering logs. There was an instance recently where a faulty power supply was causing issues, though honestly it was the first time I'd heard of a faulty power supply causing that particular issue.
For years, Hubitat has said that they expose everything useful in the Logs. Having spent hours looking at Java engine logs, I'm very grateful they have that line... but occasionally something moves across the line and becomes a "new" message in the logs... same would be true for the line for DB Corruption. I haven't read anything that explicitly says there was a change, but I also feel that it's more or less continuously reviewed.
The process of Exporting a backup and then Importing it (restore) automagically cleans the DB. Last year, we'd advise you do a DB backup, Soft Reset, then Restore that backup as a mechanism to drop corruptions. Today we can skip the soft reset because a Restore now includes the soft reset functionality. If you get a corruption, saving a backup, then restoring it should sweep away the corruptions. In other words, your restore of a previous backup MIGHT have been the cure, and the rollback of the Platform wasn't a part of it. 
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
