Correct storj configuration

Hi everybody!

I found an old htpc that no one needed in my garage.
I got the idea to make a server for storj node(s) out of it.
It’s configuration:
MB Asrock 960GC-GS FX (6x sata/mATX/VGA)
CPU AMD Athlon X2 240
RAM DDR3 2x2Gb
PSU 450W

Also I have 2 old 3.5 HDDs: Toshiba 1Tb and Samsung 750Gb
New unused Seagate 12Tb
And old SSD 60Gb

In result, I have Ubuntu Server 20.04 installed at SSD and 3 Hdds (ext4) mounted to /mnt as
/mnt/to1t (Toshiba 1Tb)
/mnt/se12t (Seagate 12Tb)
/mnt/sa750g (samsung 750Gb)

Server connected via wired ethernet (RJ45) to router.
I have 100mbs connection that is almost free of traffic.

Now I want to config storj nodes and I don’t know wich config to use.

  1. Is 1 node per 1 hdd the good idea?
  2. Do I need different authorizes per each node
  3. What tactics would you advise me to follow? E.g.
  • start with smallest hdd and wait for complete filling of it and start another
  • start all 3 nodes at one time
  • throw out small hdds and use only one node with 12Tb
  • other way

I am not chasing profit.
But if the server will cover my expenses for the Internet and the electricity that the server uses, then that will be great! And of course I am aimed at long-term use of this server with replacing dead HDDs with new ones.

It will not do that at first but maybe later, maybe

I understand this and this is not an end in itself, but in terms of a year or two, it would be cool

I would start 1 node with this NEW hdd and wait for it to fill up then start other nodes.

1 Like

Thank you much! This is really one of the options for starting.

1 Like

Hello @zeiz and welcome to the forum :slight_smile:

Your configuration is okay performance wise for Storj I think.

Be sure they are statically mounted via fstab.

Wired network is the best option.
I believe 100Mbps is currently fast enough for Storj.

The best approach is usually to have one node per HDD as suggested by @nerdatwork.
You’ll need one authorization token (aka EDIT: to then create and sign an identity) per node.
So to start things off, one identity would be enough to spin up your first node.
I would choose the disk that consumes the less energy to begin with, to be as energy efficient as possible.
When this first node is nearly full (say 90%), you’ll be ready to start a new one, with a new identity and new HDD.

It highly depends on how much power the whole machine draws, and electricity prices in your country.
New nodes take many months before making a bit of revenue.
Have a look there, copy this spreadsheet to your own Google account and fill in your numbers to have a rough idea of what you could expect:


two separate entities - you need AND new identity AND new authorization token, they are not replaceable for each other.

1 Like

Many thanks to everyone!

Summarizing all the answers:

  • Small HHD makes no sense
  • Best way is start with one big node with fresh 12Tb HDD
  • Keep track of all income and expenses
  • Wait 90% of HDD full and make decisions on adding new HDDs (nodes) if it is not at a loss

It’s right?

1 Like

Thanks for your vigilance @Alexey.

1 Like