Node is disqualified. My own fault, but what to do now?

Hello. i recently had issues with a disk. I started a migration to a new disk. and a few of the pieces never made it over.
i then started dropping in audit score and eventually got this message:

The node is many months old.
What is the best course of action for me here?

is it best to start a brand new node?
is have alot of data on it, (dont mind the small space on it currently.)
What is my move here?

Disassamble the old drive and take the magnets.
I don’t know if you can save the other sats, but if nothing works… format the new one and start a new node with new token and new identity.
Open a beer and relax…
If the other sats survive, you can delete the dirs of the DQ one and start a new node just for it, by putting in config, in the untrusted list, the other 3.
And you will have 2 nodes, one with 3 sats, one with 1 sat. Nothing wrong with that.
And than… open a beer and relax.

Thanks.

Disc is still there and still transferring files to new disk.
I am considering just starting this one all over to have all 3 sats tho…

Did you only loose AP1? Not much data there, I’d keep the node running if you can save the other sats. If they recover nicely you could also do a graceful exit later.

Happened to me due to user error with identities early on and lost EU1. :sweat_smile: But I still get that traffic on my second node so it doesn’t make a difference.

1 Like

Hmm ok! i guess if its only gonna be ap1 i might be fine to keep it running.

For a 4-5TB node you need like an year to get back on track. You have collateral, you have vetting, etc.

Yea im aware - do you know how much of a data% the AP1 satelite has?

AP1 has 3.75% of stored data for my nodes.

1 Like

Thanks, I will see how the node does from here before making a decision