Hi,
I have two nodes on two separate computers.
Today, when I was at work, the power supply in one of the computers burned out, damaging the motherboard and disks (2x SSD and 2x HDD).
The computer in which the power supply burned out was built on new components.
I checked the two HDDs on another computer, but they don’t even start.
In such a situation, can my node on the computer that is working be blocked or disqualified?
Do I have to worry about the node that is still working?
TIA!
Absolutely no worries for your surviving node.
2 cents
Julio
P.S. Unless it’s got the same branded power supply 
heh
I strongly suggest buying used and enterprise components on eBay, not new and/or consumer trash. Especially power supplies. For multiple reasons:
Hello @mikeuk,
Welcome to the forum!
All nodes are independent of each other.
Sorry, but what do you mean by independent?
I’m just starting out with Storj and I’m not sure what you mean.
I started the node that’s still working 6 weeks ago, the second node that stopped working I started a week ago.
If the node is less than a week old, then you can safely recreate a new identity and start a new node
Each node has it’s own identity; that is what you create with each token received.
That’s the only passport for your node. The IP or email or wallet dosen’t matter. You can move your node anywhere in the world. It will be identified by the node ID, which is in those identity files from Idenity dir.
And this unique Identity makes it independent from any other node, no matter if you use the same IP for both, the same wallet, or the same email.
If one node fails in your little farm, the other nodes keep working. Their scores won’t be influenced by the dead one.
I’m currently at a friend’s who is an electronics engineer. He managed to start this disk, I know he did something with the disk electronics.
The disk is currently starting, but it is in read-only mode.
We’ll try to clone this disk to a new one soon.
The Node that crashed at 5pm will be offline for 36 hours.
Disk cloning will take another 30-35 hours (this is the time the program currently shows).
Let’s say that the Node will be ready to work again after 72 hours, i.e. 3 days.
Is there any point in starting it again?
I selected the option: copy all files
Perhaps not worth it, if you suspect more than 4% of data loss. If the data is not affected, then you may continue run it. Just a week seems too small age to spend so much efforts on it. But it’s up on you.
The node can be disqualified for downtime, if it was offline more than 30 days. However, it would not leave without consequences. After 4 hours offline all pieces on the node considered as unhealthy, so they may be recovered to other nodes in the network, so, when you bring your node online this data will be removed from your node to the trash and will be deleted 7 days later. The longer node is offline, the more data could be deleted later when you bring it online.
It looks like all the data is still on this drive and hasn’t been corrupted.
I’m saying this because I’ve recovered my files that I had on this drive and they’re not corrupted.
There are 20 hours left of disk cloning.
Once this process is complete I’ll start Node and see what happens.
60 hours offline would result in 90% online score. Something is not right here, likely your node was offline for longer.
I know it should be 90% or a bit more, but I don’t know why it shows so much less.
I don’t know if this problem is something on my side because I have a second node on another server and yesterday I turned it off for exactly 3 hours.
After starting again Node it showed me that it was online 95.7%
I wouldn’t expect this number to be reliable for young nodes because calculation is based on a small number of audits.
