All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Bowes <robin-lists@robinbowes.com>
To: linux-raid@vger.kernel.org
Subject: new array not starting
Date: Wed, 08 Nov 2006 01:59:08 +0000	[thread overview]
Message-ID: <eirdlc$l7j$1@sea.gmane.org> (raw)

Hi,

I've just done an FC6 install on to a system with 2 x 250GB disks and 8
x 500GB disks. /dev/md0 is a 100MB mirror mounted as boot, and /dev/md1
is another mirror using the rest of the disks and is assigned to an LVM
PV/VG with LVs created for various system partitions.

After fun and games with grub (0.97 only supports up to 8 disks - I had
to patch grub to support up to 16 disks) I got the server to boot.

I then configured /dev/md2 as an 8 disk RAID6 array using the 8 x 500GB
disks using the whole of each disk for the array, i.e. no partitions.

This is the command I used to create the array:

mdadm --create /dev/md2 --raid-devices=8 --level=6 --auto=yes /dev/sdc
/dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh /dev/sdi /dev/sdj

When the array havd finished syncing, I rebooted the server.

However, /dev/md2 did not restart.

If I try to start the array manually:

# mdadm --assemble --auto=yes  /dev/md2 /dev/hdc /dev/hdd /dev/hde
/dev/hdf /dev/hdg /dev/hdh /dev/hdi /dev/hdj
mdadm: cannot open device /dev/hdc: No such file or directory
mdadm: /dev/hdc has no superblock - assembly aborted

What's going on here? No superblock? Doesn't that get written when the
array is created?

Am I doing this right?

Thanks,

R.


             reply	other threads:[~2006-11-08  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08  1:59 Robin Bowes [this message]
2006-11-08  2:12 ` new array not starting Robin Bowes
2006-11-08  2:37   ` Robin Bowes
2006-11-08  2:52     ` Robin Bowes
2006-11-08 12:55       ` Robin Bowes
2006-11-08 16:58       ` Bill Davidsen
2006-11-08  2:53     ` Richard Scobie

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='eirdlc$l7j$1@sea.gmane.org' \
    --to=robin-lists@robinbowes.com \
    --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.