[Storage Widget Broken] No longer correctly reports values for NAS like it used to, now only incorrectly provides values for main drive

[crocodilestick]

Description

The Storage Widget has worked perfectly for over a year but since a recent update, it no longer correctly, no longer reporting values for NAS it's pointed to like it used to, now only incorrectly providing values for main drive no matter how deep into the NAS's filesystem I point it.

Other container's like File Browser have no problem reporting the correct values so it's something that was changed in a recent update.

homepage version

v0.9.2 (af16956, Jun 6, 2024)

Installation method

Docker

Configuration

- resources:
    label: Storage
    disk: 
        - /
        - /media/toshiba
        - /media/nas

Container Logs

No response

Browser Logs

No response

Troubleshooting

• Should report the values for the 8TB NAS it's pointed to like it did before but something in a recent update broke it.
• Doesn't matter how deep into the NAS's filesystem I point it
• Other container's like File Browser have no problem reporting the correct values so it's something that was changed in a recent update.

[shamoon]

Feel free to review the commits, nothing changed. I’d re-create (not restart) the container, etc

[faximan]

I think I have the same issue, the Resources storage widget is reporting the wrong values.

compose:

services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    container_name: homepage
    restart: unless-stopped
    environment:
      PUID: 501
      PGID: 20
    ports:
      - 3001:3000
    volumes:
      - ./config:/app/config
      - /Volumes/Zion:/mnt/zion:ro

widgets.yaml:

- resources:
    label: Zion
    expanded: true
    disk: /mnt/zion

Result:

But this drive is 12TB. Inside the homepage container:

df -h | grep zion
mac                      10.9T      5.2T      5.7T  48% /mnt/zion

How is Homepage getting the values for the disk usage?

[crocodilestick]

Yeah this issue has come back fit me with the mist recent update too

…

-------- Original Message --------

On 06/01/2025 20:02, Alex Faxå wrote: I think I have the same issue, the Resources storage widget is reporting the wrong values. compose: services: homepage: image: ghcr.io/gethomepage/homepage:latest container_name: homepage restart: unless-stopped environment: PUID: 501 PGID: 20 ports: - 3001:3000 volumes: - ./config:/app/config - /Volumes/Zion:/mnt/zion:ro widgets.yaml: - resources: label: Zion expanded: true disk: /mnt/zion Result: [Screenshot.2025-01-06.at.19.59.42.png (view on web)](https://github.com/user-attachments/assets/d9c2f06f-14e4-41ab-bbab-1d4ecac8fb2e) But this drive is 12TB. Inside the homepage container: df -h | grep zion mac 10.9T 5.2T 5.7T 48% /mnt/zion How is Homepage getting the values for the disk usage? — Reply to this email directly, [view it on GitHub](#3786 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AZEQ26H2J6W72LXOMJTGCX32JLHMZAVCNFSM6AAAAABLSHWZAKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZVGI3TMMI). You are receiving this because you authored the thread.Message ID: ***@***.***>

[shamoon]

Since the recent updates haven’t changed anything here it has to do with how you’ve set things up.

[faximan]

Since the recent updates haven’t changed anything here it has to do with how you’ve set things up.

I described above how I have set things up. Let me know if you see any problems with this config and/or how I can debug this issue further:

How is Homepage getting the values for the disk usage?

[shamoon]

If you start the container with LOG_LEVEL=debug you’ll get more output in the logs.

This uses a tool called systeminformation, homepage doesn’t do any of the work itself, just reports it

[faximan]

Thanks, this is helpful. From the logs:

[2025-01-07T16:22:47.697Z] debug: <resources> fsSize: [{"fs":"overlay","type":"overlay","size":54405316608,"used":7193886720,"available":47211429888,"use":13.22,"mount":"/","rw":false},{"fs":"mac","type":"virtiofs","size":494384795648,"used":444640301056,"available":49744494592,"use":89.94,"mount":"/app/config","rw":false},{"fs":"/dev/vdb1","type":"btrfs","size":54405316608,"used":7193886720,"available":47211429888,"use":13.22,"mount":"/etc/resolv.conf","rw":true}]

so it seems my mount is not included, which makes it fall back to / here:

homepage/src/pages/api/widgets/resources.js

Lines 29 to 33 in b5f4daa

	const fsSize = await si.fsSize();
	logger.debug("fsSize:", JSON.stringify(fsSize));
	return res.status(200).json({
	drive: fsSize.find((fs) => fs.mount === target) ?? fsSize.find((fs) => fs.mount === "/"),
	});

So this seems indeed to be a problem with systeminformation. I pinged sebhildebrandt/systeminformation#697.

[shamoon]

Oh you reminded me, this might be sebhildebrandt/systeminformation#867