linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bs@q-leap.de>
To: thomas62186218@aol.com
Cc: linux-raid@vger.kernel.org
Subject: Re: No md superblock immediately after creating RAID 5 /dev/md0
Date: Thu, 28 Aug 2008 11:49:57 +0200	[thread overview]
Message-ID: <200808281149.58005.bs@q-leap.de> (raw)
In-Reply-To: <8CAD6FFC01AB7AC-524-231A@webmail-nf07.sim.aol.com>

On Thursday 28 August 2008 10:32:32 thomas62186218@aol.com wrote:
> Hi all,
>
> I am struggling with an issue on an Ubuntu 8.0.4 64-bit system. The
> system has 12 SATA drives. I create a RAID 5 array using mdadm as
> follows:
>
> mdadm -Cv /dev/md0 -n12 -l5 -c128 /dev/sd[b-m] -R -f
>
> The device creates successfully and starts and is visible as syncing in
> cat /proc/mdstat. But, according to mdadm -X /dev/md0, there is no md
> superblock on the device. Doing the same mdadm -X command for all

You need to run --detail for md devices

> components /dev/sdb through /dev/sdm shows superblocks. If I reboot the

--examine only works for the components

> system, /dev/md0 is completely gone, and a mdadm --assemble --scan

Did you add the corresponding entries to your mdadm.conf?

See this chapter in "man 8 mdadm"

<quote>
         echo ’DEVICE /dev/hd[a-z] /dev/sd*[a-z]’ > mdadm.conf
         mdadm --examine --scan --config=mdadm.conf >> mdadm.conf
       This  will  find  arrays which could be assembled from existing IDE and 
SCSI whole drives (not partitions),
       and store the information in the format of a config file.  This file is 
very  likely  to  contain  unwanted
       detail, particularly the devices= entries.  It should be reviewed and 
edited before being used as an actual
       config file.

</quote>


Cheers,
Bernd


-- 
Bernd Schubert
Q-Leap Networks GmbH
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-08-28  9:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  8:32 No md superblock immediately after creating RAID 5 /dev/md0 thomas62186218
2008-08-28  9:17 ` Andrew Farley
2008-08-29  5:31   ` thomas62186218
2008-08-28  9:49 ` Bernd Schubert [this message]
2008-08-28 10:07 ` Peter Rabbitson
     [not found] ` <9b4ac8ccbe69d232ff2d77fd4e3590c2.squirrel@neil.brown.name>
2008-08-29  5:47   ` thomas62186218
2008-08-29  6:01     ` NeilBrown
2008-09-16  9:37       ` thomas62186218

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=200808281149.58005.bs@q-leap.de \
    --to=bs@q-leap.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=thomas62186218@aol.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).