Used_serial: schema check failed: database disk image is malformed [SOLVED]

Node Operators troubleshooting
, ,
1

Hi i got cpu bluescreen and restarted a computer hardway, the service dont wnat to start, its getting stopped right after that, and in storagenode.log is just INFO
operator mail: mymail
operator wallet: my wallet
db.migration dabase version (“version”: 38)

but real errors are in storagenode-updater.log:
it started at 11:32 then i shut down the pc

Summary

2020/05/19 17:02:03 storagenode version is up to date

2020/05/19 17:17:01 downloading versions from https://version.storj.io

2020/05/19 17:17:02 storagenode version is up to date

2020/05/19 17:32:01 downloading versions from https://version.storj.io

2020/05/19 17:32:03 storagenode version is up to date

2020/05/19 17:47:01 downloading versions from https://version.storj.io

2020/05/19 17:47:02 storagenode version is up to date

2020/05/19 18:02:01 downloading versions from https://version.storj.io

2020/05/19 18:02:03 storagenode version is up to date

2020/05/19 18:17:00 downloading versions from https://version.storj.io

2020/05/19 18:17:02 storagenode version is up to date

2020/05/19 18:32:00 downloading versions from https://version.storj.io

2020/05/19 18:32:02 storagenode version is up to date

2020/05/19 18:47:00 downloading versions from https://version.storj.io

2020/05/19 18:47:01 storagenode version is up to date

2020/05/19 19:02:00 downloading versions from https://version.storj.io

2020/05/19 19:02:03 storagenode version is up to date

2020/05/19 19:17:00 downloading versions from https://version.storj.io

2020/05/19 19:17:09 storagenode version is up to date

2020/05/19 19:32:00 downloading versions from https://version.storj.io

2020/05/19 19:32:04 storagenode version is up to date

2020/05/19 19:47:01 downloading versions from https://version.storj.io

2020/05/19 19:47:03 storagenode version is up to date

2020/05/19 20:02:00 downloading versions from https://version.storj.io

2020/05/19 20:02:03 storagenode version is up to date

2020/05/19 20:17:00 downloading versions from https://version.storj.io

2020/05/19 20:17:02 storagenode version is up to date

2020/05/19 20:32:00 downloading versions from https://version.storj.io

2020/05/19 20:32:03 storagenode version is up to date

2020/05/19 20:47:00 downloading versions from https://version.storj.io

2020/05/19 20:47:02 storagenode version is up to date

2020/05/19 21:02:01 downloading versions from https://version.storj.io

2020/05/19 21:02:04 storagenode version is up to date

2020/05/19 21:17:01 downloading versions from https://version.storj.io

2020/05/19 21:17:03 storagenode version is up to date

2020/05/19 21:32:01 downloading versions from https://version.storj.io

2020/05/19 21:32:03 storagenode version is up to date

2020/05/19 21:47:01 downloading versions from https://version.storj.io

2020/05/19 21:47:04 storagenode version is up to date

2020/05/19 22:02:01 downloading versions from https://version.storj.io

2020/05/19 22:02:03 storagenode version is up to date

2020/05/19 22:17:01 downloading versions from https://version.storj.io

2020/05/19 22:17:03 storagenode version is up to date

2020/05/19 22:32:01 downloading versions from https://version.storj.io

2020/05/19 22:32:03 storagenode version is up to date

2020/05/19 22:47:01 downloading versions from https://version.storj.io

2020/05/19 22:47:02 storagenode version is up to date

2020/05/19 23:02:01 downloading versions from https://version.storj.io

2020/05/19 23:02:03 storagenode version is up to date

2020/05/19 23:17:01 downloading versions from https://version.storj.io

2020/05/19 23:17:02 storagenode version is up to date

2020/05/19 23:32:01 downloading versions from https://version.storj.io

2020/05/19 23:32:03 storagenode version is up to date

2020/05/19 23:47:01 downloading versions from https://version.storj.io

2020/05/19 23:47:04 storagenode version is up to date

2020/05/20 00:02:01 downloading versions from https://version.storj.io

2020/05/20 00:02:03 storagenode version is up to date

2020/05/20 00:17:01 downloading versions from https://version.storj.io

2020/05/20 00:17:03 storagenode version is up to date

2020/05/20 00:32:01 downloading versions from https://version.storj.io

2020/05/20 00:32:03 storagenode version is up to date

2020/05/20 00:47:01 downloading versions from https://version.storj.io

2020/05/20 00:47:03 storagenode version is up to date

2020/05/20 01:02:01 downloading versions from https://version.storj.io

2020/05/20 01:02:03 storagenode version is up to date

