My “bandwidth” database is corrupt… yay… file is not a database. GREAT Utter bullcrap. I’m out! Edit: This was written in anger when my setup failed out of the blue. Mostly because of the responses here and people like beast and littleskunk I still seem to have a few tries in me to try again. Wh…

[image] anon27637763: it’s rather that db corruption can be less likely using a tailored postgres configuration which is not possible using sqlite. Like in our last conversation I recommend you open a pull request for postgres support. Feel free to proof your statements. Right now I have the …

[image] littleskunk: that under the conditions sqlite3 is getting corrupted right now, postgres will get corrupted as well. And I’m pointing out that this very thread is proof that SNOs do not understand what this means, nor how to fix it. The installation documentation should be written suc…

I did full checkdisk /r and no issues there, SMART is all green

Ok, I had that option checked, now it’s off. Despite my pessimistic and venting post, I might still have a few retry-s in me left. Maybe this should be mentioned in setup guide as ’ best practice ’ to uncheck that caching option. Now just to wait for a new registration code. BTW beast and littles…

[image] anon27637763: the problem is due to a very low level OS/hardware issue which is not easily discoverable for the general user and also not documented well in the SNO installation guide as a potential problem. As a storj employee I will leave that decision to @Alexey @Dylan @Knowledge A…

I think disabling write cache should go into the installation documentation for windows. Judging from many threads in here most people are not familiar with anything besides knowing how to use a PC and I wouldn’t rely on people knowing the “basics” (which is a term differently for everyone).

[image] littleskunk: For that reason I vote with no. Let them get disqualified and learn from there mistakes like we all did and still do. Database corruption is a common enough problem: Storj Forum Search Results …that it should be addressed in the base documentation. The Storj network be…

Especially from our windows users you shouldn’t expect them to know about anything. I use writecache on windows myself without any problems and didn’t immediately think about it as a possible error source (especially as OP didn’t mention windows as OS). No typical windows user will know about those…

Port forwarding is also a common problem. That doesn’t necessary mean we have to explain it to everyone including to thausends of storage nodes operators that didn’t have that problem.

Well it’s your company but the typical company explains everything so even the biggest idiots know what to do best because the company profits from that and avoids frustration and support time. If STORJ likes to handle it differently that is certainly your choice.

Storj Community Forum (official)

I'm done... 4th time the database has randomly corrupted FTS. I'm out!

Node Operators troubleshooting