Skip to content
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

Open
phillxnet opened this issue May 20, 2016 · 5 comments
Open

improve mdraid content re re-deployed prior mdraid drives #140

phillxnet opened this issue May 20, 2016 · 5 comments

Comments

@phillxnet
Copy link
Member

phillxnet commented May 20, 2016

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):

yum install mdadm
mdadm --stop /dev/md0
mdadm --zero-superblock /dev/vdb
mdadm --zero-superblock /dev/vdc

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

cat /proc/mdstat
@phillxnet
Copy link
Member Author

I have something mostly written for this along with supporting images. Will try and submit during my next docs session.

@phillxnet
Copy link
Member Author

Please also update the following forum thread with progress on this issue:
https://forum.rockstor.com/t/smart-value-don-t-show-at-webinterface/2539/3

@phillxnet
Copy link
Member Author

Linking to another forum thread where this came up again recently:
https://forum.rockstor.com/t/unable-to-add-disk/6458

@phillxnet
Copy link
Member Author

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

@phillxnet
Copy link
Member Author

phillxnet commented Aug 29, 2022

Our more recent updates to the PBP via:
update Pre-Install Best Practice (PBP) #379 #395

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:
http://build.lan/docs/interface/storage/disks.html "Wiping a Partition or Whole Disk".
And we maintain a minimal reference to this in our PBP so as to provide a dual access to this caveat info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant