On 02/01/2021 22:12, Rudy Zijlstra wrote:
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.
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.
Nope, it is not redundant. It tells the init system that your UUID is on
a raid device, which means it has to wait for the raid devices to be
online. Without mdadm.conf it cannot know this.
So it just waits until that UUID appears ...
Dunno whether my system is configured with UUID or device name, but root
is on an array, and there's no mdadm.conf. Works fine ...
That's why the suggestion is "use eg /dev/md/root".
I'm with the OP. You don't need an mdadm.conf, so don't bother with it.
Cheers,
Wol
