Do not put several nodes to use the same pool, especially on Unraid and especially with unraid community app.
The Unraid community app for Storj uses an old outdated command, which guarantee the disqualification of your node after reboot:
- the Unraid has a flaw in the design: it starts user’s disks after the full boot, but docker service started before the disks are available;
- the Unriad community app have several issues:
- it uses
-v option instead of
--mount type=bind, thus the docker will create an empty volume, if drive is not available (exactly the case for Unraid design);
- the storagenode will start from scratch in such case and will be disqualified pretty quick because of missed customers’ data;
- it uses
:alpha tag instead of
So, the workaround is to run the storagenode without Unraid community app and use this guide: https://documentation.storj.io/setup/cli/storage-node instead, or contact the author and ask to fix issues with their app.
Why using the same pool for several nodes is not a good idea? Because they will concurrent for the same resource and will interfere each other, slow down everyone.
As described earlier, multiple nodes behind the same /24 subnet of public IPs will share the bandwidth, i.e. from the /24 subnet only one node will be selected for each segment. For the SNO this is mean, that traffic will be distributed between such nodes, in summary they would have the same or less traffic as only the one node.
Each new node must be vetted. It can receive only 5% of potential traffic from the customers of the satellite until got vetted. To be vetted on said satellite it should pass 100 audits for it. For the one node it should take at least a month.
In case of multiple nodes behind the same /24 subnet of public IPs the vetting process would be in the same amount times longer as a number of such nodes.
So, it’s much better to start the next node only when the previous one almost full or at least vetted. In this case the vetting process will not take forever.
And of course, they should use a separate disks/pools for the data.