Total disk space is less than required minimum

[Alexey]

Since you deleted a database, the node now doesn’t know is it its data or just you are trying to run it on a small disk?
The current safe minimum is 500GB (and of course 261GiB (Windows uses a wrong measure units) is less than 500GB).

If you are sure, that the path is correct, you may enable a scan on startup if you disabled it (it’s enabled by default), uncomment and reduce a monitoring threshold to less than you currently see as a free space (in SI units 261GiB would be 280.24GB, but it’s better to specify just 200GB):

Node with less than 500gb

storage2.monitor.minimum-disk-space option in the config.yaml

Save the config and restart the node either from the Services applet or from the elevated PowerShell:

Restart-Service storagenode

Then wait until all filewalkers will be successfully finished:

Storagenode.exe stopping for too long, for 10h+

Windows/PowerShell Logs should be at least info level Used space filewalker Regulated by the parameter in the config.yaml file or as a command line argument (add -- before the parameter, remove :, place it after the image name in your docker run command): # if set to true, all pieces disk usage is recalculated on startup (default true) storage2.piece-scan-on-startup: true to watch for a progress: cat "C:\Program Files\Storj\Storage Node\*.log" -Wait | sls "used-space-filewalker" | sls "sta…

After that it’s advisable to comment out the reduced monitoring. It may help to do not destroy your node if the path is wrong.