After a disk unmouting, I’m currently facing a similar issue with 3 of my nodes that have got database files that error with the following message when checking their PRAGMA integrity:
Error: file is not a database
I followed https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed- but it does not solve the problem, as generated “dump_all” files all contain the following:
PRAGMA foreign_keys=OFF;
BEGIN TRANSACTION;
/**** ERROR: (26) file is not a database *****/
ROLLBACK; -- due to errors
And so, the final step which is supposed to fix the file creates an empty file, as faced by @bar1 previously:
In my case we’re not talking about 1 file though, most of them are in this state:
/!\ The following database files are KO:
/home/pi/storj/mounts/disk_3/storj_node_4/revocations.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/heldamount.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/notifications.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/piece_expiration.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/pieceinfo.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/piece_spaced_used.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/pricing.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/reputation.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/satellites.db
/home/pi/storj/mounts/disk_3/storj_node_4/storage/storage_usage.db
So, yeah… Am I doomed? ^^’