linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victor <linux-raid@vitoni.de>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: missing superblock on RAID5
Date: Mon, 13 Oct 2003 17:59:14 +0200	[thread overview]
Message-ID: <3F8ACBD2.CA1B8CBD@vitoni.de> (raw)

At the time I created the RAID array I thought it had superblocks,
however if I use mdadm I get these results:

# mdadm --query /dev/md0
/dev/md0: 230.08GiB raid5 4 devices, 0 spares. Use mdadm --detail for
more detail.
/dev/md0: No md super block found, not an md component.

If  the array really shouldn't have a superblock, is it possible to add
one (maybe marking a device faulty and readding it and repeating this
for each device)?


Thanks in advance,

Victor



             reply	other threads:[~2003-10-13 15:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 15:59 Victor [this message]
     [not found] ` <3F8AD02C.8080606@fantinibakery.com>
2003-10-13 17:47   ` missing superblock on RAID5 Victor
2003-10-13 19:57     ` rob
2003-10-13 21:09       ` Victor
2003-10-13 23:27         ` rob
2003-10-13 23:44           ` Victor
2003-10-14  0:18             ` rob

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=3F8ACBD2.CA1B8CBD@vitoni.de \
    --to=linux-raid@vitoni.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 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).