Hi All, I was replacing some network equipment and decided to update the software on the linux machine running my node. I restarted the machine after the updates and noticed my used disk space had been reset from near 1.6 TB to about 500 MB (I did not pull up the dashboard right away, it probably s…

Update: After a graceful reboot, the node will not start due to insufficient disk space error (the drive is 2TB, with 288GB currently free).

Makes sense since the minimum space requirement is 500GB and the node can’t see that the used space is actually being used by storj.

When I updated and ran the node for the first time, the disk had ~300GB free, which is still well below the minimum. It ran succesfully.

This seems exactly like the pattern of behaviour I saw. Although I have more than enough free space, on the first restart when my used space went back to zero, the node did not detect that my allocated space was less than the free space, and gave no errors to that effect. On subsequent restarts my n…

I am still unable to get the node to read the old database. I’d be reluctant to delete the possibly abandoned data because I risk deleting something else by accident (timestamps do not give me absolute certainty). Still looking for advice, downtime is growing… @Alexey , could you chime in?

Please, enable a debug log level for your storagenode (log.level: debug in your config.yaml), save the config and restart the node. Please, check logs of the node for some errors related to any database.

Thanks for chiming in, Alexey. Here’s the log output: 2019-12-16T07:06:10.201Z INFO Configuration loaded from: /app/config/config.yaml 2019-12-16T07:06:10.202Z DEBUG debug server listening on 127.0.0.1:33127 2019-12-16T07:06:10.219Z INFO Operator email: fragamemnon@ove…

[image] fragamemnon: piecestore monitor: disk space requirement not met This is the consequence of losing database… The only way - to free up some space on that drive to be able to run a node. Since it doesn’t recognized the own pieces, it can see only the free space. It should have at least…

So it seems I might have been a bit impatient when I reported back initially. After replacing the owner on the entire node working folder, I started the node and the used space started at 0 again. I had let the node run for about 60s, the used space had gone up to about 100 MB. I self-declared the p…

I’ve follwed the database repair steps. However, the HDD is of 2TB capacity, and I have 1.6TB of node data. How should I proceed about freeing up space?

Storj Community Forum (official)

Used disk space resets after node rm/restart

Node Operators troubleshooting