If a disk disconnects while a node is running, if audits happen during this time is this still considered as missing pieces that could lead to very fast disqualification?

[Alexey]

We already have some:

Disqualified after 2 hours of [edit] failed audits?

Beat me to it! In any case… I’ll post what I was writing anyway… A bash script to check if a file exists on GNU/Linux systems with bash installed: #!/bin/bash if [ ! -f is_connected ]; then echo -e "WARNING! Storage is disconnected.\nShutting down Node...\n" # iptables -I INPUT -p tcp --dport 28967 -j REJECT docker stop -t 300 storagenode && exit 0 fi echo -e "Storage is connected.\n" #if [[ $(iptables -C INPUT -p tcp --dport 28967 -j REJECT) ]]; then # iptables -D INPUT -p tcp…

Prevent broken mount points from DQing nodes

For logs written to a file tail -f /volume1/storj/v3/data/node.log | awk '/(ERROR|canceled|failed).*GET_AUDIT/ {system ("docker stop -t 300 storagenode")}' For logs in docker docker logs -f --tail 20 storagenode | awk '/(ERROR|canceled|failed).*GET_AUDIT/ {system ("docker stop -t 300 storagenode")}' Please be aware I haven’t tested the docker version. But it should work. This stops your node if it encounters a single audit failure, that might be overly aggressive as it would also kill your …

Disqualified after 2 hours of [edit] failed audits?

@Hacker you can use the below powershell script to monitor for when the usb disconnects. When it detects a usb disconnection event, it will shutdown the storagenode. All you have to do is change the $driveLetter -eq ‘D:’ with the Letter of your usb drive. I know it is not a solution but it helps prevent those audit errors. If you combine this with uptimerobot monitoring you should get notified since the storagenode goes offline. Register-WmiEvent -Class win32_VolumeChangeEvent -SourceIdentifi…