Skip to content

[BUG] MDADM RAID view is still ungrouped by host #640

Closed

Description

@zipcube

Describe the bug

on release 1.65.0 (master#c38d06f) the mdadm tab still shows every mdadm array in a list rather than under host name group headings

see: [feature/579]](#579)

Expected behavior

expected behavior is layout similar to other tabs (zfs, workload, smart) where objects are group by host

Screenshots

Image

Log Files

Environment

Client:
 Version:    29.6.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  0.35.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  5.1.4
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 31
  Running: 30
  Paused: 0
  Stopped: 1
 Images: 53
 Server Version: 29.6.0
 Storage Driver: zfs
  Zpool: workpool
  Zpool Health: ONLINE
  Parent Dataset: workpool/dockersys
  Space Used By Parent: 62465466368
  Space Available: 67654430720
  Parent Quota: no
  Compression: on
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /run/cdi
 Discovered Devices:
  cdi: nvidia.com/gpu=0
  cdi: nvidia.com/gpu=GPU-c237c2c8-0008-9bc8-c04d-df135828fddd
  cdi: nvidia.com/gpu=all
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 nvidia runc
 Default Runtime: runc
 Init Binary: /usr/bin/tini-static
 containerd version: 1.fc44
 runc version:
 init version:
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 7.0.14-201.fc44.x86_64
 Operating System: Fedora Linux 44 (Server Edition)
 OSType: linux
 Architecture: x86_64
 CPUs: 32
 Total Memory: 188.8GiB
 Name: darwin
 ID: c47d303b-9919-439f-95a4-92132fd7ec0d
 Docker Root Dir: /workpool/dockersys
 Debug Mode: false
 Username: redacted
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Live Restore Enabled: false
 Firewall Backend: nftables
  EnableUserlandProxy: true
  UserlandProxyPath: /usr/bin/docker-proxy

Activity

  1. moved this to Bug Backlog in Release Scheduleon Jul 2, 2026
  2. Starosdev commented on Jul 8, 2026

    @Starosdev
    Owner

    @zipcube the MDADM host-grouping fix for #640 is now in develop and deployed in our development environment. When you have a chance, please pull the latest develop image and check whether the MDADM RAID page is now grouping arrays under host headings as expected in your multi-host setup. If it still looks wrong, a screenshot of /web/mdadm and a sample /api/mdadm/summary response would help narrow it down quickly.

  3. zipcube commented on Jul 11, 2026

    @zipcube
    Author

    Issue persists in develop, see attached screenshot and api output:

    Image

    { "data": [ { "uuid": "e695673f:13bd154e:5ecff648:ef675a78", "name": "md0", "level": "raid1", "devices": [ "/dev/sda2" ], "archived": false, "muted": false, "state": "clean, degraded", "array_size": 2009071616 }, { "uuid": "04f6f66c:e0c0c92b:c1dd791f:64b3d4e1", "name": "md3", "level": "raid1", "devices": [ "/dev/sda5" ], "archived": false, "muted": false, "state": "clean, degraded", "array_size": 15992171266048, "used_bytes": 11014506856448 }, { "uuid": "ebed2cc5:8a8be0b9:d0e0a759:582cca14", "name": "md127", "level": "raid10", "devices": [ "/dev/sda2", "/dev/sdb2", "/dev/sdc2", "/dev/sdd2" ], "archived": false, "muted": false }, { "uuid": "9635b9e4:a137caeb:3175027e:1bf13b4f", "name": "md126", "level": "raid10", "devices": [ "/dev/sda1", "/dev/sdb1", "/dev/sdc1", "/dev/sdd1" ], "archived": false, "muted": false }, { "uuid": "2b904abd:23c0b613:b6975ee8:4396f09d", "name": "md127", "level": "raid0", "devices": [ "/dev/sda3", "/dev/sdb1", "/dev/sdc1", "/dev/sdd1" ], "archived": false, "muted": false, "state": "clean", "array_size": 1012437876736 } ], "success": true }

  4. zipcube commented on Jul 11, 2026

    @zipcube
    Author

    update, develop branch works after i force run a new collection on the associated hosts, see attached output and screenshot:

    Image

    {"data":[{"uuid":"e695673f:13bd154e:5ecff648:ef675a78","name":"md0","level":"raid1","devices":["/dev/sda2"],"archived":false,"muted":false,"host_id":"unifi","state":"clean, degraded","array_size":2009071616},{"uuid":"04f6f66c:e0c0c92b:c1dd791f:64b3d4e1","name":"md3","level":"raid1","devices":["/dev/sda5"],"archived":false,"muted":false,"host_id":"unifi","state":"clean, degraded","array_size":15992171266048,"used_bytes":11018795544576},{"uuid":"ebed2cc5:8a8be0b9:d0e0a759:582cca14","name":"md127","level":"raid10","devices":["/dev/sda2","/dev/sdb2","/dev/sdc2","/dev/sdd2"],"archived":false,"muted":false,"host_id":"kepler","state":"clean","array_size":997664489472},{"uuid":"9635b9e4:a137caeb:3175027e:1bf13b4f","name":"md126","level":"raid10","devices":["/dev/sda1","/dev/sdb1","/dev/sdc1","/dev/sdd1"],"archived":false,"muted":false,"host_id":"kepler","state":"clean","array_size":1995440128,"used_bytes":508436480},{"uuid":"2b904abd:23c0b613:b6975ee8:4396f09d","name":"md127","level":"raid0","devices":["/dev/sda3","/dev/sdb1","/dev/sdc1","/dev/sdd1"],"archived":false,"muted":false,"state":"clean","array_size":1012437876736}],"success":true}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions