Re: identifying failed disk/s in an array.

2008-01-23 Thread David Greaves
Tomasz Chmielewski wrote:
 Michael Harris schrieb:
 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.

And/or use smartctl to look up the make/model/serial number and look at the
drive label. I always do this to make sure I'm pulling the right drive (also
useful to RMA the drive)


David
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: identifying failed disk/s in an array.

2008-01-23 Thread Wolfgang Denk
In message [EMAIL PROTECTED] you wrote:

 And/or use smartctl to look up the make/model/serial number and look at the
 drive label. I always do this to make sure I'm pulling the right drive (also
 useful to RMA the drive)

Or, probblay even faster, do a ls -l /dev/disk/by-id (assuming you
are using udev).

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH, MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
Command, n.:
Statement presented by a human and accepted by a computer
in such a manner as to make the human feel as if he is in control.
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: identifying failed disk/s in an array.

2008-01-23 Thread Nagilum

- Message from [EMAIL PROTECTED] -
Date: Wed, 23 Jan 2008 16:05:40 +1100
From: Michael Harris [EMAIL PROTECTED]
Reply-To: Michael Harris [EMAIL PROTECTED]
 Subject: identifying failed disk/s in an array.
  To: linux-raid@vger.kernel.org



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?.


- End message from [EMAIL PROTECTED] -

Try this:
mdadm -Q --detail /dev/md0
to see which disk is which disk in the raid.
To identify a disk you can examine it using:
mdadm -E /dev/sd[b-d]
and read your dmesg.
And finally you can use blkid to associate UUIDs with devices.
I hope this helps.
Kind regards,
Alex.


#_  __  _ __ http://www.nagilum.org/ \n icq://69646724 #
#   / |/ /__  _(_) /_  _  [EMAIL PROTECTED] \n +491776461165 #
#  // _ `/ _ `/ / / // /  ' \  Amiga (68k/PPC): AOS/NetBSD/Linux   #
# /_/|_/\_,_/\_, /_/_/\_,_/_/_/_/   Mac (PPC): MacOS-X / NetBSD /Linux #
#   /___/ x86: FreeBSD/Linux/Solaris/Win2k  ARM9: EPOC EV6 #




cakebox.homeunix.net - all the machine one needs..
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


identifying failed disk/s in an array.

2008-01-22 Thread Michael Harris
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?.

thanks

Mike



-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: identifying failed disk/s in an array.

2008-01-22 Thread Tomasz Chmielewski

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


-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html