How to set-up your own 3Node

You can set up different nodes under one farm. The same bootstrap image is fine for that, so you can indeed full copy your USB.

1 Like

Thank you. Makes things easier. :slight_smile:

Hi again. Now i use gofarmer. Just out of curiousity, is there a way to customize pricing settings in gofarmer and how to do it?

This is currently only a feature available in 3Bot. Grid 3.0 introduces big changes to the billing system, so we’re prioritizing rolling that out over integrating Grid 2 features into 3Bot.

Hi @scott, all,

I’ve been trying to diagnose an issue but can’t, so I am here…

I’ve followed this guide up to the final step but, once the image is downloaded I get the following screen without any progress, it just freezes there. Has this happened to anyone else? Thanks for any help,

IMG_20211215_164827

I’ve never seen this one before :slight_smile: My recommendation is posting your screenshot in the Zos Telegram group so one of the developers can have a look.

1 Like

Can anyone please help?
This has been going on on my screen for over an hour now. Does Zero OS take this long or have I done something wrong? The count on the left is increasing.
The number on the left reached 960 and now it seems to be stuck there.
20220120_100523

Hey there, and welcome to the ThreeFold forum :wave:

Zero OS usually boots within ten minutes or so, and it definitely shouldn’t take an hour.

Seems the network device is cycling from up to down. Can’t say why though. Are you attempting to boot Grid 2 or Grid 3?

Hey Scot,
I figured it out. For some reason my ethernet cable had issues. I am glad I tested that. It is now working. Thank you for you comment.
Excuse my ignorance, but what do you mean by Grid2 and Grid3?
Also if I want to build another DIY Node, do I need to use another email?

Ah, good to know. Generally issue with network connectivity show up earlier in the boot cycle, so this was instructive for me, thanks.

We have recently releases a major update to the Grid, thus v2 and v3. Reviewing this post, it’s still referencing Grid 2, so that’s probably where you’re at. I’ll add a note to this post on that. Migration to Grid 3 is still optional, but we’re encouraging DIY farmers to go ahead. Details here.

For your next node, you can actually reuse the boot file or generate a new one based on your same farm id. No need to start over or use any different info.

I will check the new version. I think the community would appreciate a step by step guide on migrating to V3 just like the guide above.
Just to confirm I can have the same 3bot name, the same email and the same farm ID for different nodes? Also if I reuse the same boot file, will it automatically create a new Node ID for the new system?

Yes, you can have as many nodes as you want on the same farm, using all the same info. Each node creates its own node id when it boots up and stores it to disk. The farm id is on the USB drive and the node id never gets stored there.

1 Like

One last question. Can I have multiple nodes at the same location?

Yep, multiple nodes is fine. In that case, you’ll want to consider having sufficient bandwidth for the amount of capacity you’re providing. Check this thread, which I’ll update with some thoughts shortly.

1 Like

Hi, just booted a little Xeon server on v3 Testnet, following the instructions (https://library.threefold.me/info/manual/#/manual__tfchain_portal_ui_farming).
I cleared all HDDs and added a blank SSD.
Got the message: “node is not registered” (farmer 143: wrong farm id) and “no ssd disks detected”, see screenshot
20220122_215404
What went wrong here, please???

20220122_214140
Boot USB started up fine and completed in a few minutes

Following this. I am having the same problem with my new node that I just set up.

1 Like

update: after another clean run of the disks, I got my ssd recognized after boot.
But still getting “node is not registered” (farmer 143: wrong farm id) message.
20220123_144047

Alt-f2 log shows the issue with the farm registration:
20220123_144616
how long does it take to get registered here? Anything I can do??

Update 2:
I just created a new farm under my v3 Twin and loaded a boot image for Mainnet/Production.
This loaded within minutes correctly:
20220123_161743

so it seems there is an issue with the Testnet Bootstrap image to register you correctly on testnet…

Update 3 and ISSUE CLOSED:
I registered my TWIN on Mainnet - portal.grid.tf
So you can only register a Farm and nodes on Mainnet with a Twin on Mainnet.

If you want to set up a node on Testnet, you need to start with a Twin on Testnet
https://portal.test.grid.tf/

Make sure you select the correct corresponding choice also on the Bootstrap site:
Mainnet: https://v3.bootstrap.grid.tf/

There is still an issue because from a mainnet Twin and Farm, the link
Bootstrap node image: Take me to bootstrap page
takes you to https://dev.bootstrap.grid.tf/ and defaults to Testnet…

So, don’t get trapped & confused:
Main, test and devnet are 3 different chains / grid stacks with each service like the portal having its own url

Many thanks to @bertcoesens and @muhamadazmy (@azmy) for clarifying the issue

I made the same mistake since the testnet loads by default.
Thanks for clarifying.

1 Like