Storage-dir-verification file format error on Docker (NAS environment)

[Bossy]

Hi everyone,

I'm trying to set up a Storj storage node on my TeraMaster F4-424 Pro NAS using Docker, but I keep getting this error:

Error: piecestore monitor: error verifying location and/or readability of storage directory: content of file is not a valid node ID

Environment:
- Device: TeraMaster F4-424 Pro NAS
- OS: TOS (TeraMaster OS)
- Docker: storjlabs/storagenode:latest (v1.137.5)
- Python3: Available (3.10.6)
- Storage: 6TB available

What I've tried:
1. Created storage-dir-verification file using Python base58 library
2. Tried multiple base58 decoding methods
3. File contains binary data (not text), but Storj still rejects it

The error shows the file content as hex, but Storj says it's "not a valid node ID".

Has anyone encountered this issue on a NAS environment? Is there a specific format required for the storage-dir-verification file?

My Node ID: 12Ewpq9CqGyYkD2TPQHURzNKj5SBESBHc8nNgvRMpHATSvbqgsd

Any help would be appreciated!

[Alexey]

Hello @Bossy,
Welcome to the forum!

This file is generated when you use a setup command. This error indicates, that you provided a wrong path to the identity. This node has been using a different identity before.

Please restore this file, if possible and find a correct identity for this data.
You may use this method to check the identity to see does it match the required NodeID (for that you need to know the previous NodeID, not the current one, which doesn’t match):

RaspberryPi crash

./identity certificate-authority id --ca.cert-path /mnt/storagenode2/identity/ca.cert It will print a NodeID. Then you need to search in your logs, what was the NodeID before. Please also SKIP a SETUP step, it must not be executed again for a worked node, otherwise you can destroy it. no, this token is one-time only and can be used only once to sign any identity, after that it has no use. It also doesn’t contain any info related to your node (even to used email address, it’s just used for …

if you have previous logs you can figure out what NodeID was before.

If it’s a new node, then simple generate a new identity and run the setup command, but you need to delete config.yaml to allow the command to finish.
If this node is worked before, but its identity is lost, you can delete it, its data and start from scratch. It will not work with a foreign identity anyway.

[Bossy]

Hi Alexey,

Thank you so much for your guidance regarding the identity setup issue.
Thanks to your advice, I was able to identify the mismatch and skip the unnecessary setup step.
My node is now successfully online and functioning as expected.

I truly appreciate your support and the time you take to help others in the community.
Thanks again!

Best regards,
Bossy

[Alexey]

I would recommend moving/copying the correct identity to the data drive and using that path instead of the location on the system drive, as they are useless without each other anyway. It is also recommended to create a backup copy of the identity, as even if just one file in the identity is corrupted, the node will not be able to use it.