From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Michael Harris <michael.harris@rmit.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: identifying failed disk/s in an array.
Date: Wed, 23 Jan 2008 07:56:41 +0100 [thread overview]
Message-ID: <4796E529.7030502@wpkg.org> (raw)
In-Reply-To: <479765CF.A931.0080.0@ems.rmit.edu.au>
Michael Harris schrieb:
> Hi,
>
> I have just built a Raid 5 array using mdadm and while it is running fine I have a question, about identifying the order of disks in the array.
>
> In the pre sata days you would connect your drives as follows:
>
> Primary Master - HDA
> Primary Slave - HDB
> Secondary - Master - HDC
> Secondary - Slave -HDD
>
> So if disk HDC failed i would know it was the primary disk on the secondary controller and would replace that drive.
>
> My current setup is as follows
>
> MB Primary Master (PATA) Primary Master - Operating System
>
> The array disks are attached to:
>
> MB Sata port 1
> MB Sata port 2
> PCI card Sata port 1
>
> When i setup the array the OS drive was SDA and the other SDB,SDC,SDD.
>
> Now the problem is everytime i reboot, the drives are sometimes detected in a different order, now because i mount root via the UUID of the OS disk and the kernel looks at the superblocks of the raided drives everything comes up fine, but I'm worried that if i move the array to another machine and need to do a mdadm --assemble that i won't know the correct order of the disks and what is more worrying if i have a disk fail say HDC for example, i wont know which disk HDC is as it could be any of the 5 disks in the PC. Is there anyway to make it easier to identify which disk is which?.
If the drives have any LEDs, the most reliable way would be:
dd if=/dev/drive of=/dev/null
Then look which LED is the one which blinks the most.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-01-23 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 5:05 identifying failed disk/s in an array Michael Harris
2008-01-23 6:56 ` Tomasz Chmielewski [this message]
2008-01-23 12:02 ` David Greaves
2008-01-23 14:00 ` Wolfgang Denk
2008-01-23 15:22 ` Nagilum
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=4796E529.7030502@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-raid@vger.kernel.org \
--cc=michael.harris@rmit.edu.au \
/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).