Node desqualified and planned downtime

[Pac]

Hello @lordsam and welcome to the forum.

@lordsam

In the process I mistakenly pointed it to the same identify of the first node and it run for a couple of minutes before I removed the docker container

Sorry to hear that
I’m surprised running a node just for 2 minutes with the wrong identity can disqualify it though. Having a node configured with the wrong identity can disqualify it fast, but not that fast I believe.

You should check your logs:

How do I check my logs? - Storj Docs

And search for lines that contain both “audit” (or “repair”) and “failed”.
On linux this can be achieved like so:

docker logs YOUR_NODE_NAME 2>&1 | grep -E "GET_AUDIT|GET_REPAIR" | grep failed

@lordsam

I will have to move my hardware to a new data center soon and I fear that it will take more than 5 hours

You have way more than 5 hours before getting suspended:

Availability and bandwidth control for the operator

Hello @gusmb, Welcome to the forum! Your node could be offline for 288 hours before suspension, then you would have a week to fix the problem. After you fixed the problem your node would be on review for the next 30 days. If node would be still suspended after 30 days it will be disqualifed. To recover online score the node should be online for the next 30 days. Suspension mean that your node will not receive a traffic. Since your node offline or suspended, all its pieces considered as unhea…