Hi, I’m using write-hashtbl and run into a new situation: hashstore: put:{key:1b1bbd32f020502e52e839717e13a486ae0b9f6eff7c2f25001bf1df606bc12e offset:1073162112 log:116 length:2319872 created:20450 (2025-12-28) expires:0 (1970-01-01) trash:false} != exist:{key:1b1bbd32f020502e52e839717e13a486ae0b9f…

Seem like I just need to delete log 64 (decimal 100) and log 74 (decimal 116) it will work again.

It should be fixed with these changes: [image] Unrecoverable error Here are proposed changes: https://review.dev.storj.tools/c/storj/storj/+/20196 storagenode/hashstore: skip log file check bool https://review.dev.storj.tools/c/storj/storj/+/20197 storagenode/hashstore: log hint info https://…

if updates will go like now, my nodes will be DQ before this updates see the light.

The team is aware of the problem, as you can see by these changes, so they should be included to the new version. I also think that we back on track, so it should be updated before the node will be disqualified for downtime.

Please note, that – in general – we recommend to use the version which is published by https://version.storj.io/ , because that’s the tested one which passed all QA test, and also tested in select network for a certain time period. Currently it (1.142.7) is an older one, because still we are testing…

Thank you i will try, generally today I use 1.146.5 everywhere, and it working fine.

thank you for update. i have 2 nodes that have error, one node service gone live. but dashboard not loading and log show this error 2026-01-30T12:53:14+02:00 ERROR contact:amnesty failed to get satellite URL for amnesty report {“satellite”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “p…

my result is: (node is not running) hashstore: put:{key:9db4ea9c83d49db0e2fd248a50d91771a6df4febf88f20de2ee3cec1da4ee0dd offset:153484096 log:292 length:2319872 created:20475 (2026-01-22) expires:20496 (2026-02-12) trash:true} != exist:{key:9db4ea9c83d49db0e2fd248a50d91771a6df4febf88f20de2ee3cec1da…

i executed write-hashtbl.exe C:\link\1-3\30\hashstore\12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S\s0 it runs with following result: Record count=2501009 Using logSlots=23 The file exists. main.(*cmdRoot).Execute:97 github.com/zeebo/clingy.(*Environment).dispatchDesc:129 github.com/ze…

Did you put new made file instead of old in this folder meta?

Storj Community Forum (official)

Write-hashtbl hashstore: collision detected

Node Operators troubleshooting