On systems that are set up statically mdadm.conf is often used to list the md devices that should be set up and the startup script just calls mdadm --assemble --scan.
But on systems oriented towards hotplug ability this prevents arrays from being assembled by the hotplug system.
Ubuntu has switched to set up complete (non-degraded) arrays automatically with udev rules. But any ARRAY line in mdadm.conf created during (package) installation prevents the hotplugging to work with other arrays.
As only complete (non-degraded) arrays are run automatically the automatic assembly will leave partial arrays that may be plugged in untouched, thus the system shoud be save even without the ARRAY restriction.
(The --no-degraded and --increamental options have been implemented with this hotplugging in mind.)
The ARRAY lines should not be created on udev+mdadm systems.
Binary package hint: debian-installer
On systems that are set up statically mdadm.conf is often used to list the md devices that should be set up and the startup script just calls mdadm --assemble --scan.
But on systems oriented towards hotplug ability this prevents arrays from being assembled by the hotplug system.
Ubuntu has switched to set up complete (non-degraded) arrays automatically with udev rules. But any ARRAY line in mdadm.conf created during (package) installation prevents the hotplugging to work with other arrays.
As only complete (non-degraded) arrays are run automatically the automatic assembly will leave partial arrays that may be plugged in untouched, thus the system shoud be save even without the ARRAY restriction.
(The --no-degraded and --increamental options have been implemented with this hotplugging in mind.)
The ARRAY lines should not be created on udev+mdadm systems.