I checked my config.yaml and it appears that the storage.path was changed.
My Storj data folder shows last access of May 8 and after correcting the config.yaml file, most DBs are updated with today’s date. I didn’t change anything. My node has been online since the alpha and I updated my node from docker to Windows back in November with no issues.
I only have several disqualification emails from various locations but not all of them.
Then your node would not start and should be offline.
If it was online, then it’s stored data somewhere. And this path was correct, otherwise it will be disqualified months ago.
Please, show the result of the command (Powershell):
Well… I guess your node running the incorrect path for a week collected data pieces which are now being audited after you corrected the path… which definitely leads to DQ since those data pieces do not exist in the corrected path.
You should look for all failed audits, remove the last piped command and see what you get. I think “open” was even based on old log terminology, but it definitely won’t show you all errors either way.