Hi, I have a long running node (with high performance if you ask me) on my server, node ID 12DpuxieuH7SBVtA4zTtKHafvNyBEtqBm7QEZdSKqmUsHLch1ey , which has now been disqualified on Europe-West
The server suffered hardware damage during transport when moving to a new home. It took some time to diagnose the problem which ended up to be motherboard failure. As we were moving at that time, it took a while to diagnose the problem, get new parts and get the server up and running again. Fortunately all the data was intact and I was able to reinstall, which also allowed me to upgrade the software as well (Debian upgrade from Stretch/OMV4 to Buster/OMV5).
The node is now back online and all was looking well, but I a small mistake mapping the storage directory to the new docker image. After about 30 minutes I noticed this because usage on the dashboard was too low, so I took the node offline and corrected the docker mapping to the old storage dir.
During this time, the node was already getting in new data quickly, but obviously failed to audit the old data. Europe-West is probably closest to me and was quickest, but now has an audit score of 59.9% so that means disqualification.
Your node has been disqualified on Tue, 25 Aug 2020 07:57:32 GMT . If you have any questions regarding this please check our Node Operators thread on Storj forum.
Is there any way to fix this? I hope this can be repaired because permanent disqualification seems a bit harsh for a small mistake like this. I have my node running since the alpha version of v3 and really did my best to be a good SNO and restore the data.