2020/05/20 01:17:01 downloading versions from https://version.storj.io

2020/05/20 01:17:03 storagenode version is up to date

2020/05/20 01:32:01 downloading versions from https://version.storj.io

2020/05/20 01:32:03 storagenode version is up to date

2020/05/20 01:47:02 downloading versions from https://version.storj.io

2020/05/20 01:47:04 storagenode version is up to date

2020/05/20 02:02:01 downloading versions from https://version.storj.io

2020/05/20 02:02:04 storagenode version is up to date

2020/05/20 02:17:01 downloading versions from https://version.storj.io

2020/05/20 02:17:03 storagenode version is up to date

2020/05/20 02:32:01 downloading versions from https://version.storj.io

2020/05/20 02:32:08 storagenode version is up to date

2020/05/20 02:47:01 downloading versions from https://version.storj.io

2020/05/20 02:47:03 storagenode version is up to date

2020/05/20 03:02:01 downloading versions from https://version.storj.io

2020/05/20 03:02:03 storagenode version is up to date

2020/05/20 03:17:01 downloading versions from https://version.storj.io

2020/05/20 03:17:04 storagenode version is up to date

2020/05/20 03:32:01 downloading versions from https://version.storj.io

2020/05/20 03:32:03 storagenode version is up to date

2020/05/20 03:47:01 downloading versions from https://version.storj.io

2020/05/20 03:47:03 storagenode version is up to date

2020/05/20 04:02:01 downloading versions from https://version.storj.io

2020/05/20 04:02:03 storagenode version is up to date

2020/05/20 04:17:01 downloading versions from https://version.storj.io

2020/05/20 04:17:03 storagenode version is up to date

2020/05/20 04:32:01 downloading versions from https://version.storj.io

2020/05/20 04:32:03 storagenode version is up to date

2020/05/20 04:47:01 downloading versions from https://version.storj.io

2020/05/20 04:47:02 storagenode version is up to date

2020/05/20 05:02:01 downloading versions from https://version.storj.io

2020/05/20 05:02:04 storagenode version is up to date

2020/05/20 05:17:01 downloading versions from https://version.storj.io

2020/05/20 05:17:03 storagenode version is up to date

2020/05/20 05:32:01 downloading versions from https://version.storj.io

2020/05/20 05:32:03 storagenode version is up to date

2020/05/20 05:47:01 downloading versions from https://version.storj.io

2020/05/20 05:47:03 storagenode version is up to date

2020/05/20 06:02:01 downloading versions from https://version.storj.io

2020/05/20 06:02:03 storagenode version is up to date

2020/05/20 06:17:01 downloading versions from https://version.storj.io

2020/05/20 06:17:03 storagenode version is up to date

2020/05/20 06:32:01 downloading versions from https://version.storj.io

2020/05/20 06:32:02 storagenode version is up to date

2020/05/20 06:47:01 downloading versions from https://version.storj.io

2020/05/20 06:47:03 storagenode version is up to date

2020/05/20 07:02:01 downloading versions from https://version.storj.io

2020/05/20 07:02:03 storagenode version is up to date

2020/05/20 07:17:02 downloading versions from https://version.storj.io

2020/05/20 07:17:05 storagenode version is up to date

2020/05/20 07:32:01 downloading versions from https://version.storj.io

2020/05/20 07:32:07 storagenode version is up to date

2020/05/20 07:47:01 downloading versions from https://version.storj.io

2020/05/20 07:47:03 storagenode version is up to date

2020/05/20 08:02:01 downloading versions from https://version.storj.io

2020/05/20 08:02:03 storagenode version is up to date

2020/05/20 08:17:01 downloading versions from https://version.storj.io

2020/05/20 08:17:05 storagenode version is up to date

2020/05/20 08:32:07 downloading versions from https://version.storj.io

2020/05/20 08:32:25 version control client error: Get https://version.storj.io: net/http: TLS handshake timeout

2020/05/20 08:47:01 downloading versions from https://version.storj.io

2020/05/20 08:47:03 storagenode version is up to date

2020/05/20 09:02:01 downloading versions from https://version.storj.io

2020/05/20 09:02:03 storagenode version is up to date

2020/05/20 09:17:01 downloading versions from https://version.storj.io

2020/05/20 09:17:04 storagenode version is up to date

2020/05/20 09:32:02 downloading versions from https://version.storj.io

2020/05/20 09:32:10 storagenode version is up to date

2020/05/20 09:47:01 downloading versions from https://version.storj.io

2020/05/20 09:47:02 storagenode version is up to date

