My nodes updated now to v 1.152.5 and did not started. 2026-04-23T20:04:36Z WARN Disk space is less than requested. Allocated space is {"process": "storagenode", "bytes": 352777011200} 2026-04-23T20:04:36Z ERROR Total disk space is less than required minimum {"process": "storagenode",…

the fix in 1.52.6 work for me :tada:

Same issue for me. 2 of my 3 storagenodes have been upgraded today from v1.148.3 to v1.152.5 After the upgrade, the 2 upgraded nodes failed to start with this error: 2026-04-23T21:51:55Z WARN Disk space is less than requested. Allocated space is {“process”: “storagenode”, “bytes”: 155761098752} …

Excellento, Despite the solution previously accepted, this actually works, ie: specifically only the storage2.monitor.dedicated-disk: true is needed. Thanks @alamdarzia ! 2 cents, Julio

Hi guys, my overused space is almost 4TB. The hard drive is a 12TB Exos, with 2TB free space (reported by OS). My node is only recognizing 5.59TB, despite the value in config file being 10.9TB. I can put whatever value in config, the dashboard only sees it as 5.9. I don’t know how to handle this, …

Looks like problem with v1.152.5 [image]

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,…

[image] Release preparation v1.152 STORJLINGS Thank you @ItsHass . Investigating that problem. 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 befo…

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.

Bug in 1.152.5 - disk size

Node Operators troubleshooting

ItsHass April 24, 2026, 7:31am 64

Confirmation of this being investigated