linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Craig Hollabaugh <craig@hollabaugh.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 kicks non-fresh drives
Date: Thu, 25 May 2006 16:30:37 -0600	[thread overview]
Message-ID: <1148596237.4957.4.camel@hendrix.hollabaugh.com> (raw)
In-Reply-To: <17526.7947.129968.287311@cse.unsw.edu.au>

On Fri, 2006-05-26 at 07:18 +1000, Neil Brown wrote:
> And the partition types of sdj1 and sdk1 are ???

Neil,

That did it! I set the partition FS Types from 'Linux' to 'Linux raid
autodetect' after my last re-sync completed. Manually stopped and
started the array. Things looked good, so I crossed my fingers and
rebooted. The kernel found all the drives and all is happy here in
Colorado.

Thanks ever so much for your comment!!

Craig


After the reboot

root@vaughan[501]: mdadm -D /dev/md0
/dev/md0:
        Version : 00.90.03
  Creation Time : Thu Jan 16 09:10:52 2003
     Raid Level : raid5
     Array Size : 1289056384 (1229.34 GiB 1319.99 GB)
    Device Size : 117186944 (111.76 GiB 120.00 GB)
   Raid Devices : 12
  Total Devices : 13
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Thu May 25 16:21:28 2006
          State : clean
 Active Devices : 12
Working Devices : 13
 Failed Devices : 0
  Spare Devices : 1

         Layout : left-symmetric
     Chunk Size : 128K

           UUID : 4d862825:91140f1a:eb97e7f2:9bfa2403
         Events : 0.2684360

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       8       33        2      active sync   /dev/sdc1
       3       8      129        3      active sync   /dev/sdi1
       4       8       65        4      active sync   /dev/sde1
       5       8       81        5      active sync   /dev/sdf1
       6       8       97        6      active sync   /dev/sdg1
       7       8      113        7      active sync   /dev/sdh1
       8       8       49        8      active sync   /dev/sdd1
       9       8      161        9      active sync   /dev/sdk1
      10      22        1       10      active sync   /dev/hdc1
      11       8      177       11      active sync   /dev/sdl1

      12       8      145        -      spare   /dev/sdj1






  parent reply	other threads:[~2006-05-25 22:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-25 15:38 RAID5 kicks non-fresh drives Craig Hollabaugh
2006-05-25 21:18 ` Neil Brown
2006-05-25 21:39   ` Craig Hollabaugh
2006-05-25 22:30   ` Craig Hollabaugh [this message]
2006-05-26  7:57     ` Mikael Abrahamsson
2006-05-26 14:11       ` Craig Hollabaugh
2006-05-26 16:45         ` Mark Hahn
2006-05-26 17:06           ` Craig Hollabaugh
2006-05-26 17:30             ` Mark Hahn
2006-05-26 18:01               ` Craig Hollabaugh
2006-05-26 18:38             ` Luca Berra
2006-05-26 19:37               ` Mark Hahn
2006-05-27 12:21                 ` Luca Berra
2006-05-29  4:34           ` Neil Brown
2006-05-26 17:32       ` Bill Davidsen
2006-05-26 17:49         ` Craig Hollabaugh
2006-05-29  5:20       ` Neil Brown

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=1148596237.4957.4.camel@hendrix.hollabaugh.com \
    --to=craig@hollabaugh.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).