Storage showing local only

[oOStroudyOo]

Hello,

I've got 2 network storage devices set up in the widgets, this has always worked fine until I updated the application yesterday. It now only shows the local storage capacity of the container and not the NAS drives.

I've not changed any of the YAML files, it just simply stopped working after the update but unfortunately I didn't take note of what version I was previously running.

My homepage application is running on a Linux (Debian) container via Proxmox and it's built from source.

The container can see, and access the NAS drives:

The widgets.yaml config is set as:

But the homepage shows local container storage which I've set as 3GB:

Does anybody have any suggestions to get it to display the correct storage capactity please?
Like I said, it worked before I updated the application yesterday, I've even uninstalled and reinstalled.
I've been through the changelog and not seen any obvious changes to the application that would affect it.

Thank you.

[Rufmord]

Same problem here.
df inside the container shows right values and the path in Mounted on is the path I wrote in the widgets.yaml. It is only showing the main storage where the system is running.

[punksinatra]

Not sure if you have fixed this you have to mount the volume from the host to docker

something like this

volumes:
- /path/to/volume/Dockers/homepage/config:/app/config # Make sure your local config directory exists
- /path/to/volume//Dockers/homepage/icons:/app/public/icons/
- /media/nas4tb:/mnt/nas4tb # mount volume as mount to show disk info
- /media/nas6tb:/mnt/nas6tb # mount volume as mount to show disk info

Then on your resources you should have something like this

disk:
- /
- /mnt/nas4tb
- /mnt/nas6tb

[Rufmord]

I know and I followed the manual. Problem is, that it sometimes works and shows the correct space and sometimes not with no changes on the compose file.

[oOStroudyOo]

Since this post, I moved homepage into Docker and not had any issues since.

[crispybegs]

Not sure if you have fixed this you have to mount the volume from the host to docker

something like this

volumes:

• /path/to/volume/Dockers/homepage/config:/app/config # Make sure your local config directory exists
• /path/to/volume//Dockers/homepage/icons:/app/public/icons/
• /media/nas4tb:/mnt/nas4tb # mount volume as mount to show disk info
• /media/nas6tb:/mnt/nas6tb # mount volume as mount to show disk info

Then on your resources you should have something like this

disk:

• /
• /mnt/nas4tb
• /mnt/nas6tb

i'm really struggling with this

I have two disks on the same box on which homepage is running

lsblk lists them as

sdb      8:16   0   3.6T  0 disk
└─sdb1   8:17   0   3.6T  0 part /media/crispy/NAS_4TB_1
sdc      8:32   0   3.6T  0 disk
└─sdc1   8:33   0   3.6T  0 part /media/crispy/NAS_4TB_2

i've mapped them in my homepage compose as

    volumes:
      - /home/crispy/docker/homepage/config:/app/config
      - /var/run/docker.sock:/var/run/docker.sock:ro 
      - /media/crispy/NAS_4TB_1:/mnt/NAS_4TB_1
      - /media/crispy/NAS_4TB_1:/mnt/NAS_4TB_2

my homepage config is

    disk:
      - /etc/hosts
      - /mnt/NAS_4TB_1
      - /mnt/NAS_4TB_2

yet nothing shows up in the widget

I've tried the same thing with

/dev/sdb1 & /dev/sdc1

and

/dev/sdb & /dev/sdc

but literally nothing makes a difference and nothing shows up in the widget.
What am I getting wrong here?

[oOStroudyOo]

If you're using a NAS and docker, try something like this in your docker compose:
If your NAS doesn't require credentials to access, then you could probably miss the o: in the Volumes section.

[punksinatra]

@crispybegs

Are you using docker?

Are the mounts showing up inside the container? Go inside the container and check inside /mnt if NAS_4TB_1 and NAS_4TB_2 shows up

[crispybegs]

@crispybegs

Are you using docker?

Are the mounts showing up inside the container? Go inside the container and check inside /mnt if NAS_4TB_1 and NAS_4TB_2 shows up

yep, they are..

[oOStroudyOo]

This is the full setup I have to get my NAS drives to appear on Homepage:

docker-compose.yml

widgets.yaml

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.