Thx @Alexey, very helpful as always
I did stop the node before running @beast’s script.
The corrupted database file was
Restoring it (command
sqlite3 used_serial.db ".read dump_all_notrans.db") took ages.
I initially had started the process on the HDD, but because it was so slow I switched to the SD card which did go faster, but it still took roughly 1 hour to recreate this 25MB file!
That’s frightening. Hope it did not kill my SD card…
I’m not sure all of that is normal, but the node is back online and for the moment, it seems like it’s working…
I still think such attempts at fixing a database should be handled by the node itself because apparently that happens regularly with sqlite databases. It could check all that after a version update for instance. Or on a regular basis.
In my case, I had a power outage a few days ago, could it be the root cause of this malformed database? If so, surely it will happen time to time to many SNOs in the future.
Just my 2 cts