From: Max Waterman <davidmaxwaterman@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: strangre drive behaviour.
Date: Sun, 06 Mar 2005 15:00:55 +0800 [thread overview]
Message-ID: <422AAAA7.6080106@fastmail.co.uk> (raw)
I've been reconfiguring my raid drives.
I used to have it this way...
4 Parallel IDE i/f's
each i/f's master was a WD800 in a RAID5
each i/f's slave was a WD2000 in a RAID5
I am removing the WD800 array and moving the WD2000 array to masters; so
there are no slaves.
However, in the process, one of my WD2000's seems to be having problems.
It seems to work as a slave device, but not as a master. I have tried
many combinations of interfaces/cables/power/etc.
I can even put it on an i/f on it's own as a slave device, and it seems
to work (the device name changes to show that it is actually the 2nd
device on the channel - ie when testing it on the motherboard, it shows
up as hdd, not hdc).
I am not sure what to do.
Can I just make it a slave device? How will that effect performance?
Any ideas?
Max.
next reply other threads:[~2005-03-06 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 7:00 Max Waterman [this message]
2005-03-06 9:41 ` strangre drive behaviour Nicola Fankhauser
2005-03-06 10:29 ` strange " Max Waterman
2005-03-07 21:21 ` strangre " Molle Bestefich
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=422AAAA7.6080106@fastmail.co.uk \
--to=davidmaxwaterman@fastmail.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=mwaterman@jingmei.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).