geneNZ

updated

17 years ago

G

geneNZ

21 Posts

0

136199

September 8th, 2009 21:00

MD3000i Physical Disk Channel Degraded Errors

Hi All,

Last night we had several critical error messages from one of our MD3000i's, that happened out of the blue.  These MD3000i's are used in an ESX4 environment.  The logs of interest are as follows:

Date/Time: 8/09/09 19:52:04
Sequence number: 623
Event type: 1707
Event category: Error
Priority: Critical
Description: Degraded wide port becomes failed
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:52:04
Sequence number: 621
Event type: 1707
Event category: Error
Priority: Critical
Description: Degraded wide port becomes failed
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:52:04
Sequence number: 622
Event type: 1706
Event category: Error
Priority: Critical
Description: Optimal wide port becomes degraded
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:52:04
Sequence number: 620
Event type: 1706
Event category: Error
Priority: Critical
Description: Optimal wide port becomes degraded
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:36
Sequence number: 607
Event type: 1513
Event category: Error
Priority: Critical
Description: Individual physical disk - Degraded path
Event specific codes: 0/0/0
Component type: Channel
Component location: Physical Disk-side: channel 1
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:28
Sequence number: 605
Event type: 1707
Event category: Error
Priority: Critical
Description: Degraded wide port becomes failed
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:28
Sequence number: 603
Event type: 1707
Event category: Error
Priority: Critical
Description: Degraded wide port becomes failed
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:28
Sequence number: 604
Event type: 1706
Event category: Error
Priority: Critical
Description: Optimal wide port becomes degraded
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:28
Sequence number: 602
Event type: 1706
Event category: Error
Priority: Critical
Description: Optimal wide port becomes degraded
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)
Component location: Enclosure 0, Slot 0
Logged by: RAID Controller Module in slot 0


Date/Time: 8/09/09 19:51:15
Sequence number: 598
Event type: 1209
Event category: Error
Priority: Critical
Description: Physical Disk channel set to Degraded
Event specific codes: 0/0/0
Component type: Channel
Component location: Physical Disk-side: channel 1
Logged by: RAID Controller Module in slot 0

 

The errors occurred under normal load, and nothing special was going on.  The errors that concern me are:

1) Physical Disk channel set to Degraded
2) Individual physical disk - Degraded path

I understand that the "Optimal wide port becomes degraded" and "Degraded wide port becomes failed" is a result of controllers rebooting.  The reboots presumably were as a result of the two above error messages.  

What I would like to find out is what do these Channel errors mean.  Note that since these errors occurred, the arrays are now back in 'Optimal' State, and there is nothing of interest on the Recovery Guru.  There has been no issue over the past 20 hours (fingers crossed it stays up).  I have opened a case with Dell, and they are investigating, but I would like to check with the community also. 

Thanks in advance.

Gene

  • Pawn33

    28 Posts

    1697

    1

    Posted September 9th, 2009 18:00

    Yeah, with the destination drive errors, if the location on that error = None , that is a firmware glitch and is currently being worked on by engineering to fix that issue.

    If the unit is reporting running optimal , i would not worry about any problems. The md3000/3000i is really good about alerting you if there are apparent problems.

  • Pawn33

    28 Posts

    1697

    0

    Posted September 9th, 2009 16:00

    The Event types -1706-1707 are communication loss between the storage unit and the MDSM software. Nothing to be to concerned over .

    As for the other events, The physical disk channel errors might indicate a disk problem. What kind of drives ?SAS/Sata? The degraded disk channel happens once one of the Raid controllers accumilate a certain amount of disk errors. there is a SMcli command to clear that out. You can find the commands here--

    But you may have a problem with the disk it is pointing to .

  • geneNZ

    21 Posts

    1697

    0

    Posted September 9th, 2009 17:00

    Thanks for your information,

    We have SAS Disks

    This is the first occurence we have seen of this problem, and slightly before these error messages, I noticed there were 3 'Disk Destination Errors'.  I contacted Dell about these 'Disk Destination Errors' last week, and they have indicated that it is normal behaviour. 

    Problem is I can't find out what physical component is at fault, since the MD is reporting Optimal with no errors.  So I can't determine whats at fault.  Any ideas?

  • geneNZ

    21 Posts

    1697

    0

    Posted September 10th, 2009 20:00

    Thanks for the reassurance.

    Our "Destination Drive Errors" are pointing to the location "None" as stated.  I'll keep monitoring the situation, but the MD is still reporting optimal.

    Thanks again.

    Gene