This isn't a yaird bug, it's actually a bug with "mdadm". It is failing
to start a mirror with a drive missing. (mdadm is an entire major
revision behind Debian current -- this bug has been long-since fixed
in upstream mdadm.)
The silly behavior from yaird is that it drops to a shell if a dev
> > On 2/1/06, Jonas Smedegaard <[EMAIL PROTECTED]> wrote:
> > 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 agains
On Wed, 1 Feb 2006 11:19:18 -0700
Shaun Jackman <[EMAIL PROTECTED]> wrote:
> On 2/1/06, Jonas Smedegaard <[EMAIL PROTECTED]> wrote:
> > I believe including broken disks will then fail to boot the degraded
> > system (if not including --run). See bug#350710.
> >
> > Upstream dislikes including conf
On 2/1/06, Jonas Smedegaard <[EMAIL PROTECTED]> 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 t
On Tue, 31 Jan 2006 23:13:55 -0700
Shaun Jackman <[EMAIL PROTECTED]> wrote:
> If yaird is run while the root partition, a RAID 1 array, is in a
> degraded state, the system will not boot if the array is ever restored
> to a complete state.
>
> I installed a new kernel (linux-image-2.6.15-1-k7). I
5 matches
Mail list logo
