Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault - Howto with screen shots
in [Debian]
|
Prev: Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault - Howto with screen shots
Next: VLC no longer plays *.wmv video format
From: Bob Weber on 16 Jun 2010 12:20 Use smartctl from the smartmontools package. If mdadm says that /dev/sdc (or cat /proc/mdstat) is at fault then use "smartctl -a /dev/sdc" and it will print out all kinds of info on the drive including its serial number which should be on a sticker on the case of the drive. The programs included with smartmontools might have warned you of an impending failure. I have a smart self long test run om my drives 2 times a week. *...Bob* On 06/16/2010 09:32 AM, Steven wrote: > On Wed, June 16, 2010 13:13, Siju George wrote: >> Hope some one finds this helpful :-) >> >> --Siju >> >> Rebuilding RAID 1 Array in Linux with a new hard disk after a disk fault. >> ========================================================================= >> > Thanks, this might prove useful. > However I do have a question... which might be just as important. > > How to identify which drive has failed in an array? > > I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, / > and /home. > /dev/sdc > /dev/sdd > /dev/sde > /dev/sdf > Each have 1 partition. > /dev/md0 (raid 1) consists of /dev/sdc1 and /dev/sdd1 > /dev/md1 (raid 1) consists of /dev/sde1 and /dev/sdf1 > > If a drive fails, how do I know which drive? This is a desktop system, not > a server. >
From: Håkon Alstadheim on 16 Jun 2010 15:10 Steven skrev: > How to identify which drive has failed in an array? > > I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, / > and /home. > /dev/sdc > /dev/sdd > /dev/sde > /dev/sdf > Each have 1 partition. > /dev/md0 (raid 1) consists of /dev/sdc1 and /dev/sdd1 > /dev/md1 (raid 1) consists of /dev/sde1 and /dev/sdf1 > > If a drive fails, how do I know which drive? This is a desktop system, not > a server. > > Just do "ls -l /dev/disk/by-id/". The disks will have factory labels with serial-numbers to match. -- Håkon Alstadheim / N-7510 Skatval / email:hakon(a)alstadheim.priv.no tlf: 74 82 60 27 mob: 47 35 39 38 http://alstadheim.priv.no/hakon/ spamtrap: finnesikke(a)alstadheim.priv.no -- 1 hit & you are out -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C191159.8080307(a)alstadheim.priv.no
From: Michal on 17 Jun 2010 04:20
On 16/06/2010 19:00, H�kon Alstadheim wrote: > Steven skrev: >> How to identify which drive has failed in an array? >> >> I have 6 disks, 4 are used in raid (mdadm), the other 2 contain /boot, / >> and /home. >> /dev/sdc >> /dev/sdd >> /dev/sde >> /dev/sdf >> Each have 1 partition. >> /dev/md0 (raid 1) consists of /dev/sdc1 and /dev/sdd1 >> /dev/md1 (raid 1) consists of /dev/sde1 and /dev/sdf1 >> >> If a drive fails, how do I know which drive? This is a desktop system, >> not >> a server. >> >> > > Just do "ls -l /dev/disk/by-id/". The disks will have factory labels > with serial-numbers to match. > This is a better way then disconnecting the drive and checking which drive was disconnected like I did, but I would still put a very easy to read label on the drive to say /dev/sdX. It would be far easier then checking a long serial number, especially if it's hard to read and you'd need to take each HDD out to check :) -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/4C19DA2D.1090604(a)ionic.co.uk |