Index: [Article Count Order] [Thread]

Date:  Thu, 26 Feb 2009 06:55:14 -0600
From:  Chris Gebhardt - VIRTBIZ Internet <cobaltfacts (at mark) virtbiz.com>
Subject:  [coba-e:15138] Re: Hard Drive Failure
To:  coba-e (at mark) bluequartz.org
Message-Id:  <49A69132.8000700 (at mark) virtbiz.com>
In-Reply-To:  <C5CBF874.70E1%webmaster (at mark) muntada.com>
References:  <C5CBF874.70E1%webmaster (at mark) muntada.com>
X-Mail-Count: 15138

Abdul Rashid Abdullah wrote:
> I have a RAID 1 on my system.  I have a hard drive failure:
> 
> cat /proc/mdstat
> Personalities : [raid1]
> md6 : active raid1 sdb1[1] sda1[0]
>       104320 blocks [2/2] [UU]
>       
> md3 : active raid1 sdb3[1] sda3[2](F)
>       4192896 blocks [2/1] [_U]
>       
> md5 : active raid1 sdb5[1] sda5[2](F)
>       1052160 blocks [2/1] [_U]
>       
> md2 : active raid1 sdb6[1] sda6[2](F)
>       1052160 blocks [2/1] [_U]
>       
> md4 : active raid1 sdb7[1] sda7[2](F)
>       475692544 blocks [2/1] [_U]
>       
> md1 : active raid1 sdb2[1] sda2[2](F)
>       6289344 blocks [2/1] [_U]
> 
> 
> How do I know which specific drive failed so that I can replace it correctly
> and what best practices should I follow when replacing it?

Hi Rashid,
First off, there's no guarantee that the drive has actually sustained a 
failure.  It's certainly possible that it simply fell out of sync for 
some reason.   In that case, give it a reboot and see if it rebuilds for 
you.  (from the "try the most simple thing first" school of thought.)

If it's really a bad drive, looks to me like it's sdb2.  What is the 
output of this:
# mdadm -D /dev/md1

-- 
Chris Gebhardt
VIRTBIZ Internet Services
Access, Web Hosting, Colocation, Dedicated
www.virtbiz.com | toll-free (866) 4 VIRTBIZ