Container launch error

surprise00 · November 14, 2025, 8:10pm

Can someone explain whats going on here? and how to fix it?

2025-11-14T20:08:20Z INFO hashstore hashstore opened successfully {“Process”: “storagenode”, “satellite”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “open_time”: “531.134384ms”}
2025-11-14T20:08:20Z INFO Current binary version {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”, “Version”: “v1.141.2”}
2025-11-14T20:08:20Z INFO Version is up to date {“Process”: “storagenode-updater”, “Service”: “storagenode-updater”}
2025-11-14T20:08:21Z ERROR failure during run {“Process”: “storagenode”, “error”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”, “errorVerbose”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”}
Error: Failed to create storage node peer: hashstore: missing hashtbl when log files exist
storj.io/storj/storagenode/hashstore.NewStore:238
storj.io/storj/storagenode/hashstore.New:100
storj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252
storj.io/storj/storagenode/piecestore.NewHashStoreBackend:117
storj.io/storj/storagenode.New:604
main.cmdRun:84
main.newRunCmd.func1:33
storj.io/common/process.InitBeforeExecute.func1.2:389
storj.io/common/process.InitBeforeExecute.func1:407
github.com/spf13/cobra.(*Command).execute:985
github.com/spf13/cobra.(*Command).ExecuteC:1117
github.com/spf13/cobra.(*Command).Execute:1041
storj.io/common/process.ExecWithCustomOptions:115
main.main:34
runtime.main:283
2025-11-14 20:08:21,097 WARN exited: storagenode (exit status 1; not expected)
2025-11-14 20:08:22,123 INFO spawned: ‘storagenode’ with pid 108
2025-11-14 20:08:22,129 WARN received SIGQUIT indicating exit request
2025-11-14 20:08:22,131 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2025-11-14T20:08:22Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2025-11-14 20:08:22,146 INFO stopped: storagenode-updater (exit status 0)
2025-11-14T20:08:22Z INFO Configuration loaded {“Process”: “storagenode”, “Location”: “/app/config/config.yaml”}
2025-11-14T20:08:22Z INFO Anonymized tracing enabled {“Process”: “storagenode”}
2025-11-14T20:08:22Z INFO Operator email {“Process”: “storagenode”, “Address”: “surprise00@msn.com”}
2025-11-14T20:08:22Z INFO Operator wallet {“Process”: “storagenode”, “Address”: “0xE510b4c76F01F71F4FeBDBEF01BB7979E69Cf6C3”}
2025-11-14T20:08:22Z INFO server kernel support for server-side tcp fast open remains disabled. {“Process”: “storagenode”}
2025-11-14T20:08:22Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {“Process”: “storagenode”}
2025-11-14T20:08:22Z INFO hashstore hashstore opened successfully {“Process”: “storagenode”, “satellite”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”, “open_time”: “150.589538ms”}
2025-11-14T20:08:22Z ERROR failure during run {“Process”: “storagenode”, “error”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”, “errorVerbose”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”}
Error: Failed to create storage node peer: hashstore: missing hashtbl when log files exist
storj.io/storj/storagenode/hashstore.NewStore:238
storj.io/storj/storagenode/hashstore.New:100
storj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252
storj.io/storj/storagenode/piecestore.NewHashStoreBackend:117
storj.io/storj/storagenode.New:604
main.cmdRun:84
main.newRunCmd.func1:33
storj.io/common/process.InitBeforeExecute.func1.2:389
storj.io/common/process.InitBeforeExecute.func1:407
github.com/spf13/cobra.(*Command).execute:985
github.com/spf13/cobra.(*Command).ExecuteC:1117
github.com/spf13/cobra.(*Command).Execute:1041
storj.io/common/process.ExecWithCustomOptions:115
main.main:34
runtime.main:283
2025-11-14 20:08:22,987 WARN stopped: storagenode (exit status 1)
2025-11-14 20:08:22,993 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)

surprise00 · November 14, 2025, 8:15pm

