it looks like the last hashtbl file is invalid (it consists of all 0s). side question: what filesystem are you using?
there does exist a write-hashtbl command that can be used to reconstruct the table from the log files. it’s at storj/cmd/write-hashtbl at main · storj/storj · GitHub. here’s some steps to follow to use it:
- have the Go toolchain installed (https://go.dev)
- run
go install storj.io/storj/cmd/write-hashtbl@latestto install it (it will probably end up in$HOME/go/bin) - run it like
write-hashtbl /path/to/hashstore/satellite_id/sX. it will make a file namedhashtblin the current working directory - move it into the appropriate
metadirectory. (mv hashtbl /path/to/hashstore/satellite_id/sX/meta/hashtbl)
to identify which directory, it should be the last file printed by find /mnt/poolx/subvol-536-disk-0/storage/hashstore/ -type f -name 'hashtbl-*'. you can double check that it’s the right one by running xxd /path/to/hashstore/satellite_id/sX/meta/hashtbl-whatever | head -n 2 and it should be all zeros.
be careful when doing any destructive actions (like moving a file over top of a different one). it would be wise to move files out of the way (like, mv foo foo.bak to rename it out of the way) instead.
a more user friendly change is coming in the form of https://review.dev.storj.tools/c/storj/storj/+/19363 but it’s not yet reviewed/merged/released.
good luck and let me know if you have any questions.