Alexey
October 7, 2019, 10:57pm
14
Your node is not disqualified for downtime. This check is under construction:
Hi everyone,
Our initial attempt to calculate SNs reputations using based on audits and uptime reputation didn’t work out as we thought, for such reason, we disabled the disqualification due to uptime failures as it was the one which caused to disqualify several nodes without being clear how long they were offline.
We need to enable back the uptime reputation calculation of the SNs and disqualify those ones which aren’t online long enough for keeping our network healthy, for such reason we are…
Yes. You can attach the disk to the VM on Hyper-V.
However, I would recommend to create a virtual disk and attach it to the VM.
Partition it and format it to the ext4. Add it to the /etc/fstab
. Then move all data to there (from SMB attached drive).
Short term you can carefully use this suggestion:
I fixed my issue by stopping the node and removing the docker image. Copied the storage folder that was on a nfs mount locally (I used /storj), except for the blobs directory since it’s too big. Entered the docker command with the new storage path. This updated the DB and created the new files. I then stopped and removed the docker image. Copied all files back to my nfs mount. And recreated the docker image with the nfs mount like I was running before, and everything is working now.
I tried to …