I successfully ran the installer and have one drive running. If I install additional drives, how do I add them into the software? Do I run the installer again? But even if I do, the installer only lets you select one drive.
Currently you cannot add multiple drives to a single node without RAID. Ideally you should keep 1 node per HDD. Also you shouldn’t invest in hardware just for Storj. Storj is for lending extra space on your HDD for some extra cash.
I think multiple hdd to One node was on the ideas page and this was One of the ideas that would not happen
Official response https://ideas.storj.io/ideas/V3-I-2
Brandon Iglesias commented 09 Sep 17:54
Hey everyone Brandon the Product Manager @storj here. Thanks for submitting this idea, Chris VdG has a point about the redundancy between raid and erasure coding. Our recommendation is to run one node per HD. This will actually spread your overall risk of a HD failing and losing the withholdings for that specific node ID. If you have 4 2 TB HDs then the best thing to do is run 1 node per HD and if one of those fails then at most you would only lose 25 percent of your overall withholdings amongst all 4 nodes. Instead of using raid to backup one of your nodes its may be in your best interest to just allocate that extra raid space to the network and profit off of it instead.
I assume you are referring to the windows installer. To my knowledge it is not possible to run more than one node using the windows installer. It is possible with docker though. So if you want to have multiple nodes for multiple disks, you might want to switch to a docker setup.
I just set up a store node with an old quadcore + 6 1tb HD in ZFS with a big pool of a bit more of 4,2TB and I’m sharing 4TB this was old hardware getting dust, so it’s just about the power is consuming.
I rather prefer a ZFS with raidz1, and in case of a disk failing, i can just replace it in no time and the RAID would resilver and everything will be fine again in a couple of hours other that having 6 machines running
This makes sense except for the traffic/bandwidth setting. You pretty much have to divide the available monthly traffic by the number of nodes. This risks one node reaching its limit while there is still plenty of free traffic available by other nodes that aren’t using it.
It would be great if there were some official solution to this problem.
This is why Storj recommends starting another node behind same IP IF your first node is full. Starting more than 1 node that are not full behind same IP does not make any sense.
The first node could still use egress traffic, so this doesn’t solve the problem.