This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] domU -->Failure: failed to start /dev/md1

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] domU -->Failure: failed to start /dev/md1
From: Frank <josephbeuys@xxxxxx>
Date: Sat, 01 Sep 2007 23:18:00 +0200
Delivery-date: Sat, 01 Sep 2007 14:14:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <46D9D0DA.2080709@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <46D9B37F.60502@xxxxxx> <20070901192108.GV18805@xxxxxxxxxxx> <46D9D0DA.2080709@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Macintosh/20070728)

Nico Kadel-Garcia schrieb:
Andy Smith wrote:
On Sat, Sep 01, 2007 at 08:46:23PM +0200, Frank wrote:
I don't understand this boot error from the domU:

Begin: Assembling MD array /dev/md1 ...
md: md1 stopped.
mdadm: no devices found for /dev/md1
Failure: failed to start /dev/md1

Why does your domU try to assemble a software RAID at all if..

disk = [ 'file:/vd/domains/xen-etch/disk.img,sda1,w', file:/vd/domains/xen-etch/swap.img,sda2,w' ]

..it only has one block device?

Is this a showstopper for you or does it carry on to boot normally?

Do you have an /etc/mdadm/mdadm.conf in the domU?

Does your domU have mdadm set to run and assemble arrays?

Is there *ANY* reason to do software RAID, LVM, or other filesystem cuteness in a DomU? Except maybe for configuration testing purposes? Let the Dom0 do the work, I'm quite certain it will be more efficient about it.

No there is no reason and I don't want, need and understand not why I get this error. I'm not trying to use software raid in a domU. That woult be funy as this strange error I get. Software raid is only used in dom0, only there!

My question is: Why I get this error in the domU if I don't use software raid in the domU and how can I get rid off this errors?

Xen-users mailing list