Database disk image is malformed

Node Operators troubleshooting
,
1

I cant seem to figure out how to fix this error. It looks like it cant set the migration table but which database is corrupted? I checked all of them and they are ok. I had two corrupted DB (orders and bandwidth) and I fixed them but now I cant start my node again.

docker logs --tail 500 storagenode
runtime.main:203
main.main:320
storj.io/private/process.ExecCustomDebug:70
storj.io/private/process.ExecWithCustomConfig:88
github.com/spf13/cobra.(*Command).Execute:885
github.com/spf13/cobra.(*Command).ExecuteC:945
github.com/spf13/cobra.(*Command).execute:840
storj.io/storj/storagenode/storagenodedb.(*DB).MigrateToLatest:293
storj.io/storj/private/migrate.(*Migration).Run:170
storj.io/storj/private/dbutil/txutil.WithTx:36
storj.io/storj/private/dbutil/txutil.withTxOnce:75
storj.io/storj/private/migrate.(*Migration).Run.func1:171
storj.io/storj/private/migrate.SQL.Run:252
Error: Error creating tables for master database on storagenode: migrate: database disk image is malformed
2020-07-17T15:23:28.269Z INFO db.migration.27 Add index archived_at to ordersDB
2020-07-17T15:23:28.246Z INFO Telemetry enabled
2020-07-17T15:23:27.321Z INFO Operator wallet {“Address”: “”}
2020-07-17T15:23:27.321Z INFO Operator email {“Address”: “”}
2020-07-17T15:23:27.299Z INFO Configuration loaded {“Location”: “/app/config/config.yaml”}

2

You can start checking all dbs

3

I checked them and they all came back ok.

4

Is it a docker or Windows GUI ?

5

im on centos 8 and they dont have docker so im using podman. Its been working great for a month since ive moved everything over

6

I see another SNO got docker installed but had a bad HDD.

7

welp… I got it working again. I went back to the old database backup and did the recovery process over again and it fixed the problem (whatever that was). Not sure what went wrong the first time but happy I got everything working again.