[BUG] MDADM collector returns devices: null, causing frontend crash on RAID Arrays page #652

Describe the bug

Collector version: 1.66.0

• Collector version: 1.66.0
• The API response you got from /api/mdadm/summary (the JSON with devices: null for all 3 arrays)
• The console error: TypeError: Cannot read properties of null (reading 'length') at se (chunk-RFPO5FLL.js...)
• Your setup: 3 mdadm arrays (raid1, raid1, raid6), omnibus + separate collector-mdadm sidecar container

Expected behavior

• Each array card (md0, md1, md2) should render fully, not just the first one in the list
• The devices field returned by /api/mdadm/summary should contain the list of member block devices for each array (e.g. sde2, sdc2, sdg2, sdf2 for md1, per cat /proc/mdstat), not null
• A missing/null devices field shouldn't crash the frontend rendering pipeline for that card or any subsequent cards in the list — at minimum it should degrade gracefully (e.g. show the array with an empty device list or a "device info unavailable" note) rather than throwing an uncaught TypeError that halts rendering of later items

Screenshots

Log Files

Environment

No response