I have an node that is configured on a TrueNAS system. Last month I upgraded my TrueNAS to the latest version and that introduced a bug in the Kubernetes integration and that cause my node to block daily. It took about 2 weeks until I managed to upgrade to the latest version from TrueNAS and apply a hotfix to make the image stable (now it is not fixed for good 24.04 (Dragonfish) Version Notes | TrueNAS Documentation Hub)
In this period my node was " Your node has been disqualified on 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"
I understand this and it is OK it is my problem not the network problem, also I am on yellow sign to other satellites:
I need a recommendation start a new one or continue with this.
If the best path is to start a new one I want to gracefully close this one and recuperate all the funds.
I need instructions on how to do the 2 part job: 1. close and 2.withrow.
I am located in East Europe
10q.
Hello @yang_system ,
Welcome to the forum!
Since the node is disqualified only on one satellite, you may continue run it, all remained satellites will pay for the usage.
However, you may also call a Graceful Exit on remained satellites: Graceful Exit Guide (new procedure as of 2023-10-?), if the node is older than 6 months, otherwise GE wouldn’t be available.
The online score would fully recover after 30 days online, audit scores can recover only if the data is intact and audit score not less than 96%. But if it is damaged, as in Saltlake, then the node could likely soon be disqualified on all other satellites as well.
Just a tangential comment: when people ask me why do I stay on Core and not migrate to scale, that is “it’s just as good”, “it’s also very stable”, “Linux is the future”, “Containers!!!1111”, they almost reached performance parity — your post illustrates one of many reasons why…
OK I will wait until next month and se then if I recover the node.
If not I will ask again for help on how to move the rewards and start a new node.
1 Like
