linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ninti Systems <office@ninti.com.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: Add device doesn't stick
Date: 31 Mar 2004 17:56:45 +0930	[thread overview]
Message-ID: <1080721605.10119.57.camel@localhost> (raw)

Back again ... :-)

So far so good with building RAID1 arrays using the 'missing' device
method on an already installed Slackware 9.1 system.

I've set up the RAID devices, they are autodetected on boot, everything
looks good. 

I hotadd the 'missing' device and the two devices sync.

I run 'mdadm --detail /dev/md5' and yep, the full array is now running
with both disks. I can 'ls' the contents etc.

I reboot and ... back to degraded mode with one failed device. The
hotadded device doesn't stick to the RAID device.

I'm sure there is a simple explanation. One system complaint is that the
expected superblock info couldn't be found (something like "expecting
a2hgf64jdk found 00000000").

I'm not sure how to rectify this?

Thanks
Mick



                 reply	other threads:[~2004-03-31  8:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1080721605.10119.57.camel@localhost \
    --to=office@ninti.com.au \
    --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).