Recovering Database with error "File corrupted while reading record: null"

Drew Blood 10 months ago updated by Tom 10 months ago 2
I had a heavily customized install of Ubooquity (Docker/Synology) a couple years back that I tweaked once too many times and broke it. I'd like to recover my old instance rather than start from scratch. Does this error give you any leads on what I should try first?  The error in the log is as follows:

ata.database.d - Cound not get number of existing tables org.h2.jdbc.JdbcSQLException: File corrupted while reading record: null. Possible solution: use the recovery tool [90030-193] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.message.DbException.get(DbException.java:168) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.mvstore.db.MVTableEngine$Store.convertIllegalStateException(MVTableEngine.java:195) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:167) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:99) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.engine.Database.getPageStore(Database.java:2468) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.engine.Database.open(Database.java:695) ~[h2-1.4.193.jar.5380734851354284907.tmp:1.4.193] at org.h2.engine.Datab

I'll leave this up but I ended up just rescanning and pulling my theme back over from my backup. 


First time I see this kind of error.

Apparently the "recovery tool" it mentions is the one offered by the H2 database used internally by Ubooquity: