-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve mdraid content re re-deployed prior mdraid drives #140
Comments
I have something mostly written for this along with supporting images. Will try and submit during my next docs session. |
Please also update the following forum thread with progress on this issue: |
Linking to another forum thread where this came up again recently: |
Linking to another more recent forum post by HarryHUK who shared another 'work around' for this same re-deploying (read wiping) mdraid members issue: https://forum.rockstor.com/t/cant-add-disks-to-pool-or-reformat-solved/7440 |
Our more recent updates to the PBP via: Add in a primordial mention of mdraid artefacts to our PBP. But not with the details given here. It is proposed that we move this new PBP mdraid and wipefs content in PBP to a dedicated caveat section of regular disk wiping within: |
Thanks to @elmcrest in the following forum thread for influencing this issue creation:
https://forum.rockstor.com/t/solved-disks-failing-with-badge-disk-is-a-mdraid-member/1210/12?u=phillxnet
Now we have the 'advanced' mdraid system disk howto we need to clarify that this mdraid capability is only supported for the system drive and offer up a howto on re-purposing mdraid members as Rockstor btrfs data drives. Ie detail the commands required to erase mdraid member status inherited from previous NAS deployments. ie
BIG WARNING THAT ALL DATA WILL BE LOST PERMANENTLY
and then (for example):
And finally a 'Rescan' in disk page to refresh Rockstor's knowledge of the devices mdraid member status change. This Rescan mdraid member status change is functional as of 3.8-13.11, via pr:
rockstor/rockstor-core#1314
Some initial investigation of the mdX device name may also be required, ie
The text was updated successfully, but these errors were encountered: