Used_Serial.DB vanished

Node Operators troubleshooting
1

Hey guys,

quick question: I had a SSD failure (where my DBs where stored).
I could restore everything despite my “used_serial.db”… don’t know why there is a backup of everything, but this DB :frowning:

Is my node now doomed or can I replace it from another node or regenerate it somehow?

Regards

2
  1. Stop the storagenode
  2. Execute either with a local sqlite3 binary or with a docker version (how to run a docker version described in https://support.storj.io/hc/en-us/articles/360029309111), replace the /path/to/ to your actual path
sqlite3 /path/to/used_serial.db
  1. When you see the sqlite> prompt, execute the script:
CREATE TABLE versions (version int, commited_at text);
.exit
  1. Start the storagenode
  2. Check your logs
1 Like
3

Thanks for the fast response.
After uploading the freshly created DB I get these:

image
image748×366 11.2 KB

4

I could use your tutorial from another thread:

image
image850×398 24.1 KB

now the node is starting back up, but the “used Disc Space” is shown incorrect…no problem for me, if I get paid correctly :slight_smile:

image
image867×866 46.1 KB

5

That table is no longer there in the latest version. Make sure you update your node.

Good to see it’s up and running again though!

6

Which table do you mean?

My node is @ v1.10.1 (docker)…I didn’t get a newer yet.

7

The used_serial_ table.

But I just noticed that the error was thrown by the migration step. So, that should have automatically gotten rid of it again.

If you’re on the latest version now, you’re all good. Please disregard my previous message.