Event 571

Event 571 is a "sense key" event.

Essentially, it is typically a failure or prefailure event for a disk drive in your system.

Saying you had a 571, then another one.... means little.  571 is the generic even ID.  Whats important, is *what it says in the event*!!!!

You need to come here with more information.... specifically, the drive ID of both events, and the SCSI sense codes of both events.

In any case, the typical response to a sense key is to replace the drive, because they typically denote a drive with a problem. 

However, if you are continuously getting sense key events on the same SCSI ID even after replacing the drive, depending on what the SCSI sense codes are, you might be lookgin at a controller or backplane issue.

babiking:

What is the text of the actual event message?  What RAID controller card do you have?  What is the firmware/driver revision numbers?  Have you cleared the ESM log after the replacement of parts?

Message Edited by DELL-RobertC on 07-30-2004 09:41 AM

Ok, RobertC here's the info:

Actual Event Message: Source: PercPro 

- PERC 4/DI Controller 0, Array Disk 255:255 Sense Key = FF, Sense Code = FF, Sense Qualifier = FF.  If this disk is part of a redundant virtual disk, select the 'Offline' option and then replace the disk.  Then configure a hot spare and it will start the rebuild automatically.  If this disk is a hot spare, select the 'Prepare to Remove' option and then replace the disk.  If this disk is part of a non-redundant disk, you should back-up your data immediately.  If the disk fails, you will not be able to recover the data.

RAID Controller Card: PERC4/Di 128 MB (2 Internal Channels) (340-6467)

Firmware/Driver Revision Number: 2.27/6.32.2.32

Clearing the ESM log: I had a technician from Dell come out and replace the first failed drive.  I don't believe he clearned the log.  How would one do this?

Thanks again for the help!

~babiking

I highly recommend updating the firmware on the PERC4/di controller.  The two firmware updates since 2.27 did address some sense error request updates.  The fact that your sense error is detected on array disk 255:255 implies something is wrong with the firmware on the card (more so than that a particular disk is failing), since there is no disk #255 on Channel #255. 

Your driver also needs to be updated and should be updated first.  You are currently using the Microsoft Windows 2003 CD version of the driver.  Please update the PERC 4/DI driver for your Windows Server 2003 OS with the Dell revision (link below). 

*Are any drives actually blinking amber and showing as failed?  If so, we may not want to update firmware.  Judging from the description and error you quoted, it sounds like none of the actual drives (255:255 excluded) should be showing any kind of error status.

Please visit this page for the driver:  (This link is specific to the 2600)

The above link also links to the Firmware update files.  Choose an update type that you prefer (floppy boot DOS method, or Dell Update Package which runs in Windows then requires a reboot) and download it and update your firmware.  After the firmware update completes, if you have a RAID 5, you must run a consistency check.  You can start  a consistency check from the Management Menu of the [Ctrl-M] PERC BIOS Utility.

Yes, we do run RAID 5.  This happens to be a production server...our web server. How long will the consistency check take and if I run it after work hours will the server wait for me to click anything or just bootup on it's own?  I have a few other PE2600 that are not expierencing this issue....one being our email server...do I have to do the upgrade on them, too?  I actually downgraded the email server to W2K.

Sorry RobertC I have another question....after looking at the link you gave me, it does not state the drivers are for Windows 2003 Server unless that's what Windows Powered means.  This server is running Windows 2003 and I don't want to crash it by installing the wrong drivers.  Thank you!

~babiking

http://support.dell.com/support/downloads/type.aspx?c=us&cs=555&l=en&s=biz&SystemID=PWE_FOS_XEO_2600&category=0&os=WNET&osl=en&deviceid=2608&devlib=26

sorry Robert another question here...What is the difference between teh perc-cerc-w2k3-6.41.2.32-A03.exe and the RAID-DRVR-R71521.exe?  Do I just execute both files, the perc-cerc first and let it do it's thing?  Also under the "Additional Information" section, step #2 has me a little confused expecially where it says "The user must be careful to select the appropriate id when installing Windows Server 2003," does this pertain to a server that already has Windows 2003 installed and is just doing an update? 

Again, please tell me a lot more about running the consistency check...how long it will take (I think there are 3-36 GB drives) and I access the utility when I reboot the server, correct?

The perc-cerc-w2k3-6.41.2.32-A03.exe  file is a hard drive copy of the inf files needed to install or update the driver using the Device Manager driver update procedure.  The RAID-DRVR-R71521.exe is a executable update package that updates the driver for you when you launch it and click "Install".   

That consistency check should be run after hours and can take 6-8 hours give the disks on this server.

You don't need to be concerned about the additional information section that states to be careful about the ID when installing the OS.  That's just an extra note to explain that when installing Windows Server 2003 and when dealing with more than one Logical Disk in a RAID system, you would need to pay closer attention during the assisted setup as to where to the OS will be installed. 

Run the Update Package for the driver.  Do not reboot yet.  Then run the Update package for the firmware. Then reboot at the prompt.  Upon reboot, the firmware will be update. 

My statement about updating the driver was a general practice guideline.  In the case of the Adaptec controllers, it is a requirement.  In the case of  your embedded LSI PERC 4/di controller, it's not critical.  You can update the firmware first and the driver a week later and would still be fine.  In general though it's recommended to update the driver then the firmware and run a consistency check.  Sounds like you are ready to perform the updates if the drives are all online.

So should I run both executables to update the PERC driver and RAID controller firmware?  You said I needed to update the PERC/4di driver first and then the RAID controller firmware.

PS: the indicator light on the front bezel is not blinking amber and all drive statuses are online.  I checked my other PE2600, which came in the same shipment, and it is not displaying any warnings in the event log.

Thank you!