Storj node take much more space in my hdd than in the node deashboard what is the probleme

storj node take much more space in my hdd than in the node deashboard what is the probleme exmp
for 55 gb ihave in my 300 gb space used

Can you show screenshots?

looks like you have been DQ-ed on 1-2 sattelites, so this data is staid, but dashboard do not use tham any more

1 Like

it do it for me the secend time without disqualification

Filesystem Type Size Used Avail Use% Mounted on
none tmpfs 2.1G 4.1k 2.1G 1% /mnt/wsl
drivers 9p 499G 258G 242G 52% /usr/lib/wsl/drivers
none tmpfs 2.1G 0 2.1G 0% /usr/lib/modules
none overlay 2.1G 0 2.1G 0% /usr/lib/modules/5.15.153.1-microsoft-standard-WSL2
/dev/sdh ext4 1.1T 4.8G 1.1T 1% /
none tmpfs 2.1G 82k 2.1G 1% /mnt/wslg
none overlay 2.1G 0 2.1G 0% /usr/lib/wsl/lib
rootfs rootfs 2.1G 2.2M 2.1G 1% /init
none tmpfs 2.1G 824k 2.1G 1% /run
none tmpfs 2.1G 0 2.1G 0% /run/lock
none tmpfs 2.1G 0 2.1G 0% /run/shm
tmpfs tmpfs 4.2M 0 4.2M 0% /sys/fs/cgroup
none overlay 2.1G 78k 2.1G 1% /mnt/wslg/versions.txt
none overlay 2.1G 78k 2.1G 1% /mnt/wslg/doc
C:\ 9p 499G 258G 242G 52% /mnt/c
D:\ 9p 2.1T 251G 1.8T 13% /mnt/d
E:\ 9p 1.1T 136G 865G 14% /mnt/e
F:\ 9p 501G 500G 989M 100% /mnt/f
snapfuse fuse.snapfuse 132k 132k 0 100% /snap/hello/42
snapfuse fuse.snapfuse 41M 41M 0 100% /snap/snapd/21759
snapfuse fuse.snapfuse 68M 68M 0 100% /snap/core20/2379
tmpfs tmpfs 412M 17k 412M 1% /run/user/1000
tmpfs tmpfs 412M 17k 412M 1% /run/user/0
none tmpfs 2.1G 8.2k 2.1G 1% /mnt/wsl/docker-desktop/shared-sockets/host-services
/dev/sdc ext4 1.1T 60M 1.1T 1% /mnt/wsl/docker-desktop/docker-desktop-user-distro
/dev/loop0 iso9660 486M 486M 0 100% /mnt/wsl/docker-desktop/cli-tools
none tmpfs 2.1G 861k 2.1G 1% /mnt/wsl/docker-desktop-bind-mounts/Ubuntu-20.04/71329c4cc6e32171553fa81d044eb31d1a3aac52ba9376c4a99f4505c494cf5b
C:\Program Files\Docker\Docker\resources 9p 499G 258G 242G 52% /Docker/host
none tmpfs 2.1G 4.1k 2.1G 1% /mnt/wsl/docker-desktop-bind-mounts/Debian/71329c4cc6e32171553fa81d044eb31d1a3aac52ba9376c4a99f4505c494cf5b
none tmpfs 2.1G 4.1k 2.1G 1% /mnt/wsl/docker-desktop-bind-mounts/kali-linux/71329c4cc6e32171553fa81d044eb31d1a3aac52ba9376c4a99f4505c494cf5b

Your node has been offline for 15% of the measured time (as measured by two satellites). You had computer turned off or no internet?

i had 00x daemon problem

Hello @xgDkAbzkp9yi,
Welcome to the forum!

You need to remove the data of satellites, which disqualified your node to free up some space.
You may use this guide:

Just use it for the satellites which will never talk with your node, and do not forget to apply a --force flag to remove their data too.
It would be useful if you will figure out, why your node is DQ on them though:

2024-10-16T11:02:35Z FATAL Failed to load identity. {“Process”: “storagenode”, “error”: “file or directory not found: open C:\Users\guesmi\Desktop\3/identity.cert: no such file or directory”, “errorVerbose”: “file or directory not found: open C:\Users\guesmi\Desktop\3/identity.cert: no such file or directory\n\tstorj.io/common/identity.Config.Load:326\n\tmain.cmdForgetSatellite:133\n\tmain.newForgetSatelliteCmd.func1:88\n\tstorj.io/common/process.cleanup.func1.4:392\n\tstorj.io/common/process.cleanup.func1:410\n\tgithub.com/spf13/cobra.(*Command).execute:983\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:1115\n\tgithub.com/spf13/cobra.(*Command).Execute:1039\n\tstorj.io/common/process.ExecWithCustomOptions:112\n\tmain.main:34\n\truntime.main:271”}
ihave this eroor

The storagenode CLI (versions from 1.88.0) provides a forget-satellite subcommand to remove satellites from the trust cache and clean up the available data.

If you use a Windows GUI, then you need to change the owner for that location, if it’s exist to the SYSTEM user. You may do so, but you wouldn’t be able to open this folder under your user, only as an Administrator.
So I would recommend to copy the identity folder to the data location instead and use that path instead of C:\Users\guesmi\Desktop\3 in your config.yaml using the Notepad++ text editor, save the config and restart the node.