Great, the Contributing to Rockstor documentation section of the docs should be useful on this one.
the additional command requirement may just be down to upstream changes in the installer as since that doc was written we have inherited changes after rebasing on a newer version of CentOS for our iso. Our installer is essentially a re-branded CentOS installer and we have made no other changes that I can see would have affected this auto start of mdraid or not behaviour. But we do have that label issue which should be fixed so it’s possible that could be upsetting something. You could add a small note on the label issue if that was what you were thinking, ie point to the GitHub issue as then once it is resolved then it would be noted as such in the issue itself.
No, that additional command is harmless so might as well just pop it in.
That is not my experience having just gone through the install as per the howto but with our discovered caveats; ie the label change (bug work around) to use the rescue system and the additional command once in there to activate the mdraid arrays (suspected changes upstream on defaults). There after I was able to follow the directions as written there after and the install completed successfully.
Could it be that you have forgotten to tick the “reformat” where indicated?
It’s a pretty round about way to do things but it allows us to circumvent the installers inability to do this install without a ‘double take’ approach such as the howto details.
It’s getting late here so I’ve got to dash but I would say that although my install went as described the first boot resulted in an emergency mode so we are not there yet. Looks on quick inspection to be some issue with the /home subvolume:
BTRFS error (device md125): subvol 'home' does not match subvolid 5
Oh well, I thought we had nailed this one. I’ll try and put some more time into this to see if it’s still possible to install this way. Otherwise it might be that we have to wait until the next iso is rolled out and see how it goes with that one.
Hope that helps and let us know if you run into this and manage to sort it. I may have missed something myself or it may just be an artefact of me having to break off during the install process earlier and then restart it. I’ll update if / when I find out.
Otherwise you options are to try installing using the 3.9.0 iso where this method presumably still works and then update once installed.