Hello!
It’s time to expand the storage. I would like to connect an additional HDD. What is the proper shutdown procedure? We can expect about 5-8 minutes of downtime. I am expanding a RAID configuration without data loss, so it’s important that the service does not run during the process. Is it sufficient to stop the services for a proper shutdown? Which part of the month would be ideal to minimize the impact on online availability (percentage-wise, so there’s no exclusion)? Thank you!
The network won’t even notice you’re gone for 5-8 minutes: just a normal shutdown is fine.
yeah just shut down the docker or stop the windows service, do your hard drive work, and then start it back up again.
Note there is a maximum practical size of a node of 24TB. Going larger than that may lead to trash not being deleted.
What are the requirements for a Storage Node on V3? – Storj
it’s often better to start a new node for each new disk (assuming the disk is basically dedicated to storj)
The real question is – why do you want to shut down anything to connect an HDD?
Pretty much every single raid on earth supports online expansion and management.
I would not shutdown anything. Connect new disk, grow the array, let everything else continue working.
I’m not necessarily committed to expanding the RAID. I’ll look into starting a new node on the same computer. Am I correct in understanding that if I start a new node, and the email and payout address are the same, the system will aggregate the payouts, or will each node operate independently? I’m asking because of the payout limit.
I thought about shutting it down because if there is data traffic at the moment of expansion, it could be lost. And I don’t want any errors to occur in the system.
Why would data be lost?
Are you using software raid or a hardware controller?
This is a supported usecase. The whole point of RAID is to increase system uptime. It would be absolutely pointless if it was required to shutdown the system to replace/add drives/expand/etc.
The only exception is if you are plugging in a PCIE disk – PCIE hot plug support is very spotty to say the least.
Unfortunately, I’m using Windows 10 with my own software RAID. I tested it before use and confirmed that expansion works without issues during operation. I’m just concerned that there might be errors due to data traffic during the process. But if that’s unfounded, thank you for the information!
Yes it will aggregate payouts per wallet address. Please make sure that you would generate a new identity (only token would not be enough, you need to generate a new one identity, not cloning) for the next node and sign it with a new authorization token.
Thank you very much! On Windows, do I need to run the installer by providing the new data, and it will create the new node? Or is it only possible via the command line? If the installer is launched, will it interfere with the node that is currently running?
On Windows the standard Windows installer is able to install only one node.
The second and next nodes you may run using a Docker Desktop: CLI Install - Storj Docs or using the Community tool Win GUI Storj Node Toolbox.
See details there:
"I have one more question regarding the new node. If I start the new one, does it calculate its age from the moment of starting, meaning that the 1-3 months begin from there? I’m asking because of the held. Or does it take the time of the first node as a reference?
It’s from the first time each satellite hears from your node: which should be within the first minute of node startup.