linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcus <nexuslite@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Raid 5 Array
Date: Sat, 2 Apr 2011 11:51:58 -0700	[thread overview]
Message-ID: <BANLkTim8620MUckc+EVCWo9FCTs=65_p8Q@mail.gmail.com> (raw)

I have a raid array this is the second time an upgrade seems to have
corrupted the array.

I get the following message from dmesg when trying to mount the array
[  372.822199] RAID5 conf printout:
[  372.822202]  --- rd:3 wd:3
[  372.822208]  disk 0, o:1, dev:md0
[  372.822212]  disk 1, o:1, dev:sdb1
[  372.822216]  disk 2, o:1, dev:sdc1
[  372.822305] md2: detected capacity change from 0 to 1000210300928
[  372.823206]  md2: p1
[  410.783871] EXT4-fs (md2): Couldn't mount because of unsupported
optional features (3d1fc20)
[  412.401534] EXT4-fs (md2): Couldn't mount because of unsupported
optional features (3d1fc20)

I originally had a raid0 md0 with two 160GB drives, a raid0 md1 with
250GB and md0, a raid 5 with a 1.0TB, 500GB, and md1

I swapped out md1 with a new 1TB drive which worked. then i dropped
the 500GB and combined it with the 250GB drive to make a 750GB drive

The error seems to come when you reintroduce drives that were
previously in a raid array into a new raid array. This is the second
time I have ended up with the same problem.

Any suggestions on how to recover from this or is my only option to
reformat everything and start again?

             reply	other threads:[~2011-04-02 18:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 18:51 Marcus [this message]
2011-04-02 19:01 ` Raid 5 Array Simon McNair
     [not found]   ` <BANLkTimJfUhvkpkkAH=NLJOvLL-Jotrwqg@mail.gmail.com>
2011-04-02 20:09     ` Simon McNair
     [not found]       ` <BANLkTim3uOiF7Qdir_Vou3rSp1zJmgf6iA@mail.gmail.com>
2011-04-02 21:27         ` Simon Mcnair
2011-04-02 21:45       ` Simon Mcnair
2011-04-02 22:01         ` Roman Mamedov
2011-04-02 22:04           ` Roberto Spadim
2011-04-02 23:06             ` Marcus
2011-04-03  0:22               ` Marcus
2011-04-03  6:41                 ` Marcus
2011-04-03  7:49                   ` NeilBrown
2011-04-03  8:02                     ` Marcus
2011-04-03 11:01                       ` NeilBrown
2011-04-03 17:46                         ` Marcus
2011-04-03 17:50                           ` Roman Mamedov
     [not found]                             ` <BANLkTinzOpR-pgR1GYxgxaJhNoOUxc0D_w@mail.gmail.com>
2011-04-03 19:57                               ` Roman Mamedov

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='BANLkTim8620MUckc+EVCWo9FCTs=65_p8Q@mail.gmail.com' \
    --to=nexuslite@gmail.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 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).