During rebuild of metadata, write-hashtbl found this error. lot of this eerors in log file
how critical it is, is this mean that file is broken, is it possible to fix it somehow?
may be we need to think about tools that can fix rebuild the file and save some data from it?
record at offset=1008449856 in E:\hashstore\12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S\s0\62\log-0000000000000862-00000000 has invalid piece hash=c6dad9068db1ff86d8e7b0648d37d05e89e49c00d7957840670e7df567ab914f
There is no way to fix a corrupted part of the log file, but other addressable pieces will be still available.
Seems NTFS is not so robust or maybe this disk has issues?
I had problems with HBA, this is 2 output HBA. so boath nodes on reconstruction now.
so almost all metadata files are gone after restart.
It also will be very good if result hashtbl file will be configurable, so i can run several at once. today it is fixed path in code C:\Users\Miner 4, it is user main folder. so i cant run several at once. or it just appear near the exe file
After I rebuild all, i plan to change all small HBAs there to p840 with 16 channels. it is more robbust solution.
Actually you can. You need to switch to a directory where you want to store a new hashtbl file and run the command.
do you mean just CD command in cmd?
I tried before, but win 11 dot give me to change it to other hdd, but now i cound it work like that
cd /d I:\
only then it will allow you
thank you for info I will try.
1 Like
Yes, or open it in the Explorer and select “Open in Terminal” from the context menu.
looks like collision problem was not fixed
hashstore: put:{key:b33df7890d9847d950ad7094374e1bac2e8e04cf83a0f287e1bdb1644267fdfe offset:969388476 log:3145 length:16384 created:20337 (2025-09-06) expires:20481 (2026-01-28) trash:true} != exist:{key:b33df7890d9847d950ad7094374e1bac2e8e04cf83a0f287e1bdb1644267fdfe offset:1071965952 log:2858 length:16384 created:20337 (2025-09-06) expires:0 (1970-01-01) trash:false}: hashstore: collision detected
storj.io/storj/storagenode/hashstore.(*HashTbl).insertLocked:411
storj.io/storj/storagenode/hashstore.(*HashTblConstructor).Append:552
main.(*cmdRoot).Execute.func2:111
main.(*cmdRoot).iterateRecords:211
main.(*cmdRoot).Execute:110
github.com/zeebo/clingy.(*Environment).dispatchDesc:129
github.com/zeebo/clingy.Environment.Run:41
main.main:30
runtime.main:285
I had Gemini fix it for me, I can send you my GitHub fork if you want it. I have tested it on one of my nodes, and it 100% works.
I was told, that devs fixed it, but looks like not yet. I wait for fix.
Sounds good. If they don’t get it fixed quick enough, just hit me up any time and I can send you a link to the fork and you can read through all the code changes.
1 Like
Have you re-ran the install command to get the latest changes from the main branch?
yes, i deleted old exe, and rerun it, it downloaded some parts.
You do not need to delete anything, just repeat the same command.
Ok, I would let the team know.
error not exactly the same, line of codes are different
created:20337 (2025-09-06) expires:20481 (2026-01-28) trash:true} != exist:{key:b33df7890d9847d950ad7094374e1bac2e8e04cf83a0f287e1bdb1644267fdfe offset:1071965952 log:2858 length:16384 created:20337 (2025-09-06) expires:0 (1970-01-01) trash:false}: hashstore: collision detected
storj.io/storj/storagenode/hashstore.(*HashTbl).insertLocked:411
storj.io/storj/storagenode/hashstore.(*HashTblConstructor).Append:552
main.(*cmdRoot).Execute.func2:111
main.(*cmdRoot).iterateRecords:211
main.(*cmdRoot).Execute:110
github.com/zeebo/clingy.(*Environment).dispatchDesc:129
github.com/zeebo/clingy.Environment.Run:41
main.main:30
runtime.main:285
Did it fail, or is it continued?
now after you asked, it looks like this error was shown after last piece was processed.
mapp ff in one way it was 7th log on other b login mapp ff. so it possible it made it till the end.
I will try on s1 both nodes also.
After rebild, service is starting, but not dashboard, I see that it makes something there on hdd, I am on version 1.146.8 there. is it checking fsk errors before start, it go like several hoers ?
UPdate about 8h working, but no sing of loaded dashboard, even databases not opend, no logs.
Seems it didn’t find a hint file, so it will check all logs.
one of the nodes gone alive today, looks like it done its chekings.
So I wait then.
1 Like