All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Christoph Pleger <Christoph.Pleger@cs.tu-dortmund.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Setting up fakeraid with mdadm / dmraid
Date: Mon, 11 Apr 2016 11:33:41 -0400	[thread overview]
Message-ID: <wrfjk2k4ma7e.fsf@redhat.com> (raw)
In-Reply-To: <b6ced30ee931f9a6faf2541db2462401.squirrel@postweb.cs.tu-dortmund.de> (Christoph Pleger's message of "Tue, 5 Apr 2016 15:03:12 +0200")

"Christoph Pleger" <Christoph.Pleger@cs.tu-dortmund.de> writes:
> Hello,
>
> I have a machine with an LSI Megaraid Sofware RAID fakeraid, which uses
> ddf format. About two weeks ago, when I wanted to install the machine, I
> configured a RAID 1 array in the BIOS config utility and then booted the
> machine from PXE with an NFSROOT. mdadm and dmraid are installed in the
> NFSROOT, dracut is used for initrd generation. As dracut prefers mdadm
> over dmraid, mdadm was chosen for RAID management.
>
> But though mdadm detected the RAID (it created container device /dev/md127
> and raid device /dev/md126), it destroyed it - that is, though I did not
> perform any action on the raid disks, at the next boot, the BIOS RAID
> utility had "forgotten" about the RAID configuration it had created
> before.
>
> Why are the possible reasons for that?

The LSI uses DDF and requires mdmon etc. to be launched. It is not clear
from your posting what you created, but you would have to update dracut
to include mdmon etc. after creating the RAID.

Jes

  parent reply	other threads:[~2016-04-11 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 13:03 Setting up fakeraid with mdadm / dmraid Christoph Pleger
2016-04-05 13:58 ` John Stoffel
2016-04-11 15:33 ` Jes Sorensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-05 15:43 Christoph Pleger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=wrfjk2k4ma7e.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=Christoph.Pleger@cs.tu-dortmund.de \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.