Storagenode Specs Sheet for easy referencing

The big majority of posts, especialy in SNO section, have a lot of questions and answers about the specs of the storagenodes that have errors, crash, have problems etc. And a vast majority of SNOs don’t know what to tell about their setups, or use multiple replyes to create a complete image, making harder for others to answer promptly and give rapid and good solutions. This creates unnecesary clutter.
The solution is simple: implement a Storagenode ID Card, with a predifined format, with all the specs nedeed, to be easily reffered like you would tag a member with @.
The ID Card or Specifications Card or whatever you want to call it, should:

  • be accesible and editable in each member’s Account page;
  • be unique per node, with an user defined named, like @snorkel’s_Node_11 or something, that can be refferenced by the owner or others in a conversation;
  • contain all the info that are needed for debuging and statistics, with no personal data that can be linked to the real node.
  • have predefined fields, in a predefined order, to keep everyone on the same page, and to make it easy for every SNO to enter the required data.
  • pop-up or be automaticaly added in the conversation when someone references it, in a predifined format, with all the detailed specs.

Also, there should be an ID card for every member, that acts like the forementioned node card, that should contain a predefined description of the technical level of the owner - like “IT specialist, only Windows knowledge, can easily follow guides” or “newbie, PC operator, no linux knowlege, basic windows knowledge, needs step-by-step detailed guidence” etc.

With all this info available, would also be very easy to make statistics, available for public or just for Storj. There can be also private info like energy costs, expected ROI, etc. that would help Storj decides easily what effects their decisions will have, without conducting surveys.
I hope you like this ideea and any input is welcomed. If you want it to be implemented, you should vote for it by giving “like”.

Storagenode ID card example:
Machine type: NAS/ PC/ SoC
Maker: Synology/ QNAP/ CUSTOM/ RaspPi etc
Model: DS720+/ etc
CPU: xxx
OS: Windows/ Linux Ubuntu/ Proprietary OS Linux based/ etc
Storagenode runs in: Docker/ VM/ as Service
No. of nodes in the same machine: xx
No. of nodes in the same VM: xx
Internet connection type: wired/ wireless
Internet connection speed: xx UP + xx Down Mbps
WAN IP type: static IP/ DDNS
HDD maker: Seagate
HDD model: Exos X18
HDD capacity: 18TB
HDD rpm: 7200
HDD writecache: No/ Yes - xx MB
HDD space alocated for node: xxTB
HDD used for something else: Yes/No
No of nodes on HDD: xx
HDD connection: local SATA/ local USB 3/ network
RAID setup: No/ xx
HDD filesystem: xxx
Filesystem optimisations: …
SSD cache: Yes/No
SSD cache used for: DB, logs, etc.


Quite comprehensive list, I like it! I’d add:

  • What other services are run on the same hardware?
  • What optional storage node parameters are used? E.g. piece-scan-on-startup, max-concurrent-requests
  • ISP plan used: consumer-grade, business-grade, data center
  • Hardware age

As a suggestion, but not a requirement, some folks like having lots of nodes.

Yes, there should be the option to create multiple cards per user account, one for each node, and the user can choose how to name eachone. I mean “node” as 1 storagenode instance runing on a machine that can have many instances.