2020/05/20 10:02:01 downloading versions from https://version.storj.io

2020/05/20 10:02:03 storagenode version is up to date

2020/05/20 10:17:02 downloading versions from https://version.storj.io

2020/05/20 10:17:05 storagenode version is up to date

2020/05/20 10:32:01 downloading versions from https://version.storj.io

2020/05/20 10:32:04 storagenode version is up to date

2020/05/20 10:47:01 downloading versions from https://version.storj.io

2020/05/20 10:47:03 storagenode version is up to date

2020/05/20 11:17:14 downloading versions from https://version.storj.io

2020/05/20 11:17:16 storagenode version is up to date

2020/05/20 11:32:10 downloading versions from https://version.storj.io

2020/05/20 11:32:32 version control client error: Get https://version.storj.io: dial tcp 34.69.12.165:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

2020/05/20 11:39:17 Stop/Shutdown request received.

2020/05/20 11:40:04 downloading versions from https://version.storj.io

2020/05/20 11:40:07 storagenode version is up to date

2020/05/20 11:45:44 Stop/Shutdown request received.

2020/05/20 11:46:33 downloading versions from https://version.storj.io

2020/05/20 11:46:34 storagenode version is up to date

2020/05/20 11:59:37 Stop/Shutdown request received.

2020/05/20 12:00:24 downloading versions from https://version.storj.io

2020/05/20 12:00:27 storagenode version is up to date

2020/05/20 12:15:25 downloading versions from https://version.storj.io

2020/05/20 12:15:26 storagenode version is up to date

2020/05/20 12:18:22 Stop/Shutdown request received.

2020/05/20 12:19:15 downloading versions from https://version.storj.io

2020/05/20 12:19:18 storagenode version is up to date

2020/05/20 12:26:26 Stop/Shutdown request received.

2020-05-20T12:26:54.982+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “server.address”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “operator.email”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “storage.path”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.output”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.stack”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.caller”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.development”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.encoding”}

2020-05-20T12:26:54.983+0200 INFO Invalid configuration file value for key {“Key”: “log.level”}

2020-05-20T12:26:54.985+0200 INFO tracing disabled

2020-05-20T12:26:54.999+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T12:26:57.214+0200 INFO Version is up to date. {“Service”: “storagenode”}

2020-05-20T12:26:57.214+0200 INFO Version is up to date. {“Service”: “storagenode-updater”}

2020-05-20T12:28:56.053+0200 INFO Stop/Shutdown request received.

2020-05-20T12:29:37.205+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

