Bug in 1.152.5 - disk size

Subject: Node showing incorrect disk space and “Overused” status after v1.152.5 update

"I am experiencing a failure in one of my nodes. I have always had it configured to use 5TB on a 6TB drive. Currently, I have a little over 3.5TB of data stored, and this node has been running since 2023.

Today, after restarting the node, I noticed that it only detects 2.33TB of available space instead of the configured 5TB. As a result, it is now showing an ‘overused’ status of 1.21TB. I noticed that the node has recently updated to version v1.152.5."
Windows Node

Confirmation of this being investigated :check_mark:

Same problem with mine noticed last night it was constantly restarting. cant seem to get the work around to work with mun think its because i used one of the scripts to set it up and its put my config somewhere else. If i just leave it on restarting will it pick up the next update if theres one before i am disqualified? Also to note i didn’t get any emails notifying me that my node was offline like i usually do so how many others haven’t noticed yet!

I noticed this morning around 30% of my nodes are down. Should we wait for a fix?

The storagenode doesn’t reach as far into the startup process that an automatic upgrade will be possible, so manual intervention is required. Appending “storage2.monitor.minimum-disk-space: 1 GB” to config.yaml works for me, so batching that up now, all will be online again in a few minutes.

Hi Peter,

@Andrii is working on it in the background with Storj Devs from what we understand… - I would recommend to mitigate the situation yourself , and once a fix comes in , remove the additional config.

Thank you @elek

1.152.6 is now publishing… It will take abit of time to get through the network.

Docker image upgrade could also work.

Hello - i seem to have the same issue with on of my windows nodes.

but:

That seems broken. restart has not helped.

the fix in 1.52.6 work for me :tada:

Is it possible to force an update to 1.152.6 or do I have to let it be and the update will get picked up on its own? I tried forcing a docker image update but there was nothing new to pull. I’m guessing the update is done outside docker.

I’m starting to rollback , that additional config in my nodes :slight_smile:

BTW negative values also work if you have over usage of space.

If it’s not yet updated, you can force it by removing a bin subfolder from the data location.

Hello @Wirecin,
Welcome to the forum!

If it’s not yet updated, you can force it by:

  1. stop and remove the container
  2. remove a bin subfolder from the data location
  3. run the container back.

It now rolled me back to 1.148.3. Is that normal?

My node went offline since 2 days. I looked into it. The node tells me it has not enough space (less than 500GB). Even though the node is 1TB in size. The node “thinks” the free space is the space it has to run the node in, for some reason.

2026-04-26T00:41:41Z	WARN	Disk space is less than requested. Allocated space is	{"process": "storagenode", "bytes": 145294295040}

2026-04-26T00:41:41Z	ERROR	Total disk space is less than required minimum	{"process": "storagenode", "bytes": 500000000000}

2026-04-26T00:41:41Z	ERROR	failure during run	{"process": "storagenode", "error": "Failed to create storage node peer: piecestore monitor: disk space requirement not met\n\tstorj.io/storj/storagenode/monitor.(*SharedDisk).PreFlightCheck:117\n\tstorj.io/storj/storagenode/monitor.NewSharedDisk:71\n\tstorj.io/storj/storagenode.New:632\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:290", "errorVerbose": "Failed to create storage node peer: piecestore monitor: disk space requirement not met\n\tstorj.io/storj/storagenode/monitor.(*SharedDisk).PreFlightCheck:117\n\tstorj.io/storj/storagenode/monitor.NewSharedDisk:71\n\tstorj.io/storj/storagenode.New:632\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:290\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(*Command).execute:985\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tmain.main:34\n\truntime.main:290"}

Error: Failed to create storage node peer: piecestore monitor: disk space requirement not met

	storj.io/storj/storagenode/monitor.(*SharedDisk).PreFlightCheck:117

	storj.io/storj/storagenode/monitor.NewSharedDisk:71

	storj.io/storj/storagenode.New:632

	main.cmdRun:84

	main.newRunCmd.func1:33

	storj.io/common/process.InitBeforeExecute.func1.2:389

	storj.io/common/process.InitBeforeExecute.func1:407

	github.com/spf13/cobra.(*Command).execute:985

	github.com/spf13/cobra.(*Command).ExecuteC:1117

	github.com/spf13/cobra.(*Command).Execute:1041

	storj.io/common/process.ExecWithCustomOptions:115

	main.main:34

	runtime.main:290

df -h tells:

/dev/sde4 1,1T 908G 136G 88% /srv/dev-disk-by-uuid-de75ca90-63fd-406f-8c53-93adf96fca93

How can I fix this? I had nodes with less than 4GB free disk space, this was never an issue.

Thanks in advance.

This is mean that your node is not eligible to be updated to a new version. You may check your logs to make sure.

Well I was on 1.152.5 just yesterday. How could I not be eligible anymore? What kind of entries should I look for in the logs?

The combination of the seed and the cursor is used as a mask for your NodeID, so if it’s not match, then it will not be updated.

You may search for “version” in your logs, e.g.

docker logs storagenode 2>&1 | grep "version"