I am using environment variables:
- STORJ_STORAGE2_MONITOR_DEDICATED_DISK=true
- STORJ_STORAGE2_MONITOR_RESERVED_BYTES=25GB
I am using environment variables:
- STORJ_STORAGE2_MONITOR_DEDICATED_DISK=true
- STORJ_STORAGE2_MONITOR_RESERVED_BYTES=25GB
I’m hoping , someone can give the community a easy adjustment to their configs for downgrading the version , so we dont have to do these unsafe configs..
Hello everyone, today I noticed that twoof my nodes are showing the following:
Can someone explain what this is due to?
root@Storj01:~# df -h
Filesystem Size Used Avail Use% Mounted on
rpool/data/subvol-901-disk-0 4.0G 1.3G 2.8G 33% /
/dev/sdk1 11T 5.6T 4.0T 59% /mnt/storjdata
- STORAGE=10TB
volumes:
- /opt/storj/identity:/app/identity
- /mnt/storjdata:/app/config
The other Node is a 4TB Node
root@Storj02:~# df -h
Filesystem Size Used Avail Use% Mounted on
rpool/data/subvol-911-disk-0 4.0G 1.3G 2.8G 32% /
/dev/sde1 3.6T 2.4T 1.1T 70% /mnt/storjdata
- STORAGE=3.6TB
volumes:
- /opt/storj/identity:/app/identity
- /mnt/storjdata:/app/config
My third node doesn’t start at all anymore. It shows the following error message:
2026-04-24T00:14:04+02:00 WARN Disk space is less than requested. Allocated space is {"process": "storagenode", "bytes": 418176114688}
2026-04-24T00:14:04+02:00 ERROR Total disk space is less than required minimum {"process": "storagenode", "bytes": 500000000000}
4TB HDD (- STORAGE=3.6TB) Same as the second one
Thank you very much and best regards.
Well, these configs aren’t working on my side ![]()
Safest stuff to do would be to permit a rollback initiated from satellites
Personnaly, I reconfigured my node as previously and go back to sleep, having a look tomorrow on a global solution
The bug is that somehow this version is doing this math, total disk space minus the reserve is being compared has the free disk space with minimum disk space
Meaning that the config for allowing small drives to be a node (less than 500GB) is now being used for free disk space reporting.
if you change in the config or in the settings the minimum disk space to 1GB it will work if you have at least 1GB free on the node.
i.e. config.yaml
storage2.monitor.minimum-disk-space: 1 GB
Welcome with us ![]()
https://forum.storj.io/t/allocated-disk-space-issue/31712/22
you might try this. trying doesn’t hurt
Привет.
Сегодня внезапно одна из нод перестала работать и упала. В логах вижу информацию что диск слишком маленький для запуска ноды, но диск имеет размер 2Тб.
2026-04-23 23:36:38,576 INFO Set uid to user 0 succeeded
2026-04-23 23:36:38,578 INFO RPC interface 'supervisor' initialized
2026-04-23 23:36:38,578 INFO supervisord started with pid 1
2026-04-23 23:36:39,580 INFO spawned: 'processes-exit-eventlistener' with pid 54
2026-04-23 23:36:39,582 INFO spawned: 'storagenode' with pid 55
2026-04-23 23:36:39,583 INFO spawned: 'storagenode-updater' with pid 56
2026-04-23T23:36:39Z INFO Configuration loaded {"process": "storagenode-updater", "location": "/app/config/config.yaml"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "console.address"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "server.private-address"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "contact.external-address"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "server.address"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "pieces.file-stat-cache"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "storage.allocated-disk-space"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "pieces.enable-lazy-filewalker"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "storage.allocated-bandwidth"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "operator.wallet"}
2026-04-23T23:36:39Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "operator.email"}
2026-04-23T23:36:39Z INFO Anonymized tracing enabled {"process": "storagenode-updater"}
2026-04-23T23:36:39Z INFO Running on version {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.5"}
2026-04-23T23:36:39Z INFO Downloading versions. {"process": "storagenode-updater", "server_address": "https://version.storj.io"}
2026-04-23T23:36:39Z INFO Configuration loaded {"process": "storagenode", "location": "/app/config/config.yaml"}
2026-04-23T23:36:39Z INFO Anonymized tracing enabled {"process": "storagenode"}
2026-04-23T23:36:39Z INFO Operator email {"process": "storagenode", "address": "stas@istas.ru"}
2026-04-23T23:36:39Z INFO Operator wallet {"process": "storagenode", "address": "0xc3f87565c9D033B6B047776487Bc5F8a1a52571d"}
2026-04-23T23:36:39Z INFO server kernel support for server-side tcp fast open remains disabled. {"process": "storagenode"}
2026-04-23T23:36:39Z INFO server enable with: sysctl -w net.ipv4.tcp_fastopen=3 {"process": "storagenode"}
2026-04-23T23:36:39Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "store": "s0", "path": "config/storage/hashstore/121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6/s0/meta/hint-000000000000157b", "writable": [], "largest": 231, "skip": false}
2026-04-23T23:36:39Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "store": "s1", "path": "config/storage/hashstore/121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6/s1/meta/hint-000000000000157a", "writable": [], "largest": 242, "skip": false}
2026-04-23T23:36:39Z INFO hashstore hashstore opened successfully {"process": "storagenode", "satellite": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "open_time": "65.041063ms", "logs_skipped": 40, "logs_matched": 0, "logs_mismatched": 0}
2026-04-23T23:36:39Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "store": "s0", "path": "config/storage/hashstore/12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S/s0/meta/hint-00000000000015e9", "writable": [], "largest": 509, "skip": false}
2026-04-23T23:36:39Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "store": "s1", "path": "config/storage/hashstore/12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S/s1/meta/hint-00000000000015f7", "writable": [], "largest": 533, "skip": false}
2026-04-23T23:36:40Z INFO hashstore hashstore opened successfully {"process": "storagenode", "satellite": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "open_time": "222.372861ms", "logs_skipped": 277, "logs_matched": 0, "logs_mismatched": 0}
2026-04-23T23:36:40Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "store": "s0", "path": "config/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s0/meta/hint-00000000000015c9", "writable": [], "largest": 346, "skip": false}
2026-04-23T23:36:40Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "store": "s1", "path": "config/storage/hashstore/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs/s1/meta/hint-00000000000015b5", "writable": [], "largest": 310, "skip": false}
2026-04-23T23:36:40Z INFO Current binary version {"process": "storagenode-updater", "service": "storagenode", "version": "v1.152.5"}
2026-04-23T23:36:40Z INFO Version is up to date {"process": "storagenode-updater", "service": "storagenode"}
2026-04-23T23:36:40Z INFO Current binary version {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.5"}
2026-04-23T23:36:40Z INFO Version is up to date {"process": "storagenode-updater", "service": "storagenode-updater"}
2026-04-23T23:36:40Z INFO hashstore hashstore opened successfully {"process": "storagenode", "satellite": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "open_time": "133.545819ms", "logs_skipped": 144, "logs_matched": 0, "logs_mismatched": 0}
2026-04-23T23:36:40Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "store": "s0", "path": "config/storage/hashstore/1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE/s0/meta/hint-000000000000156a", "writable": [], "largest": 172, "skip": false}
2026-04-23T23:36:40Z INFO hashstore loaded hint file {"process": "storagenode", "satellite": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "store": "s1", "path": "config/storage/hashstore/1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE/s1/meta/hint-0000000000001561", "writable": [], "largest": 165, "skip": false}
2026-04-23T23:36:40Z INFO hashstore hashstore opened successfully {"process": "storagenode", "satellite": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "open_time": "66.94677ms", "logs_skipped": 30, "logs_matched": 0, "logs_mismatched": 0}
2026-04-23T23:36:40Z WARN Disk space is less than requested. Allocated space is {"process": "storagenode", "bytes": 308672462848}
2026-04-23T23:36:40Z ERROR Total disk space is less than required minimum {"process": "storagenode", "bytes": 500000000000}
2026-04-23T23:36:40Z 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
2026-04-23 23:36:40,448 WARN exited: storagenode (exit status 1; not expected)
df внутри контейнера:
# docker exec storagenode df -h
Filesystem Size Used Avail Use% Mounted on
overlay 1.8T 1.3T 564G 69% /
tmpfs 64M 0 64M 0% /dev
shm 64M 0 64M 0% /dev/shm
/dev/mapper/pool-storage 1.8T 1.3T 564G 69% /app/identity
storj 1.8T 1.6T 288G 85% /app/config
udev 30G 0 30G 0% /dev/tty
tmpfs 30G 0 30G 0% /proc/asound
tmpfs 30G 0 30G 0% /proc/acpi
tmpfs 30G 0 30G 0% /proc/scsi
tmpfs 30G 0 30G 0% /sys/firmware
Команда запуска контейнера:
docker run -d -p 28967:28967/tcp -p 28967:28967/udp -p 14002:14002 --restart unless-stopped --stop-timeout 300 -e WALLET="" -e EMAIL="email" -e ADDRESS="address:28967" -e STORAGE="1.6TB" --mount type=bind,source="/home/storj",destination=/app/identity --mount type=bind,source="/mnt/storj/storj",destination=/app/config --name storagenode storjlabs/storagenode:latest
Упал ровно в 00:00. Что делать?
check this. maybe it is the same?
Found the solution (kinda): add these lines to /app/config/config.yaml: storage2.monitor.minimum-disk-space: 1 GB
storage2.monitor.dedicated-disk: true
storage.allocated-disk-space: 966367641600 # 900GB in bytes
Then restart the node.
Verified Working
Tested on Ubuntu 22.04 with Docker, 900GB dedicated disk. Node runs stable and dashboard accessible.
Hope this helps others stuck with the same issue!
Same, some node updated to this and it is saying 0 free space in dashboard
Edit: this seems to work for a work around storage2.monitor.dedicated-disk: true
Thanks and can confirm, my nodes also stopped accepting new ingress, egress was working fine. I already had the following line but this wasn’t enough:
storage.allocated-disk-space
First added this line, still didn’t work:
storage2.monitor.minimum-disk-space
Until I added the next one, it started working again.
storage2.monitor.dedicated-disk:
My nodes failed to start with 1.152.5 as well. I edited the config file to uncomment out the default value of
storage2.monitor.minimum-disk-space: 500.00 GB
and changed it to:
storage2.monitor.minimum-disk-space: 5.00 GB
Seems the start-up procedure was expecting my node’s drive to have 500GB of free space, which is unrealistic since that drive is full to the brim with Storj data.
Notified the team. I marked a current workaround as a solution.
Hello @DutchSNO,
Welcome back!
You need also to provide a value, e.g.:
or
save the config and restart the node.
Остановите и удалите контейнер, затем либо установите в config.yaml:
либо через опцию после имени образа:
в вашей docker run команде и запустите контейнер обратно.
I seem to have the same issue, running it on Unraid.
Nothing changed in my config either, it was set for a few months already at 8TB.
I have dedicated disk parameter … how can i fix this
2026-04-23 20:29:38,039 WARN exited: storagenode (exit status 1; not expected)
2026-04-23 20:29:44,201 INFO spawned: 'storagenode' with pid 57
2026-04-23 20:29:44,201 WARN received SIGQUIT indicating exit request
2026-04-23 20:29:44,498 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2026-04-23T20:29:45Z INFO Got a signal from the OS: "terminated" {"process": "storagenode-updater"}
2026-04-23 20:29:45,417 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-04-23 20:29:45,457 INFO stopped: storagenode-updater (exit status 0)
2026-04-23 20:29:48,461 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-04-23 20:29:51,465 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-04-23 20:29:54,467 INFO waiting for processes-exit-eventlistener, storagenode to die
2026-04-23 20:29:55,468 WARN killing 'storagenode' (57) with SIGKILL
2026-04-23 20:29:56,473 WARN stopped: storagenode (terminated by SIGKILL)
2026-04-23 20:29:56,496 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2026-04-23 20:32:21,663 INFO Set uid to user 0 succeeded
2026-04-23 20:32:21,673 INFO RPC interface 'supervisor' initialized
2026-04-23 20:32:21,673 INFO supervisord started with pid 1
2026-04-23 20:32:22,676 INFO spawned: 'processes-exit-eventlistener' with pid 34
2026-04-23 20:32:22,678 INFO spawned: 'storagenode' with pid 35
2026-04-23 20:32:22,682 INFO spawned: 'storagenode-updater' with pid 36
2026-04-23T20:32:22Z INFO Configuration loaded {"process": "storagenode-updater", "location": "/app/config/config.yaml"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "server.private-address"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "server.address"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "console.address"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "healthcheck.details"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "operator.wallet"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "operator.email"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "healthcheck.enabled"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "contact.external-address"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "operator.wallet-features"}
2026-04-23T20:32:22Z INFO Invalid configuration file key {"process": "storagenode-updater", "key": "storage.allocated-disk-space"}
2026-04-23T20:32:22Z INFO Anonymized tracing enabled {"process": "storagenode-updater"}
2026-04-23T20:32:22Z INFO Running on version {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.5"}
2026-04-23T20:32:22Z INFO Downloading versions. {"process": "storagenode-updater", "server_address": "https://version.storj.io"}
2026-04-23 20:32:23,678 INFO success: processes-exit-eventlistener entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-04-23 20:32:23,679 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-04-23 20:32:23,679 INFO success: storagenode-updater entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-04-23T20:32:35Z INFO Current binary version {"process": "storagenode-updater", "service": "storagenode", "version": "v1.152.5"}
2026-04-23T20:32:35Z INFO Version is up to date {"process": "storagenode-updater", "service": "storagenode"}
2026-04-23T20:32:35Z INFO Current binary version {"process": "storagenode-updater", "service": "storagenode-updater", "version": "v1.152.5"}
2026-04-23T20:32:35Z INFO Version is up to date {"process": "storagenode-updater", "service": "storagenode-updater"}
2026-04-23T20:33:43Z ERROR Total disk space (minus reserved bytes) is less than required minimum {"process": "storagenode", "bytes": 500000000000}
2026-04-23T20:33:49Z 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: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.(*DedicatedDisk).PreFlightCheck:50\n\tstorj.io/storj/storagenode/monitor.NewDedicatedDisk:33\n\tstorj.io/storj/storagenode.New:627\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.(*DedicatedDisk).PreFlightCheck:50
storj.io/storj/storagenode/monitor.NewDedicatedDisk:33
storj.io/storj/storagenode.New:627
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
2026-04-23 20:33:52,527 WARN exited: storagenode (exit status 1; not expected)
2026-04-23 20:33:55,214 INFO spawned: 'storagenode' with pid 59
2026-04-23 20:33:55,215 WARN received SIGQUIT indicating exit request
2026-04-23 20:33:55,320 INFO waiting for processes-exit-eventlistener, storagenode, storagenode-updater to die
2026-04-23T20:33:55Z INFO Got a signal from the OS: "terminated" {"process": "storagenode-updater"}
2026-04-23 20:33:56,784 INFO success: storagenode entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2026-04-23 20:33:56,928 INFO stopped: storagenode-updater (exit status 0)
2026-04-23 20:33:57,931 WARN stopped: storagenode (terminated by SIGTERM)
2026-04-23 20:33:57,939 WARN stopped: processes-exit-eventlistener (terminated by SIGTERM)
2026-04-23 20:35:25,617 INFO Set uid to user 0 succeeded
I think you cannot, IMHO there is bug that node is taking remaining disk space as total capacity. See my other thread. Another of my nodes (4TB disk, so configured as 3.7TB)
df --si
# reports
storj2/data 3.9T 2.2T 1.8T 55% /storj2/data
shows:
I think it match my theory that node use physical free space as declared capacity