2020-05-20T12:29:37.215+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “operator.email”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “storage.path”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “server.address”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file value for key {“Key”: “log.development”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file value for key {“Key”: “log.level”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file value for key {“Key”: “log.output”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file value for key {“Key”: “log.stack”}

2020-05-20T12:29:37.216+0200 INFO Invalid configuration file value for key {“Key”: “log.caller”}

2020-05-20T12:29:37.526+0200 INFO tracing disabled

2020-05-20T12:29:37.605+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T12:29:40.980+0200 INFO Version is up to date. {“Service”: “storagenode”}

2020-05-20T12:29:40.981+0200 INFO Version is up to date. {“Service”: “storagenode-updater”}

2020-05-20T12:38:59.863+0200 INFO Stop/Shutdown request received.

2020-05-20T12:43:33.437+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “operator.email”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “storage.path”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file key {“Key”: “server.address”}

2020-05-20T12:43:33.438+0200 INFO Invalid configuration file value for key {“Key”: “log.level”}

2020-05-20T12:43:33.439+0200 INFO tracing disabled

2020-05-20T12:43:33.452+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T12:43:34.479+0200 INFO Version is up to date. {“Service”: “storagenode”}

2020-05-20T12:43:34.479+0200 INFO Version is up to date. {“Service”: “storagenode-updater”}

2020-05-20T12:53:36.506+0200 INFO Stop/Shutdown request received.

2020-05-20T12:54:18.396+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “operator.email”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “server.address”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file key {“Key”: “storage.path”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file value for key {“Key”: “log.encoding”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file value for key {“Key”: “log.level”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file value for key {“Key”: “log.output”}

2020-05-20T12:54:18.398+0200 INFO Invalid configuration file value for key {“Key”: “log.stack”}

2020-05-20T12:54:18.417+0200 INFO tracing disabled

2020-05-20T12:54:18.435+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T12:54:19.251+0200 INFO Stop/Shutdown request received.

2020-05-20T12:54:19.256+0200 ERROR Error retrieving version info. {“error”: “version control client error: Get https://version.storj.io: context canceled”, “errorVerbose”: “version control client error: Get https://version.storj.io: context canceled\n[tstorj.io/storj/private/version/checker.(*Client).All:66\n\tmain.loopFunc:24\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tmain.cmdRun:115\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57](http://tstorj.io/storj/private/version/checker.(*Client).All:66\n\tmain.loopFunc:24\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tmain.cmdRun:115\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:55\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57)”}

2020-05-20T12:55:02.145+0200 INFO Configuration loaded {“Location”: “C:\Program Files\Storj\Storage Node\config.yaml”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “storage.path”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “server.address”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-disk-space”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “server.private-address”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “operator.wallet”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “server.debug-log-traffic”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “operator.email”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “contact.external-address”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file key {“Key”: “storage.allocated-bandwidth”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file value for key {“Key”: “log.development”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file value for key {“Key”: “log.output”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file value for key {“Key”: “log.stack”}

2020-05-20T12:55:02.152+0200 INFO Invalid configuration file value for key {“Key”: “log.caller”}

2020-05-20T12:55:02.234+0200 INFO tracing disabled

2020-05-20T12:55:02.281+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T12:55:03.895+0200 INFO Version is up to date. {“Service”: “storagenode”}

2020-05-20T12:55:03.896+0200 INFO Version is up to date. {“Service”: “storagenode-updater”}

2020-05-20T13:10:02.294+0200 INFO Downloading versions. {“Server Address”: “https://version.storj.io”}

2020-05-20T13:10:04.235+0200 INFO Version is up to date. {“Service”: “storagenode”}

2020-05-20T13:10:04.235+0200 INFO Version is up to date. {“Service”: “storagenode-updater”}

iuninstaleed the node, restarted computer, and instaled storage node with newest instaler 1.4.2. but this log error reapeats about invalid key, what to do?

PS. i always use notepad++, thats not a problem, problem was windows 10, bit 64 uppdate, it cause this in first place. its GUI node.

2

Uninstall again, remove the storage node folder in program files, then reinstall. Make sure you fill in the right data during install. It should recreate a functioning config.yaml.

4

Hey there was a post here that was flagged by other community members for using profanity, thus detracting from the value of the conversation. Answers and atmosphere are both important, and we’re always trying to to do our best on both.

I want to say that even though the post was flagged due to swearing, the issue itself matters, and has been flagged to engineering \ . Will post any updates as they come through.

2 Likes
5

It’s known issue, does not influences either updater or storagenode and can be safely ignored.
It’s not related to the config.yaml itself, it’s related to the storagenode-updater, which doesn’t aware of keys for storagenode. You do not need to modify your config.yaml

What is the real problem?
Is the node offline?
If so, please, check all points from the checklist:

1 Like
6

real problem is the node is not even visible in node dashboard, cant see if online or offline, but i asume, its offline hard, due to Services turns instantly to “Stopped” after it starts, or after i start it. The real problem i was trying to move that node to fresh windows, and it wont work the same, so, tommoro i will be trying if i can run new fresh node on this windows to eliminate a windows problems made by update, but im tired, im slowly accepting this node and its ~70$ on it, is probbaly done, it might be db damage i dont know how to debug that, its just dont work and i shoot some troubles from '19 its been 7 months or so, neved got such case, just donknow whats broken after those new windows 10 64bit updates, they were updating .net 3.8 and 4.5 i saw

1 Like
7

Please, change the log level from info to debug in the config.yaml, save it and restart the service.
Then take last 20 lines from the log (Powershell)

Get-Content -Tail 20 "C:\Program Files\Storj\Storage Node\storagenode.log"
8

Sure, please:

DEBUG

2020-05-20T23:39:56.828+0200 DEBUG Version info {“Version”: “1.4.2”, “Commit Hash”: “e4d9c2684a948b8e632abd613d35c8c21204d936”, “Build Timestamp”: “2020-05-06 20:41:44 +0200 CEST”, “Release Build”: true}

2020-05-20T23:39:57.808+0200 DEBUG version Allowed minimum version from control server. {“Minimum Version”: “1.1.0”}

2020-05-20T23:39:57.808+0200 DEBUG version Running on allowed version. {“Version”: “1.4.2”}

2020-05-20T23:39:57.823+0200 INFO db.migration Database Version {“version”: 38}

2020-05-20T23:39:57.823+0200 DEBUG telemetry Initialized batcher {“ID”: “12mMKmuNMzBx5uhz9MoQU7Eddr3tN5wkyqoidoYkzKVMCAiTsrv”}

2020-05-20T23:40:01.521+0200 DEBUG Unrecoverable error {“error”: “Error during preflight check for storagenode databases: storage node preflight database error: used_serial: schema check failed: database disk image is malformed\n[tstorj.io/storj/storagenode/storagenodedb.(*DB).Preflight:304\n\tmain.cmdRun:190\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57](http://tstorj.io/storj/storagenode/storagenodedb.(*DB).Preflight:304\n\tmain.cmdRun:190\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57)”, “errorVerbose”: “Error during preflight check for storagenode databases: storage node preflight database error: used_serial: schema check failed: database disk image is malformed\n[tstorj.io/storj/storagenode/storagenodedb.(*DB).Preflight:304\n\tmain.cmdRun:190\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n\tmain.cmdRun:192\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57](http://tstorj.io/storj/storagenode/storagenodedb.(*DB).Preflight:304\n\tmain.cmdRun:190\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57\n\tmain.cmdRun:192\n\tstorj.io/private/process.cleanup.func1.4:343\n\tstorj.io/private/process.cleanup.func1:361\n\tgithub.com/spf13/cobra.(*Command).execute:840\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:945\n\tgithub.com/spf13/cobra.(*Command).Execute:885\n\tstorj.io/private/process.ExecWithCustomConfig:86\n\tstorj.io/private/process.Exec:63\n\tmain.(*service).Execute.func1:66\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57)”}

i see it says: “unrecoverable”,
can i at least give the files back?
it’s 650GB of data there

9

Please, don’t panic and fix the used_serial.db:

2 Likes
10

thank You, i got so far as to 10.
And that command:

“cat /storage/dump_all.sql | grep -v TRANSACTION | grep -v ROLLBACK | grep -v COMMIT >/storage/dump_all_notrans.sql”

it says me, that “cat” is not recognized, or “grep” is not recognized

Summary

imgur.com/a/CEsTPUm

im doin it on windows 10 64bit in cmd
version 3.31.1 2020-01-27 19:55:54

11

On windows I think you need to use the docker container if you want to follow these instructions. There is a line on how to start a shell inside the docker container. 7.1.

12

oh man, not that doker again, got rid of it for windows gui and im more than happy
edit: yea, thank You @BrightSilence i really appreciate Your help, this docker tho is a still a docker, hate dealing with it :frowning:

13

I wasn’t suggesting you use docker for your node (you definitely shouldn’t on windows), just to perform this repair.

14

@Alexey im afraid its outdated, i kindly demand an update for those of us, who have to repair a .db and all they got is windows 10, no docker.
And “sqlite3.exe” of course, i got it it. ver 3.31.

REASON:
Even if i install this complicated docker again i dont know how to translate this instructions for windows gui version:

“4. Make a backup of all the sqlite3 databases. They are located in the storage folder for your data storage. For example x:\storagenode\storage\bandwidth.db , where x:\storagenode is the data folder, which you have specified in the --mount type=bind,source=x:\storagenode,destination=/app/config option of the docker run command for your storagenode , or x:\storagenode\storage in case of Windows GUI in the storage.path: option of the config.yaml file.” - too complicated for person who does not know what is doing like me.

NEXT it says:
Open a shell inside the container:
docker run --rm -it --mount type=bind,source=x:\storagenode\storage,destination=/storage sstc/sqlite3 sh

again i have to apply instrucuin from above to this line of code, that i dont understand, im supostu to replace
“x:\storagenode\storage,destination=/storage sstc/sqlite3 sh” with different paths, i dont know the syntax, dont know where to put “=/” in new code etc.

15

You can install the sqlite3 locally:

Then you can use paths locally
The cat /storage/dump_all.sql | grep -v TRANSACTION | grep -v ROLLBACK | grep -v COMMIT >/storage/dump_all_notrans.sql in the Powershell:

cat dump_all.sql | sls -NotMatch TRANSACTION | sls -NotMatch ROLLBACK | sls -NotMatch COMMIT >dump_all_notrans.sql
16

thank You, sorry to say, but looks the commands has no effect? pic:

[Album] Imgur

desnt produce any new file

[Album] Imgur
17

to repear my db I used DB.Browser.for.SQLite-3.11.2-win64

i made it like normale people with GUI interface, not command line.

1 Like
18

In the Powershell the executable files which are not in the PATH environment variable should be prefixed with & or at least a path, in your case

.\sqlite3

or

&'.\sqlite3.exe'

The first form looks simpler.

19

i used .\sqlite3 it worked, but “cat” or “.\cat” seems to not work

20

It should be. Seems your Powershell is very old.
Try this one:

Get-Content

instead of cat

21

Oo. “Get-Content” sam effect Oo