Hi,
I ran into this also, the problem seems to be an inconsistant mdadm.conf.
Check the arrays to make sure that all the identities are correct. like
the UUIDs and Devices.
The key lines in /etc/init.d/mdadm-raid are:
if [ -f $CONFIG ] [ -x $MDADM ] ; then
$MDADM -A
Package: yaird
Version: 0.0.12-3
Severity: normal
I recently recompiled my kernel (linux 2.6.15 instead of 2.6.12) with
a newer kernel-package and the initrd being created by yaird instead
of no initrd at all. When booting this new kernel, the md device
containing the root filesystem is in /dev/,
---BeginMessage---
From [EMAIL PROTECTED] Thu Jan 05 08:34:04 2006
Return-path: [EMAIL PROTECTED]
Received: from 213-84-114-29.adsl.xs4all.nl ([213.84.114.29]
helo=capsaicin.mamane.lu)
by spohr.debian.org with esmtp (Exim 4.50)
id 1EuY3v-000341-Py
for [EMAIL PROTECTED];
that one i have seen -- as i now understand it yaird only
does the root fs -- for debian set the raid script in rcS.d
it will start the other md devices On 1/5/06, Lionel Elie Mamane [EMAIL PROTECTED] wrote:
___Yaird-devel mailing list[EMAIL PROTECTED]
On Thu, Jan 05, 2006 at 11:41:30AM -0600, RobRoy Kelly wrote:
that one i have seen -- as i now understand it yaird only
does the root fs -- for debian set the raid script in rcS.d
it will start the other md devices
Well, the debconf config says to do that only if the md drivers are
compiled as
5 matches
Mail list logo
