Event ID 571 HELP!!!

Hi,

The sense code 5-24-0 is an Illegal Request, the command descriptor block contains an invalid bit. The first thing that comes to mind is, the Perc 2/dc is not validated with tape devices. If you do have the tape drive connected to the Perc 2/dc, try connecting to the onboard Scsi controller or install a PCI Scsi controller instead.

FYI, the Scsi backplane in your system is Scsi ID 6. Also most Dell Scsi tape drives have the Scsi ID initially set to 6.

Hope this helps.

Hi Mark,
The tape drive was hooked up with the on board SCSI, before I updated to windows 2003, I have no problem with event error on array manager anyway I will try to to use addtional PCI SCSI card if this problem could be solved.

Anyway I have another question, if the Powervault 120T DD3 has its busy light keep blinking every 2 seconds where there is no activity on the drive I wonder what would caused the problem? I never experience problem with win2k before, after the upgrade win2k3 the PE2400 become wierd. I could not go back to win2k as the AD has been upgraded to Win2K3 mode. Is there any problem with same SCSI ID on the backplane and on tape drive even the tape drive is connected to different SCSI? is the Array manager misreported as it tries to detect the tape ID? Sorry to keep asking you as I could not get any expert that could help me to solve this problem.

Thankyou.

Hi,

PowerVault 120T LED:
This page discusses the LED's and possible causes of the problem (unfortunately, not very well):
http://docs.us.dell.com/docs/storage/dds3auto/front.htm

The most common cause of problems is the tape drive is dirty. A cleaning tape is only good for 20-30 uses and should be used after every 4 hours of operation on a new tape (until the entire tape has been written to once) and every 20 hours of operation for used tapes. The tapes should be replaced about once a year under normal usage.

Scsi ID:
If the tape drive is connected to the onboard Scsi controller, and the backplane is connected to the Perc 2/dc, it does not matter that the tape drive and the backplane have the same Scsi ID. I cannot explain why the Array Manager is reporting an error on Scsi ID 6 only when the tape drive is connected (again if the tape drive is definately on a different controller).

As a simple test, try changing the tape drive Scsi ID to 9, just to see if the errors change or goes away.
http://docs.us.dell.com/docs/storage/dds3auto/Jumpers.htm

I am experiencing the same "Event ID 571" message in my event logs on Array Manager, but I don't have any tape drives connected at all as you describe to the other person in this thread, just hard disks.

I have a PowerEdge 2500. The service tag is 7C2YX01

Here is the exact message:

"PERC 3/DC Controller 0, Array Disk 0:2 Sense Key =  3, Sense Code = 11, Sense Qualifier =  0."

Can you please describe what might be happening? Is this a warning of impending failure?

Thanks...

Event ID 571 is a generic message. The specifics are in the sense key and additional sense codes (asc/ascq).

The "03-11" message indicates a defective media block was encountered. If you have firmware > 1.80 on the PERC 3, it should reassign the defective block and all is well. If you do see the "03-11" reported frequently for the same drive ID, you may need to schedule replacement.

The "05-24" is an illegal request to ID#6. ID #6 is normallt the ID of the drive backplane or enclosure. I know this was a message seen with older firmware and Array Manager.  It was often seen at boot or logged when starting Array Manager. What controller, configuration, firmware revisions and Array Manager revision do you have?

We have a PERC 3/DC controller, configuration Raid 5, firmare revision 1.57, Array Manger revision 3.0 build 460.2

-will

It looks like you still have the original equipment. 

You may want to consider updating to the current firmware, drivers and Array Manager that are available in the downloads. There have been a lot of changes in all of these areas. With the 1.57 firmware, the bad block "03-11" is not reassigned and can result in the drive failing. 

If you update to the current levels and run a consistency check it should find and reassign the bad block reporting the error.

Message Edited by JakHix on 01-14-2004 12:57 PM

Hi there,

I have several systems with Event ID 571.  The majority of the errors are: Sense Key =  3, Sense Code =  C; Sense Qualifier =  3.   Nearly all originate from Fujitsu MAM3367MC disk.  Once these disks are swapped with disks from a different vendor, the errors stop.

All Perc 3 are firmware 1.80.  Many of the errors are from disks in Powervault 220s.

I have several questions:

1. Do you have details for errors "3 - C - 3"?

2. Is there a threshold (No of errors per day/week) above which we should systematically swap the disks?

3. Is there another resolution apart from swapping the disk (Consistency Checks succeed but do not stop the errors)?

Thanks, Nic

We too are receiving this event error and occasionally have had issues with data corruption.  We're running Win2003 on this server.

I ran the RAID configuration on boot and found that the backplane is listed as Processor in position 0:6 - Nothing else is tied to this.  We have drives in positions 0:0, 0:1, and 0:2.

Any idea how to clear out the backplane out of the RAID listing?  I know that would solve the problem.

Thanks.

Thak sfor the Backplane info.  Sorry I should have been clearer - the issue I'm having is what's listed at the top of this thread.

We're running a PE2300 with a Perc 2/SC and I'm also getting the Event 571 error referencing position 0:6 (which would be the Processor location in the RAID setup).

I've got the latest firmware and drivers installed so I'm a little baffled.   My apologies for not being clearer in my post.

Thanks.

The 03-0C-03 error is an offtrack write. With firmware at 1.80 or greater the operation is retried. It will only fail the drive if the operation is not successful after several attempts to retry on the same block. It shouldn't be a problem if you see this infrequently but drives reporting this error on a regular basis should be scheduled for replacement.

This is normally associated with the Fujitsu MAM3367MC drive and did not affect all of this drive type. Call Dell support and they will help with getting a replacement drive.

On the ID=6 listed as a processor in the controller BIOS, this is expected and is listing the drive backplane. It is seen by the controller as a processor device. If you didn't see this, you probably wouldn't see your drives. 

Yes, except that sense code=24.  I'm using Array Manager 3.4.0.

It shows up during every start up and generally there's about 3 instances of it in the event log each time.

I just want to be sure it's not going to cause any corruption problems.

Thanks,

Ingo