On 02/01/21 15:39, c.buhtz@xxxxxxxxx wrote: > Thanks to you and all other answers. It helped me a lot to understand > the backgrounds. > > On 2021-01-01 14:09 Phil Turmel <philip@xxxxxxxxxx> wrote: >> I recommend creating an mdadm.conf file containing ARRAY entries for >> your desired setup. Trim those lines to only have the desired name >> and UUID. > > Maybe I should open a new thread for that topic? > Please correct me, because I am not an usual admin nor an mdadm expert. > > I do not want to convince you with the following! I just want to bring > up my point of view and my opinion to make it possible for you experts > to "correct" me. ;) > > I do not see the advantage of creating mdadm.conf. > Via fstab I mount the devices by their UUID. > And all other information's mdadm needs to use the RAID is stored in the > superblock. As the guy who looks after the wiki, none of my systems (to my best knowledge) have or have had an mdadm.conf. There's supposed to be a way to create it automagically from the current running config, but I've never managed to get to grips with it ... > > So information's in mdadm.conf would be redundant. And especially for > a non-routine home-admin like me each conf-file I modify keep the > possibility of misstakes/missconfigurations and more problems. Keeping > it as simple as possible is very important for my environment. > >> Once you are sure it works, I also recommend adding AUTO=-all to >> mdadm.conf, so any extra arrays you might plug in temporarily won't >> auto-assemble if still plugged in during boot. > > I do not understand this. What does "auto-assemble" means? You mean if > I plug in a SDD/HDD with a mdadm-created superblock? > It's what happens when a system boots - as each drive is recognised, it's added to an array until the array has enough drives to function. In other words, rather than doing an mdadm assemble command with all the drives, it's doing an assemble with just one drive at a time saying "add to the relevant array". If you've disabled auto-assemble, presumably you do need mdadm.conf to tell mdadm what to assemble, which presumably also means you can't have root on a raid because boot needs the array to find mdadm.conf in order to start the array ... Don't quote me on that ... Cheers, Wol
