Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Rick Bragg <lists@gmnet.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: fsck problems.  Can't restore raid
Date: Fri, 25 Dec 2009 21:47:31 -0500	[thread overview]
Message-ID: <1261795651.10448.97.camel@vibe> (raw)
In-Reply-To: <1261791227.10448.88.camel@vibe>

On Fri, 2009-12-25 at 20:33 -0500, Rick Bragg wrote:
> Hi,
> 
> I have a raid 10 array and for some reason the system went down and I
> can't get it back.  
> 
> during re-boot, I get the following error:
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate
> superblock:
>     e2fsck -b 8193 <device>
> 
> I have tried everything I can think of and I can't seem to do an fsck or
> repair the file system.
> 
> what can I do?
> 
> Thanks
> Rick
> 


More info:

My array is made up of /dev/sda, sdb, sdc, and sdd.  However they are
not mounted right now.  My OS is booted off of /dev/sde.  I am running
ubuntu 9.04

mdadm -Q --detail /dev/md0
mdadm: md device /dev/md0 does not appear to be active.

Where do I take if from here?  I'm not up on this as much as I should be
at all.  In fact I am quite a newbe to this... Any help would be greatly
appreciated.

Thanks
Rick




  reply	other threads:[~2009-12-26  2:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26  1:33 fsck problems. Can't restore raid Rick Bragg
2009-12-26  2:47 ` Rick Bragg [this message]
2009-12-26  3:12   ` Rick Bragg
2009-12-26 18:47     ` Leslie Rhorer
2009-12-26 19:44       ` Rick Bragg
2009-12-26 21:14         ` Leslie Rhorer
2009-12-26 21:59           ` Green Mountain Network Info
2009-12-27  1:01           ` Rick Bragg
2009-12-27  6:13             ` Leslie Rhorer
2009-12-27 18:41               ` Rick Bragg
2009-12-27 22:47                 ` Leslie Rhorer
2009-12-29  2:46                   ` Michael Evans

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=1261795651.10448.97.camel@vibe \
    --to=lists@gmnet.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