Disqualified after 3 years

[Alexey]

The writeability check creates a small file inside the storage folder, i.e.:

> ls X:\storagenode2\storage\

    Directory: X:\storagenode2\storage


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----         7/17/2019   1:03 AM                blob
d-----         1/26/2021   3:21 AM                blobs
d-----          9/1/2023   5:28 AM                garbage
d-----          7/5/2023   6:53 AM                temp
d-----         1/30/2021  10:03 PM                trash
-a----          9/1/2023   5:44 AM       56696832 bandwidth.db
-a----          9/1/2023   5:44 AM          32768 bandwidth.db-shm
-a----          9/1/2023   5:45 AM        6019352 bandwidth.db-wal
-a----          9/1/2023   3:02 AM         143360 heldamount.db
-a----         8/29/2023   3:10 PM          16384 info.db
-a----         8/29/2023   3:10 PM          24576 notifications.db
-a----         8/29/2023   4:33 PM          32768 orders.db
-a----          9/1/2023   5:38 AM          32768 orders.db-shm
-a----          9/1/2023   5:38 AM              0 orders.db-wal
-a----         8/29/2023   3:10 PM          24576 pieceinfo.db
-a----          9/1/2023   5:28 AM          32768 pieceinfo.db-shm
-a----          9/1/2023   5:28 AM              0 pieceinfo.db-wal
-a----          9/1/2023   5:36 AM        9605120 piece_expiration.db
-a----          9/1/2023   5:44 AM          32768 piece_expiration.db-shm
-a----          9/1/2023   5:36 AM             32 piece_expiration.db-wal
-a----          9/1/2023   4:54 AM          24576 piece_spaced_used.db
-a----          9/1/2023   5:24 AM          32768 piece_spaced_used.db-shm
-a----          9/1/2023   5:24 AM             32 piece_spaced_used.db-wal
-a----         8/29/2023   3:10 PM          24576 pricing.db
-a----          9/1/2023   3:00 AM          36864 reputation.db
-a----         8/29/2023   4:30 PM          32768 satellites.db
-a----          9/1/2023   5:29 AM          32768 satellites.db-shm
-a----          9/1/2023   5:29 AM              0 satellites.db-wal
-a----         8/29/2023   3:10 PM          24576 secret.db
-a----         12/6/2020   6:08 PM             32 storage-dir-verification
-a----          9/1/2023   3:02 AM         851968 storage_usage.db
-a----         8/29/2023   3:10 PM          20480 used_serial.db
-a----         5/19/2020  10:37 PM      334069760 used_serial.db.bak
-a----         9/21/2021  12:27 AM              0 write-test428211014

in my case it has a name write-test428211014 (I left this for examples, usually this file is deleted after the test).
For readability check it uses storage-dir-verification file, it contains a NodeID. This file also used to check that the identity is matched the data.

@BrightSilence

The read/writeability check uses a file in a folder higher up from the blobs folder. Since your blobs were offline, but this folder wasn’t, the node assumed your data was in place and kept running.

So, in result the node has been disqualified for losing data. I’m sorry, but reinstatement is not possible in this case, because there is no guarantee, that data is intact, it requires to execute audit for every single piece on your node for the same price as repair, but in case of repair it may never happen (the unhealthy threshold is not reached or the customer deleted their data). It also would be dedicated to only one node from 20k, too expensive.

@AndMetal

Is there any documentation on the different configuration options? I did some digging both on the Storj site (support, documentation, etc) and the Github project but didn’t really find anything useful other than a handful of command line options. I did notice this in my config file:

# directory to store databases. if empty, uses data path
# storage2.database-dir: ""

Move databases on Windows storagenode

Yes, you can. Stop the storagenode Move databases to a new place (C:\storagenode\cache\ for example) Add a new path to databases to the storage2.database-dir: option: storage2.database-dir: C:\storagenode\cache\ Save the config Start the storagenode Check that you do not have a new databases in a old place and the dashboard shows a correct numbers. However, keep in mind - you will introduce a new point of failure.