[Cialug] Bad hd in raid?
Josh More
cialug@cialug.org
Wed, 20 Apr 2005 15:19:28 -0500
--=__PartB5969C40.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
You can use smartctl to force a test and check it afterwards.
I will not supply a guide on how to do so, as the steps you do depend
on the type of drive you have and what kind of tests you run, and
I don't want to lead you down the wrong path.
However, man smartctl is fairly readable, so it's not too hard.
Just know that doing a read of a test status stops the test,
so be sure to wait until the test is done before quering it.
--
-Josh More, RHCE, CISSP
morej@alliancetechnologies.net
515-245-7701
>>>oddvector@gmail.com 04/20/05 1:59 pm >>>
I have a disk that likes to drop out of my raid array. Here is my
current mdstat.
Personalities : [linear] [raid0] [raid1] [raid5]
read_ahead 1024 sectors
md0 : active raid5 hdh1[3] hdg1[2] hdf1[1]
234444288 blocks level 5, 128k chunk, algorithm 2 [4/3] [_UUU]
unused devices: <none>
I'm running software raid 5 on a slackware 10.1 box. hde is the
culprit drive. The last time I had this drive drop out of the raid I
was able to add him back in with no problems. I'm also not seeing any
read/write errors in my log files.
Is there any way for me to check this disk before I stick it back into
the raid? If it was going bad shouldn't there be errors in my log
files? Should I just replace this disk?
Cialug mailing list
Cialug@cialug.org
http://cialug.org/mailman/listinfo/cialug
--=__PartB5969C40.0__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML
<html>
<head>
<style type=3D"text/css">
<!--
body { font-variant: normal; margin-left: 4px; line-height: =
normal; margin-bottom: 1px; margin-right: 4px; margin-top: 4px }
-->
</style>
=20
</head>
<body style=3D"margin-left: 4px; margin-bottom: 1px; margin-right: 4px; =
margin-top: 4px">
<DIV> You can use smartctl to force a test and check it afterwards=
.
</DIV>
<DIV>I will not supply a guide on how to do so, as the steps you =
do depend
</DIV>
<DIV>on the type of drive you have and what kind of tests you run, =
and
</DIV>
<DIV>I don't want to lead you down the wrong path.
</DIV>
<DIV> </DIV>
<DIV>However, man smartctl is fairly readable, so it's not =
too hard.
</DIV>
<DIV>Just know that doing a read of a test status stops the test,
</DIV>
<DIV>so be sure to wait until the test is done before quering it.
</DIV>
<DIV> </DIV>
<DIV>--=20
</DIV>
<DIV>-Josh More, RHCE, CISSP
</DIV>
<DIV> morej@alliancetechnologies.net
</DIV>
<DIV> 515-245-7701
</DIV>
<DIV> </DIV>
<DIV><br><br>>>>oddvector@gmail.com 04/20/05 1:59 pm =
>>><br>I have a disk that likes to drop out of my raid array. =
Here is my<br>current mdstat.<br><br>Personalities : [linear] =
[raid0] [raid1] [raid5]<br>read_ahead 1024 =
sectors<br>md0 : active raid5 hdh1[3] hdg1[2] hdf1[1	=
3;<br>     234444288 blocks level 5, 128k =
chunk, algorithm 2 [4/3] [_UUU]<br><br>unused devices: =
<none><br><br>I'm running software raid 5 on a slackware 10.1 =
box. hde is the<br>culprit drive. The last time I had this drive drop out =
of the raid I<br>was able to add him back in with no problems. I'm =
also not seeing any<br>read/write errors in my log files.<br><br>Is there =
any way for me to check this disk before I stick it back into<br>the =
raid? If it was going bad shouldn't there be errors in my =
log<br>files? Should I just replace this disk?<br><br>Cialug =
mailing list<br>Cialug@cialug.org<br>http://cialug.org/mailman/listinfo/cia=
lug<br> </DIV>
</body>
</html>
--=__PartB5969C40.0__=--