btw this happened after few power outages(

alpharabbit · November 14, 2025, 8:20pm

Seems like hashtable is broken or missing. Use write-hashtbl to build a new one.

surprise00 · November 15, 2025, 3:06am

Yes, i have tried instruction from Alexei,
but faced several errors:
1.

docker build . -t storj-write-hashtbl
[+] Building 7.7s (10/10) FINISHED docker:default
=> [internal] load build definition from dockerfile 0.6s
=> => transferring dockerfile: 243B 0.0s
=> [internal] load metadata for Docker Hub Container Image Library | App Containerization 6.2s
=> [internal] load metadata for Docker Hub Container Image Library | App Containerization 6.2s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [build 1/2] FROM Docker Hub Container Image Library | App Containerization 0.0s
=> [stage-1 1/3] FROM Docker Hub Container Image Library | App Containerization 0.0s
=> CACHED [stage-1 2/3] WORKDIR /meta 0.0s
=> CACHED [build 2/2] RUN git clone GitHub - storj/storj: Ongoing Storj v3 development. Decentralized cloud object storage that is affordable, easy to use, private, and secure. && cd storj && go install ./cm 0.0s
=> CACHED [stage-1 3/3] COPY --from=build go/bin/write-hashtbl /usr/bin/ 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:fd6a1d52bd6ec35273d7b7d0f5ebe3d53843529183331635adee1eb58472054a 0.0s
=> => naming to Docker Hub Container Image Library | App Containerization 0.0s

1 warning found (use docker --debug to expand):

FromAsCasing: ‘as’ and ‘FROM’ keywords’ casing do not match (line 1)

s0 passed ok, but s1 returns next:

odroidxu4:s1:# docker run -it --rm -v ${PWD}:/hashstore -v ${PWD}/meta:/meta storj-write-hashtbl write-hashtbl /hashstore
Counting /hashstore/01/log-0000000000000001-00000000…
Counting /hashstore/03/log-0000000000000003-00000000…
Counting /hashstore/04/log-0000000000000004-00000000…
Counting /hashstore/05/log-0000000000000005-00000000…
Counting /hashstore/07/log-0000000000000007-00000000…
Counting /hashstore/08/log-0000000000000008-00000000…
Counting /hashstore/0a/log-000000000000000a-00000000…
Counting /hashstore/0b/log-000000000000000b-00005005…
Counting /hashstore/0c/log-000000000000000c-00000000…
Counting /hashstore/0d/log-000000000000000d-00000000…
Counting /hashstore/0e/log-000000000000000e-00000000…
Counting /hashstore/10/log-0000000000000010-00000000…
Counting /hashstore/12/log-0000000000000012-00000000…
Counting /hashstore/13/log-0000000000000013-00005008…
Counting /hashstore/14/log-0000000000000014-00000000…
Counting /hashstore/16/log-0000000000000016-00000000…
Counting /hashstore/17/log-0000000000000017-00000000…
Counting /hashstore/18/log-0000000000000018-00000000…
Counting /hashstore/19/log-0000000000000019-00000000…
Counting /hashstore/1a/log-000000000000001a-00005009…
Counting /hashstore/1c/log-000000000000001c-00000000…
Counting /hashstore/1d/log-000000000000001d-00000000…
Counting /hashstore/1f/log-000000000000001f-00000000…
Counting /hashstore/20/log-0000000000000020-00000000…
Counting /hashstore/21/log-0000000000000021-00000000…
Counting /hashstore/22/log-0000000000000022-0000500a…
Counting /hashstore/23/log-0000000000000023-00000000…
Counting /hashstore/24/log-0000000000000024-00000000…
Counting /hashstore/25/log-0000000000000025-00000000…
Counting /hashstore/26/log-0000000000000026-00000000…
Counting /hashstore/27/log-0000000000000027-00000000…
Counting /hashstore/28/log-0000000000000028-00000000…
Counting /hashstore/29/log-0000000000000029-0000500b…
platform: invalid argument
storj.io/storj/storagenode/hashstore/platform.mmap:30
storj.io/storj/storagenode/hashstore/platform.Mmap:16
main.openFile:37
main.(*cmdRoot).iterateRecords:148
main.(*cmdRoot).countRecords:212
main.(*cmdRoot).Execute:79
github.com/zeebo/clingy.(*Environment).dispatchDesc:129
github.com/zeebo/clingy.Environment.Run:41
main.main:29
runtime.main:285
odroidxu4:s1:#

Alexey · November 15, 2025, 3:58am

Hello @surprise00,
Welcome back!

Found this way: Search results for 'platform: invalid argument order:latest' - Storj Community Forum (official)

surprise00 · November 15, 2025, 11:53am

Wow it worked.
Should i do same in all folders that located inside “hashstore”?

Alexey · November 15, 2025, 12:00pm

No, you should only do this when you have a problem like this.
Do not hesitate to use a search function on the forum - you likely will get your answer. If not, please ask, we would find a way how to help you. This is why this forum so useful - because of the Community

surprise00 · November 15, 2025, 8:29pm

sadly but it doesnt helped t launch node back online, still:

025-11-15T20:25:31Z ERROR failure during run {“Process”: “storagenode”, “error”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”, “errorVerbose”: “Failed to create storage node peer: hashstore: missing hashtbl when log files exist\n\tstorj.io/storj/storagenode/hashstore.NewStore:238\n\tstorj.io/storj/storagenode/hashstore.New:100\n\tstorj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:117\n\tstorj.io/storj/storagenode.New:604\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:283”}
Error: Failed to create storage node peer: hashstore: missing hashtbl when log files exist
storj.io/storj/storagenode/hashstore.NewStore:238
storj.io/storj/storagenode/hashstore.New:100
storj.io/storj/storagenode/piecestore.(*HashStoreBackend).getDB:252
storj.io/storj/storagenode/piecestore.NewHashStoreBackend:117
storj.io/storj/storagenode.New:604
main.cmdRun:84
main.newRunCmd.func1:33
storj.io/common/process.InitBeforeExecute.func1.2:389
storj.io/common/process.InitBeforeExecute.func1:407
github.com/spf13/cobra.(*Command).execute:985
github.com/spf13/cobra.(*Command).ExecuteC:1117
github.com/spf13/cobra.(*Command).Execute:1041
storj.io/common/process.ExecWithCustomOptions:115
main.main:34
runtime.main:283
2025-11-15 20:25:31,773 WARN exited: storagenode (exit status 1; not expected)
2025-11-15 20:25:32,777 INFO gave up: storagenode entered FATAL state, too many start retries too quickly
2025-11-15 20:25:34,786 WARN received SIGQUIT indicating exit request
2025-11-15 20:25:34,789 INFO waiting for processes-exit-eventlistener, storagenode-updater to die
2025-11-15T20:25:34Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2025-11-15 20:25:34,810 INFO stopped: storagenode-updater (exit status 0)
2025-11-15 20:25:35,821 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)

