Wrong disk in resources widget

[nerdlich]

Description

Pretty much every time after the homepage container gets recreated or even just restarted, the disk usage for the disk "Data" displays the information of the disk "/". After another 5-10 manual restarts of the container, finally the data for the correct disk is displayed. It only ever affects the "Data" disk, "/" and "Backup" are always correct.

Host fstab:

/dev/disk/by-id/dm-uuid-LVM-5edeTc8Tfgb0yYWlKtLKCt24m8rOWEdM7jb1UZOhpQoLXCGSyyMfbzOVGfMURqvN / ext4 defaults 0 1
/dev/disk/by-uuid/0081bc19-69d2-43d5-b4f2-6705add11cf9 /srv/docker	ext4	defaults	0	0
/dev/disk/by-uuid/d1e193b9-8b26-4d7d-b8b7-f8e691b53be6 /srv/backup	ext4	defaults	0	0

docker-compose.yml:

  homepage:
    volumes:
      - ./homepage:/app/config
      - /srv/docker:/srv/docker:ro
      - /srv/backup:/srv/backup:ro

widgets.yaml:

- resources:
    label: System
    expanded: true
    cpu: true
    memory: true
    disk: /
- resources:
    label: Data
    expanded: true
    disk: /srv/docker
- resources:
    label: Backup
    expanded: true
    disk: /srv/backup

homepage version

v0.10.1

Installation method

Docker

Configuration

No response

Container Logs

No response

Browser Logs

No response

Troubleshooting

Tried to remove "/" disk, change order of disks, it's always "Data" that displays info of "/".

[shamoon]

Sounds like a docker issue not a homepage one, as in for some reason docker issue not picking up that bind mount. I assume when you first run it (and the data drive isn’t working) running df inside the container would illustrate this

[nerdlich]

Negative, df is correct:

# docker exec homepage df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  61.2G     45.9G     12.1G  79% /
tmpfs                    64.0M         0     64.0M   0% /dev
shm                      64.0M         0     64.0M   0% /dev/shm
/dev/sda2                12.6T      2.3T      9.7T  19% /app/config
/dev/sda2                12.6T      2.3T      9.7T  19% /srv/docker
/dev/sdb2                12.6T      2.3T      9.7T  20% /srv/backup

Happy to debug further if you tell me how.

[shamoon]

I assume you've tried basic stuff like re-creating the container (down then up)?

If you run the container with LOG_LEVEL=debug you will see some output related to this widget which you can post here (it would be helpful to see the output when the disk isn't showing and when it is). In general, homepage basically just directly pipes the response from https://systeminformation.io so if theres an issue my guess is it's there.

[nerdlich]

Debug fsSize:

  {
    "fs": "overlay",
    "type": "overlay",
    "size": 65703391232,
    "used": 49406234624,
    "available": 12926406656,
    "use": 79.26,
    "mount": "/",
    "rw": false
  },
  {
    "fs": "/dev/sdb2",
    "type": "ext4",
    "size": 13888768679936,
    "used": 2574198534144,
    "available": 10614539550720,
    "use": 19.52,
    "mount": "/srv/backup",
    "rw": false
  },
  {
    "fs": "/dev/sda2",
    "type": "ext4",
    "size": 13888768679936,
    "used": 2555200466944,
    "available": 10633537617920,
    "use": 19.37,
    "mount": "/app/config",
    "rw": false
  },
  {
    "fs": "/dev/mapper/ubuntu--vg-ubuntu--lv",
    "type": "ext4",
    "size": 65703391232,
    "used": 49406234624,
    "available": 12926406656,
    "use": 79.26,
    "mount": "/etc/resolv.conf",
    "rw": true
  }
]```

The disk appears, but with the wrong mount point.

[nerdlich]

Seems like it's an ordering issue when parsing df output in systeminformation. When I see wrong data, /app/config appears before /srv/docker in df. When it's correct, /srv/docker comes first. I agree, this is an issue in systeminformation, not homepage.

As a workaround, I changed docker-compose to list my external disks first, before the config bind mount that seems to trip up systeminformation:

      - /srv/docker:/srv/docker:ro
      - /srv/backup:/srv/backup:ro
      - ./homepage:/app/config

Now, after 10 restarts it was correct every time... Thanks for pointing me in the right direction.

[shamoon]

Interesting. The si project is pretty actively developed if you’re interested in opening a discussion there. Either way, thanks for reporting back

[nerdlich]

Possibly related to this: sebhildebrandt/systeminformation#867

[shamoon]

Ha, been open for a year so goes against what I said but Im sure that's the same issue, yea. Thanks (I forgot about that, Im already subscribed implying someone else pointed it out from here)

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. 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.