From: Thomas Andrews <tandrews@grok.co.za>
To: linux-raid@vger.kernel.org
Subject: One partition degraded after every reboot
Date: Fri, 26 Mar 2004 17:41:25 +0200 [thread overview]
Message-ID: <20040326154125.GN1950@gaspode.nextlink.co.za> (raw)
Hi All,
I've set up RAID-1 on a pair of disks recently. When I reboot I get this
in syslog, even though the partition was perfect & not degraded before:
kernel: /dev/ide/host2/bus0/target0/lun0: p1 < p5 p6 p7 p8 > p2 p3
kernel: /dev/ide/host2/bus1/target0/lun0: p1 < p5 p6 p7 p8 > p2 p3
kernel: [events: 0000001c]
kernel: md: bind<ide/host2/bus1/target0/lun0/part5,1>
kernel: md: ide/host2/bus1/target0/lun0/part5's event counter: 0000001c
kernel: md1: former device ide/host2/bus0/target0/lun0/part5 is unavailable, removing from array!
More specifically, of the 4 RAID-1 partitions, md1 (my root partition)
is in degraded mode. Here's a snippet of /proc/mdstat:
md1 : active raid1 ide/host2/bus1/target0/lun0/part5[0]
38957440 blocks [2/1] [U_]
All the RAID partitions are of type FD on both disks, and the disks are
brand new. I swapped out the 'offending' disk with another brand new
disk, but it made no difference.
This is a stock Debian/testing pc running a stock 2.4.24-1-686 kernel.
I use mdadm. Initially I thought that it was grub messing things up, but
I'm booting from a floppy now, and I haven't bothered to intall grub on
the newer disk.
To recommission partition on the previous disk, I used
mdadm --zero-superblock /dev/hde5
mdadm /dev/md1 -a /dev/hde5
This set things right, and there were no problems until the next reboot.
The process is totally repeatable.
What am I missing here ?
Why does it say "device ide/host2/bus0/target0/lun0/part5 is unavailable"
in the log ??
next reply other threads:[~2004-03-26 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 15:41 Thomas Andrews [this message]
2004-04-09 13:39 ` One partition degraded after every reboot Thomas Andrews
2004-04-11 19:55 ` Thomas Andrews
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 11:45 Philipp Gortan
2004-04-01 17:52 ` Thomas Andrews
2004-04-02 9:20 ` Philipp Gortan
2004-04-09 13:09 ` Thomas Andrews
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=20040326154125.GN1950@gaspode.nextlink.co.za \
--to=tandrews@grok.co.za \
--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).