should i also run this tool in all this folders?

i did it only inside:
12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs
as it was in instruction.

alpharabbit · November 15, 2025, 9:32pm

You also need to delete the old hashtable in meta folder and copy or move the new one to that position if it was not created in meta folder. Did you?

surprise00 · November 15, 2025, 11:49pm

Yeah ofc, like it was in instruction, old meta was moved to meta.bak, than created new meta folder.
But the thing im interesting in right now:

i did everything in instruction inside this directory (highlited with gray), i didnt touched anything else, should i?

alpharabbit · November 16, 2025, 12:22am

Not sure about that docker instructions…
New file hashtbl must be in subfolder meta. Is it there?

surprise00 · November 16, 2025, 1:09am

Yep, they are there

alpharabbit · November 16, 2025, 1:51am

Folder 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6 was opened successfully. So I would now recreate tables for remaining 2 satellites.

Alexey · November 16, 2025, 3:05am

It was an example. If you have corrupted hashtables for other satellites, you need to do the same for them too, except

surprise00 · November 16, 2025, 7:09pm

should i do something with meta folder inside hashstore?

Alexey · November 20, 2025, 6:31am

Which one? To make a backup? Yes, it can help to restore to a previous state, if something goes wrong. But usually you can just remove files from it and move the generated ones to there or replace. Of course it’s only for the meta folders with hashtables.

surprise00 · November 26, 2025, 1:58pm

this one even better

