Non-critial drive error inquiry

Jeff Boyce <[email protected]>
Newsgroups gmane.linux.hardware.dell.poweredge
Message-ID <[email protected]>
Greetings -

I have a fairly simple question that I am hoping someone here can 
answer.  I recently replaced a hard drive in my PE T610 with the same 
manufacturer and model as the failed drive (Seagate ST3300657SS) .  
After my raid rebuild with the new drive, OMSA still shows my new drive 
with a Status=Non-Critical.  It also shows value for Certified=No.  Now 
I understand why the drive is listed as not certified because I 
purchased it from another vendor (not Dell), but I am trying to verify 
why it shows a Status=Non-Critical.  Is it *just* because it is not a 
certified Dell drive?  I am wondering this because the new drive also 
has a different firmware version than the other drives in the RAID and I 
am wondering if that is possibly the reason for the Status=Non-Critical.

I know when the PERC H700 controllers were first used, the Dell firmware 
did not allow non-Dell certified drives.  But I also recall that this 
was changed with a firmware update and that non-Dell certified drives 
are now allowed.  I am not sure that allowed / not-allowed is exactly 
correct here, it may have been something less aggressive.  The firmware 
version for my H700 controller is 12.10.6-0001, which I believe is up to 
date but still need to run some firmware update checks.  The firmware 
for my new drive is 000B, while the other original drives with updated 
firmware is ES68. The Seagate website states that 000B is the latest 
firmware for that drive, while the Dell support site states that ES68 is 
the latest firmware.  I still have to figure out what is going on 
there.  But my only question right now is what is the possible reason 
for my Status=Non-Critical.

Thanks.  Please cc me directly with responses as I only receive the 
daily digest of the mailing list.

Jeff

-- 

Jeff Boyce
Meridian Environmental
www.meridianenv.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.