Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

21962

March 30th, 2015 18:00

MD3000 slightly unwell?

Got  simple dual node Windows Cluster which uses MD3000 dual controller as shared storage. Very stable but I think the self-healing features of the storage may be masking a hardware fault.


Can anyone explain the log entries in more detail for me so I know what part to replace? Recovery guru says nothing is wrong but a 1707 critical alert was sent to the monitoring software so it's not all that happy.


Can't see how to attach the majoreventlog.txt file so pasting snippets from it...

Description: Controller tray component changed to optimal
Event specific codes: 0/0/0
Component type: Fan
Component location: Enclosure 0, Slot 0

Description: Controller tray component changed to optimal
Event specific codes: 0/0/0
Component type: Power Supply/Cooling Fan module
Component location: Enclosure 0, Slot 0

Description: Host card or switch card recovered successfully
Event specific codes: 0/0/0
Component type: Host Board

Description: Alternate controller checked in late
Event specific codes: 0/0/0
Component type: RAID Controller Module
Component location: RAID Controller Module in slot 0

Description: Destination driver error
Event specific codes: 0/0/0
Component type: Physical Disk
Component location: None
Logged by: RAID Controller Module in slot 0

Description: Destination driver error
Event specific codes: 0/0/0
Component type: Physical Disk
Component location: None
Logged by: RAID Controller Module in slot 0

Description: Start-of-day routine completed
Event specific codes: 0/0/0
Component type: RAID Controller Module
Component location: RAID Controller Module in slot 1
Logged by: RAID Controller Module in slot 1

Description: One or more Sundry regions created
Event specific codes: 0/0/0
Component type: RAID Controller Module Firmware
Component location: None
Logged by: RAID Controller Module in slot 1

Description: Host card or switch card recovered successfully
Event specific codes: 0/0/0
Component type: Host Board
Component location: None

Description: Start-of-day routine begun
Event specific codes: 0/0/0
Component type: RAID Controller Module
Component location: RAID Controller Module in slot 1
Logged by: RAID Controller Module in slot 1

Description: All connections established through wide port
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)

Description: Single connection established through previously failed wide port
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)

Description: Controller quiescence halted
Event specific codes: 0/0/0
Component type: RAID Controller Module
Component location: RAID Controller Module in slot 0

Description: Cache mirroring on controllers not synchronized
Event specific codes: 0/0/0
Component type: RAID Controller Module
Component location: RAID Controller Module in slot 0

Description: Destination driver error
Event specific codes: 0/0/0
Component type: Physical Disk
Component location: None
Logged by: RAID Controller Module in slot 0

Description: Degraded wide port becomes failed
Event specific codes: 0/0/0
Component type: Enclosure Component (EMM, GBIC/SFP, Power Supply, or Fan)

All these events happened between 1:03 and 1:05 AM. It's now 1:21 AM so I'm going to bed hoping someone can post an explanation of how to deal with it while I sleep. I can email the whole majoreventlog.txt in the morning if needed.


Thanks.

March 31st, 2015 13:00

Hello, Pondule.

Honestly from the surface, it looks and sounds like some simple firmware errors being accumulated, and an update might fix that. I generally see that when there's "destination driver error" and the Component location is "none". BUT, I'd like to take a deeper look and verify that. I sent you an email, and I'll wait for the full support bundle.

Let me know if you have any questions. Looking forward to hearing from you.

No Events found!

Top