@elmcrest and @Spectre694 Just reporting back that as of Rockstor 3.8-13.11 (testing channel updates) the issue I opened as a result of this thread, mdraid member status not updated, has now been closed. So from this version on, assuming all goes well, the disk page should now correctly update any mdraid member status changes to drives visible to Rockstor.
Thanks again for reporting this and although I know you were able to resolve this by ‘brute force’ re-install I realized when looking into the issue that simply disconnecting the drive after wiping it’s mdraid member status as you did, and hitting ‘Rescan’ on the disks page, then removing the ‘missing’ drive entry via the bin icon before re-attaching the drive would also have resulted in a quicker work around. Alas we now have in place a proper update for mdraid membership changes.
@elmcrest I have also opened a new issue in the rockstor-doc repo to address your docs suggestion. The issue is entitled “improve mdraid content re re-deployed prior mdraid drives” and links back to your last post in this thread for context.
Bit by bit.