root@storj-vm:/mnt/storj2/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s0# rm -rf meta
root@storj-vm:/mnt/storj2/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s0# docker run -it --rm -v ${PWD}:/hashstore -v ${PWD}/meta:/meta storj-write-hashtbl write-hashtbl /hashstore
Counting /hashstore/06/log-0000000000000006-00000000...
Counting /hashstore/10/log-0000000000000010-00000000...
Counting /hashstore/13/log-0000000000000013-00000000...
Counting /hashstore/14/log-0000000000000014-00000000...
Counting /hashstore/15/log-0000000000000015-00000000...
Counting /hashstore/1b/log-000000000000001b-00000000...
Counting /hashstore/1c/log-000000000000001c-00000000...
Counting /hashstore/20/log-0000000000000020-00000000...
Counting /hashstore/24/log-0000000000000024-00000000...
Counting /hashstore/26/log-0000000000000026-00000000...
Counting /hashstore/27/log-0000000000000027-00000000...
Counting /hashstore/28/log-0000000000000028-00000000...
Counting /hashstore/31/log-0000000000000031-00000000...
Counting /hashstore/32/log-0000000000000032-00004fc1...
Counting /hashstore/33/log-0000000000000033-00000000...
Counting /hashstore/35/log-0000000000000035-00000000...
Counting /hashstore/36/log-0000000000000036-00000000...
Counting /hashstore/37/log-0000000000000037-00000000...
Counting /hashstore/38/log-0000000000000038-00004fbf...
Counting /hashstore/39/log-0000000000000039-00004fc6...
Counting /hashstore/3a/log-000000000000003a-00000000...
Counting /hashstore/3b/log-000000000000003b-00000000...
Counting /hashstore/3c/log-000000000000003c-00000000...
Counting /hashstore/3d/log-000000000000003d-00000000...
Counting /hashstore/3e/log-000000000000003e-00000000...
Counting /hashstore/3f/log-000000000000003f-00000000...
Counting /hashstore/40/log-0000000000000040-00000000...
Counting /hashstore/41/log-0000000000000041-00000000...
Counting /hashstore/42/log-0000000000000042-00000000...
Counting /hashstore/43/log-0000000000000043-00004fc2...
Record count=127898
Using logSlots=18
Processing /hashstore/06/log-0000000000000006-00000000...
Processing /hashstore/10/log-0000000000000010-00000000...
Processing /hashstore/13/log-0000000000000013-00000000...
Processing /hashstore/14/log-0000000000000014-00000000...
Processing /hashstore/15/log-0000000000000015-00000000...
Processing /hashstore/1b/log-000000000000001b-00000000...
Processing /hashstore/1c/log-000000000000001c-00000000...
Processing /hashstore/20/log-0000000000000020-00000000...
Processing /hashstore/24/log-0000000000000024-00000000...
Processing /hashstore/26/log-0000000000000026-00000000...
Processing /hashstore/27/log-0000000000000027-00000000...
Processing /hashstore/28/log-0000000000000028-00000000...
Processing /hashstore/31/log-0000000000000031-00000000...
Processing /hashstore/32/log-0000000000000032-00004fc1...
Processing /hashstore/33/log-0000000000000033-00000000...
Processing /hashstore/35/log-0000000000000035-00000000...
Processing /hashstore/36/log-0000000000000036-00000000...
Processing /hashstore/37/log-0000000000000037-00000000...
Processing /hashstore/38/log-0000000000000038-00004fbf...
Processing /hashstore/39/log-0000000000000039-00004fc6...
record at offset=290528512 in /hashstore/39/log-0000000000000039-00004fc6 has invalid piece header with err=unexpected EOF
record at offset=290499904 in /hashstore/39/log-0000000000000039-00004fc6 has invalid id=13
Processing /hashstore/3a/log-000000000000003a-00000000...
Processing /hashstore/3b/log-000000000000003b-00000000...
panic: runtime error: slice bounds out of range [:36732] with capacity 512

goroutine 1 [running]:
main.(*cmdRoot).iterateRecords(0xc0000963c0, {0x73e4c0, 0xc0000fc030}, {0xc0000703f0, 0x2b}, 0x0, 0xc000105b58)
        /go/storj/cmd/write-hashtbl/main.go:188 +0xc45
main.(*cmdRoot).Execute(0xc0000963c0, {0x73e4c0, 0xc0000fc030})
        /go/storj/cmd/write-hashtbl/main.go:109 +0x965
github.com/zeebo/clingy.(*Environment).dispatchDesc(0xc000048de0, {0x73e450, 0x945540}, 0xc000098240, {{0x0, 0x0}, {0x0, 0x0}, {0x0, 0x0}, ...})
        /go/pkg/mod/github.com/zeebo/clingy@v0.0.0-20230602044025-906be850f10d/run.go:129 +0x6dd
github.com/zeebo/clingy.Environment.Run({{0x73d120, 0xc0000963c0}, {0x6d8ec6, 0xd}, {0xc000090030, 0x1, 0x1}, 0x0, 0x0, 0x6ef0e0, ...}, ...)
        /go/pkg/mod/github.com/zeebo/clingy@v0.0.0-20230602044025-906be850f10d/run.go:41 +0x198
main.main()
        /go/storj/cmd/write-hashtbl/main.go:29 +0x148
root@storj-vm:/mnt/storj2/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s0#

surprise00 · November 26, 2025, 3:05pm

btw disk was checked with fsck, and there no errors

alpharabbit · November 26, 2025, 3:27pm

Was S.M.A.R.T. also checked?

surprise00 · November 26, 2025, 3:47pm

it is external hdd on remote location(