Hey - how can i check if this node is disq on any of the satelites?
It has had alot of problems with the disk (it was a DOA).
So since the node is 2 months old my friend is considering to just remake the node on the new disk.
what is the best to do here?
You will receive an email notification, you will see a message on the dashboard, your audit score would be below 96% and in red.
The disqualification for downtime could be applied, if your node was down for more than 30 days (or more than 30 days have an online score below 60%). And you would see a message on your dashboard in that case too.
But basically you need to bring it online with its data and wait for a while.
Or do you mean, how to check that without having its data?
You may give me a NodeID and I may check. I do not think that it makes any sense though, because if you do not have its data - it’s useless already.
We have all The data. No problem there.
All i wanted to be sure was if it was disqualified for downtime.
I see there’s an hour delta between your posts. Yes, it’s entirely possible to be disqualified in such a short period. I would expect by now 11+ hours later that it’ll actually be showing the <96% failed audit scores. The downtime would have been a symptom, and not the cause. If I had to guess the recent data deletion would have been a contributing factor, ie: 4% of 10 TB vs. 4% of 1 TB, thus exposing longer term file system errors/malfunction (albeit only 2 months.)
1 cent
Just out of curiosity…
Were there any tells as to this “issue behavior” ?
Is it really dead or does it cause read/write issues?
Its not really dead. We took The node offline for a Clone for some days.
HDD was just giving about 300 dead sektors. So it was changed out
Just to clarify, your node wouldn’t get disqualified simply for being offline for a few days. What’s more likely is that it failed too many audits. While I didn’t see a lower audit score in the screenshot of your dashboard, it’s a good thing to check.
It can be disqualified for more than 30 days downtime or too many suspensions for 30 days (the node has an online score below 60% all the time).
So, unlikely the reason was a downtime, the reason is failed audits. So either data was missing or unavailable or corrupted.
