raid 5 redundancy check failure

[Alan]

I've had this problem before and assumed it had to do
with the hardware I was using at the time.

I have 6 drives that I've created a raid 5 volume from in
windows. everything works fine, and I can use my raid 5
volume with no problem, but then it suddenly tells me
that one of the drives failed a redundancy check. All
the drives are brand new and all are functioning
perfectly fine. If I tell it to reactiviate the volume
it will, and then tomorrow some time I will probably get
the same failure message.

Now, I'm not sure if this matters... but when I set up
this newest raid I noticed one of the drives under disk
management showed up with diagnal grey lines across it...
i assumed this meant that it was the "parity" drive.
That happens to be the one that failed the check also.

Is there some way to figure out why this is happening
(event log doesn't give me anything useful) and stop it?
it takes a really long time to reactivate a 1TB volume.

 

[Pegasus \(MVP\)]

I've had this problem before and assumed it had to do
with the hardware I was using at the time.

I have 6 drives that I've created a raid 5 volume from in
windows. everything works fine, and I can use my raid 5
volume with no problem, but then it suddenly tells me
that one of the drives failed a redundancy check. All
the drives are brand new and all are functioning
perfectly fine. If I tell it to reactiviate the volume
it will, and then tomorrow some time I will probably get
the same failure message.

Now, I'm not sure if this matters... but when I set up
this newest raid I noticed one of the drives under disk
management showed up with diagnal grey lines across it...
i assumed this meant that it was the "parity" drive.
That happens to be the one that failed the check also.

Is there some way to figure out why this is happening
(event log doesn't give me anything useful) and stop it?
it takes a really long time to reactivate a 1TB volume.

A CRC error indicates that you have a hardware problem.
As a first step you should run the diagnostic routine that
your disk manufacturer makes available on his web site.

 

[Guest]

Well, I actually checked all the drives after this
happened, and they checked fine. Additionally, when this
happened previously I checked the drives then too... and
they all worked fine (and in fact still are working fine,
although not in a raid like they were. This seems to be
some bug in the raid software that comes with 2000
server, although apparently it isn't very common or other
people would be complaining or at least know of it.

My 6 drives are now in a spanned volume and all working
fine, although I would prefer that they were in a raid 5
setup instead.