Bug#350861: [Yaird-devel] Bug#350861: yaird: Degraded RAID 1 array
fails to boot
sjackman at gmail.com
Wed Feb 1 18:19:18 UTC 2006
On 2/1/06, Jonas Smedegaard <dr at jones.dk> wrote:
> I believe including broken disks will then fail to boot the degraded
> system (if not including --run). See bug#350710.
> Upstream dislikes including config files with the initrd. As I
> understand it for the reason that the initrd should then probably be
> rebuild whenever the original config file is changed.
I agree with not including the mdadm.conf in the initrd. When the
initrd is built though, I'd check that the mdadm configuration stored
in the root disk's /init, which is tantamount to a config file, should
be checked against the host's mdadm.conf to ensure they match. If they
don't, I'd suggest yaird should fail. The user can then fix one or the
> Why do including --add require more discussion? What is the drawbacks?
(assuming you meant --run here) Primarily because it looks like a
--force option, which to me suggests the author was thinking, "This
may cause some damage, so make sure the user knows what he's doing."
I'd check with the mdadm author what he thinks of adding --run to
> thanks for the help with this.
No worries. Cheers,
More information about the Yaird-devel