From: Louis-David Mitterrand <vindex+lists-linux-raid@apartia.org>
To: linux-raid@vger.kernel.org
Subject: [urgent] supermicro ejecting disks
Date: Thu, 9 Nov 2006 15:18:11 +0100 [thread overview]
Message-ID: <20061109141811.GA5805@apartia.fr> (raw)
Hello,
We recently changed our main server to a Supermicro with 6 scsi disks in
soft raid6 with kernel 2.6.18.
After running OK for a few days, 3 disks were suddenly ejected from the
raid6. We are now trying to reassemble the partition in another box but
keep getting a "superblock corrupted" error on the fs. We're in a pretty
bad state right now, as this is a production machine. Of course we have
bakcups but restoring them will take some time.
Does anyone have any idea of what has happended and how to fix it?
Thanks,
next reply other threads:[~2006-11-09 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 14:18 Louis-David Mitterrand [this message]
2006-11-09 14:27 ` [consultant needed] (was: supermicro ejecting disks) Louis-David Mitterrand
2006-11-09 14:43 ` [solved] " Louis-David Mitterrand
2006-12-20 3:47 ` [solved] Bill Davidsen
2006-12-20 6:59 ` [solved] supermicro failure Louis-David Mitterrand
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=20061109141811.GA5805@apartia.fr \
--to=vindex+lists-linux-raid@apartia.org \
--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).