From: Romeyn Prescott <romeyn@gmail.com>
To: linux-raid@vger.kernel.org
Subject: RAID 0 went down...
Date: Mon, 11 Oct 2004 08:28:37 -0400 [thread overview]
Message-ID: <4aaefdb041011052847dd1c18@mail.gmail.com> (raw)
I have a RH 9.0 box with a RAID 0. I started getting some I/O errors
and when I rebooted the box md0 wouldn't mount.
/etc/raiddtab:
-----
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
chunk-size 64k
persistent-superblock 1
nr-spare-disks 0
device /dev/sdb1
raid-disk 0
device /dev/sdc1
raid-disk 1
-----
The problem appears to be with /dev/sdc, yet it passes all of the
manufacturer's (Seagate) diagnostics. Here's what /var/log/dmesg
says:
-----
md: Autodetecting RAID arrays.
[events: 00000095]
[events: 00000031]
md: autorun ...
md: considering sdc1 ...
md: adding sdc1 ...
md: adding sdb1 ...
md: created md0
md: bind<sdb1,1>
md: bind<sdc1,2>
md: running: <sdc1><sdb1>
md: sdc1's event counter: 00000031
md: sdb1's event counter: 00000095
md: superblock update time inconsistency -- using the most recent one
md: freshest: sdb1
md: kicking non-fresh sdc1 from array!
md: unbind<sdc1,1>
md: export_rdev(sdc1)
md0: former device sdc1 is unavailable, removing from array!
md0: max total readahead window set to 512k
md0: 2 data-disks, max readahead per data-disk: 256k
md: md0, array needs 2 disks, has 1, aborting.
raid0: disks are not ordered, aborting!
md: pers->run() failed ...
md :do_md_run() returned -22
md: md0 stopped.
md: unbind<sdb1,0>
md: export_rdev(sdb1)
md: ... autorun DONE.
-----
Is there any way I can recover from this? I've been googling my
brains out, but most of what I find relates to RAID1. Restoring from
a backup is possible, but..."complicated" and is my last resort.
TIA,
...ROMeyn
--
http://www2.potsdam.edu/prescor/signat-url.htm
next reply other threads:[~2004-10-11 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 12:28 Romeyn Prescott [this message]
2004-10-11 10:10 ` RAID 0 went down Mike Tran
2004-10-11 18:38 ` Romeyn Prescott
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=4aaefdb041011052847dd1c18@mail.gmail.com \
--to=romeyn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.