pdoroba

It took over 24 hours to run the extended SMART test. It completed without errors. I'll report back as I make progress. Thanks!

As requested. Thanks! seshat-diagnostics-20260614-1722.zip

Any idea how to fix this then? Disk 3 is showing as disabled. When i hover over the red X a pop up message states "Device is Disabled, Contents Emulated." I can't re-enable the disk and the SMART test returns no errors. Thanks!

Hi all, I have a disabled data disk (Disk 3) that I cannot re-enable due to a ghost Parity 2 slot (slot 29) in my superblock keeping mdNumDisabled=2. The UI never offers a Recover or Re-enable option because of this. System: Unraid 7.3.1 LSI SAS2008 HBA (new replacement) 4x Seagate Exos X20 20TB in array (BTRFS) Disk 3 serial: ST20000NM007D-3DJ103_ZVT64229 The problem: Disk 3 went disabled after what appears to have been a backplane connection issue. SMART on Disk 3 is completely clean — no reallocated sectors, no pending sectors, no uncorrectable errors. The filesystem is intact and mounted. However there is a ghost Parity 2 slot (slot 29 internally) that is permanently stuck as DISK_NP_DSBL. This keeps mdNumDisabled=2, which prevents Unraid from offering any re-enable or rebuild option for Disk 3. Diagnostics: mdState=STARTED mdNumDisabled=2 rdevStatus.3=DISK_DSBL diskState.29=4 rdevStatus.29=DISK_NP_DSBL Superblock has diskState.29=4 at byte offset 3852. What I've tried: New SAS cables New HBA Editing disk.cfg to remove slot 29 entries (reverts on boot) Writing remove 29 to /proc/mdcmd — returns "Invalid argument" whether array is started or stopped Patching superblock byte offset 3852 from 0x04 to 0x00 — cleared all disk assignments unexpectedly, restored from backup Maintenance mode — /proc/mdcmd still rejects writes Unraid updated from 7.2.3 to 7.3.1 during troubleshooting — no change Questions: Is there a supported way to clear a ghost disabled Parity 2 slot from the superblock? Is there a tool or procedure to force-clear slot 29 and drop mdNumDisabled to 1? Why does /proc/mdcmd reject all writes even with the array stopped? Data is intact and array is running degraded. No urgency but need a path forward. Thanks!