Such error is mean that storagenode service can’t start for some reason. Perhaps, you have changed something in the config.yaml, and now the storagenode can’t start.
Please, give me an output of this command (Powershell):
I should warn you - the setup with a network connected drive is not supported, it could work, but can stop working in any time.
You have a high chances to got a corrupted database or missed data in such setup.
Any network connected drive will have a higher latency than a local connected, and your node will loose the race for pieces more often than with a local connected drive.
I would recommend to run your storagenode directly on your storage server, either as a Windows service (if it’s a Windows) or a docker container (if it’s a Linux).
I run a unraid system.
On that system I had the Storj docker installed. But out of nowhere the docker got corrupted.
It had something to do with SQL and the solution was to downgrade unraid.
That was my problem: (I’m not the author, but had this problem)
That is not the solution I want for my system.
So I created a Win 10 Pro VM on my unraid system and on that Windows runs now Storj (with the same data from the unraid container).
I agree with you, that this is not a shiny solution, but it works. At least until now.
I would really like to switch to my docker again, not only beacause my system pulls now 15 W/h more.
Is there a “how to install storj on unraid 6.7.2”?
Now that I read that article again, I might know why I had that problem.
After I installed the docker, an update for the docker was available, so I installed it.
And right after the update, that problem occured.
Seems that this would be the solution?
“It’s also important to not stop the Storj docker from the ui, but instead type docker stop -t 300 storagenode in the terminal. If using an autoupdater, make sure to also set its timeout to 300 before stopping.”
I have checked all the db files. This is the only one that has errors. Can the problem be there? Can be solved?
C:\Users\bbvedf\Downloads\sqlite-tools-win32-x86-3380000>sqlite3 f:\storage_usage.db "PRAGMA integrity_check;"
*** in database main ***
On tree page 167 cell 37: Rowid 116129 out of order
On tree page 167 cell 36: Rowid 116130 out of order
On tree page 167 cell 35: Rowid 116130 out of order
On tree page 167 cell 34: Rowid 116130 out of order
On tree page 167 cell 33: Rowid 116131 out of order