linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fixitdad5@verizon.net
To: linux-raid@vger.kernel.org
Subject: RAID problem
Date: Wed, 14 Aug 2013 15:49:37 -0500 (CDT)	[thread overview]
Message-ID: <1869496.205994.1376513377257.JavaMail.root@vznit170146> (raw)

If you are still offering help with raid corruption due to the bug in kernels 3.2 and 3.3, I would like some help.

I load Ubuntu 12.04 precise (with kernel 3.2 since it was in the package) just 2 weeks ago. I had pre-existing raids and the raid's meta data was corrupted on the first boot after the successful installation so I have lost my data. I tried most of the suggestions that I found on the web, employing the intelligence in mdadm -assemble, etc. without success.

I have now updated the kernel to 3.4.0 rc7 (3.4.0-030400-generic #201205210521 SMP) and built an empty raid. However, I cannot boot without disconnecting the RAID drives. With the RAID drives hooked up and the updated kernel with the additional parameters listed below, I I fall into busybox and cannot boot successfully. What do I do now?
 
My configuration is 
Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
7983 MiB
running SELinux
Raid is a simple stripping (level 0) for speed
I have set the noautodetect and nodmraid parameters for the kernel

             reply	other threads:[~2013-08-14 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 20:49 fixitdad5 [this message]
2013-08-14 23:42 ` RAID problem NeilBrown
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 23:32 RAID Problem colli419
2010-03-17  0:09 ` Neil Brown
2010-03-20 16:55   ` Bill Davidsen

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=1869496.205994.1376513377257.JavaMail.root@vznit170146 \
    --to=fixitdad5@verizon.net \
    --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).