I have a node that I run under Docker that won’t start due to the following error: -25T13:55:27Z ERROR failure during run {"Process": "storagenode", "error": "Failed to create storage node peer: hashstore: read config/storage/hashstore/121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6/s1/meta/has…

The hastable file is likely damaged. Use write-hashtbl to create a new one: storj/cmd/write-hashtbl at main · storj/storj Ongoing Storj v3 development. Decentralized cloud object storage that is affordable, easy to use, private, and secure. - storj/storj

seems that this should work but im getting this error Counting /hashstore/26/log-0000000000000026-00004fb6… Counting /hashstore/28/log-0000000000000028-00000000… Counting /hashstore/2c/log-000000000000002c-00004fb9… Counting /hashstore/2e/log-000000000000002e-00000000… Counting /hashstore/2f/lo…

When recreating the Hashtable, you have to scan for 0 byte sized logs, and delete them, the start the script. If it fails at a certain point, take a look, at which file this happened, you can back it up and delete it from the corresponding folder, then start the script again. Hashtable seems to perf…

It may not rebuilt all hashtable, so it would start to fail audits for not scanned logs due to “file not found”. I would recommend to finish the rebuild.

So, is safe to delete the files like this? /hashstore/28/log-0000000000000028-00000000

If its size is 0, then yes (back it up, just in case).

now seems that in s1 folder works fine s1# docker run -it --rm -v ${PWD}:/hashstore -v ${PWD}/meta:/meta storj-write-hashtbl write-hashtbl /hashstore Counting /hashstore/0f/log-000000000000000f-00000000... Counting /hashstore/12/log-0000000000000012-00000000... Counting /hashstore/19/log-0000000000…

Even if it’s not 0 bytes, you can delete it (you can still back it up), since it’s corrupted and wont benefit you in any case. This small data loss wont be an issue for the audit score. I deleted one or two non 0 byte files, and my audit score did not drop.

Delete the file in the corresponding folder Counting /hashstore/3a/log-000000000000003a-00004fbd... Even if its not 0 bytes, it seem to be corrupted.

[image] Container launch error troubleshooting Not safe, but I do not know, how to fix it. Unlike piecestore, each log file contains dozens pieces, 1GB in total. So it may quickly become DQ, if there are many of such files. More than 4% will definitely end in D…

Node fails to start, error hashtbl-000000000000000b

Node Operators troubleshooting

Alexey November 28, 2025, 2:35am 11