DISK ERROR - "version": "v1.155.4" - please revert it

Hello everyone.

The Storage not Met issue seems to have come back .

@Alexey

2026-06-10 10:18:04,568 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-06-10T10:18:16Z    ERROR   Total disk space (minus reserved bytes) is less than required minimum   {"process": "storagenode", "bytes": 500000000000}
2026-06-10T10:18:16Z    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.(*DedicatedDisk).PreFlightCheck:50\n\tstorj.io/storj/storagenode/monitor.NewDedicatedDisk:33\n\tstorj.io/storj/storagenode.New:627\n\tmain.cmdRun:107\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.(*DedicatedDisk).PreFlightCheck:50\n\tstorj.io/storj/storagenode/monitor.NewDedicatedDisk:33\n\tstorj.io/storj/storagenode.New:627\n\tmain.cmdRun:107\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:109\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.(*DedicatedDisk).PreFlightCheck:50
        storj.io/storj/storagenode/monitor.NewDedicatedDisk:33
        storj.io/storj/storagenode.New:627

I have now reverted to 1.52.6

remove the /bin/* items , - restart node

Same error here.

Please devs, you had this exact error earlier and had to rollback - something in QA needs to improve.

@Andrii – forum post re: error i have posted on your app release note

Hi, i have 20 nodes but i don’t view nothing errors or oversize report in the webpage of node. 15 nodes are updated

I have 2 updated nodes, one on windows and one on qnap arm and they work, completely migrated to hashstore

total remaining space over 500gb ?

It appears to be looking at ‘remaining space’ , rather than ‘disk size’

my full nodes , have 100GB left

do those nodes have more than 500GB space remaining ?

4 nodes are full but not view oversize and others are over 500gb remaining but the size remaining are correct. I don’t know if all nodes are hashstore or piecestore. I not controlled , i power on the nodes and they works, and i wait the first days of the month for payment. :rofl:

My affected nodes are hashstore + dedicated disk

the node on windows has 15 Gb free, the qnap one 3 Tb free, not dedicated disk

massive node outages assigned to this bug. 30+ of my nodes .

Can you reproduce the bug with the default shared disk space calculation?

dedicated is both experimental and deprecated.

Still it’s a bug, but if it’s a dedicated only, I would rather remove that option from the code.

4 of my nodes was affected. They are not using dedicated. Reverting to 1.152.6 solved the problem.

I don’t understand this bug report: is it that any node with less than 500GB of free space is failing to start?

All my 4 nodes updated within a 5 min period (which is not ideal in itself, but another topic) this morning and all are (seem to be!) running fine.
No dedicated disk, no hashstore options selected, free space min 10GB, max 1.6TB

This exactly. Less than 500GB free → node won’t start.

It looks like you’re referring to versions 1.155.4 and 1.152.6, because version 1.55.6 is too old.
What are the disk allocation parameters, how much free disk space, and what are the sizes of the blobs folder and hashstore folder?
Also what’s reported by the dashboard after revert?

log before it dies.

2026-06-11T08:09:28Z    INFO    Running on version      {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.6"}
2026-06-11T08:09:28Z    INFO    Downloading versions.   {"process": "storagenode-updater", "server_address": "https://version.storj.io"}
2026-06-11T08:09:28Z    INFO    Current binary version  {"process": "storagenode-updater", "service": "storagenode", "version": "v1.155.4"}
2026-06-11T08:09:28Z    INFO    Version is up to date   {"process": "storagenode-updater", "service": "storagenode"}
2026-06-11T08:09:28Z    INFO    Current binary version  {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.6"}
2026-06-11T08:09:28Z    INFO    Version is up to date   {"process": "storagenode-updater", "service": "storagenode-updater"}
2026-06-11 08:09:29,501 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-06-11 08:09:29,501 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-06-11 08:09:29,502 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-06-11T08:10:19Z    ERROR   Total disk space (minus reserved bytes) is less than required minimum      {"process": "storagenode", "bytes": 500000000000}
2026-06-11T08:10:20Z    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.(*DedicatedDisk).PreFlightCheck:50\n\tstorj.io/storj/storagenode/monitor.NewDedicatedDisk:33\n\tstorj.io/storj/storagenode.New:627\n\tmain.cmdRun:107\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.(*DedicatedDisk).PreFlightCheck:50\n\tstorj.io/storj/storagenode/monitor.NewDedicatedDisk:33\n\tstorj.io/storj/storagenode.New:627\n\tmain.cmdRun:107\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:109\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.(*DedicatedDisk).PreFlightCheck:50
        storj.io/storj/storagenode/monitor.NewDedicatedDisk:33
        storj.io/storj/storagenode.New:627
        main.cmdRun:107
        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
2026-06-11 08:10:21,362 WARN exited: storagenode (exit status 1; not expected)
2026-06-11 08:10:22,367 INFO spawned: 'storagenode' with pid 66
2026-06-11 08:10:23,369 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-06-11 08:10:23,369 WARN received SIGQUIT indicating exit request
2026-06-11 08:10:23,370 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2026-06-11T08:10:23Z    INFO    Got a signal from the OS: "terminated"  {"process": "storagenode-updater"}
2026-06-11 08:10:24,380 INFO stopped: storagenode-updater (exit status 0)
2026-06-11 08:10:26,383 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-06-11 08:10:29,386 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-06-11 08:10:32,388 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-06-11 08:10:34,389 WARN killing 'storagenode' (66) with SIGKILL
2026-06-11 08:10:35,395 WARN stopped: storagenode (terminated by SIGKILL)
2026-06-11 08:10:35,395 INFO waiting for processes-exit-eventlistener to die
2026-06-11 08:10:35,396 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)

disk:

/dev/sdb        7.3T  6.8T  130G  99% 

in my docker run

  --storage2.monitor.dedicated-disk=$storage2_dedicatedDisk \
  --storage2.monitor.reserved-bytes=$storage2_dedicatedDisk_reservedBytes \

values:

storage2_dedicatedDisk=true
storage2_dedicatedDisk_reservedBytes=100GB

I hope we can get it fixed

@Alexey @elek @Andrii

Please try to disable the deprecated dedicated disk feature and use the allocation instead.