Start a Conversation

Unsolved

This post is more than 5 years old

31831

September 20th, 2011 15:00

MD3000 disconnected - meaning of event log message?

Our MD3000 disconnected from its host recently. The 1st entry in the MD3000 event log at the corresponding time period is "Mode select for redundant controller page 2c received". EventType = 300D. what does this error message mean? It is not flagged as a critical error. Is this something that might happen when the unit is under a heavy I/O load?

946 Posts

September 29th, 2011 08:00

I don't see anything in the user guides for that...have you checked with support? They may be able to give you a quick answer. If not, try posting on the break fix forums below:

http://en.community.dell.com/support-forums/storage/f/1216.aspx

Hope that helps!

5 Posts

September 30th, 2011 20:00

Our IT department did open a ticket, but I didn't find the answer very satisfying:

"I opened a ticket with Dell support and gave them all the MD3000 storage logs. The ticket number is SR # 842247131. According to the Engineer, the logs showed that there is nothing wrong with the storage array although it showed the operating system getting disconnected at around 10:37AM. This caused the two RAID controllers to automatically run self-test diagnostics. No errors we're found. At this point, I'll keep the ticket open just in case. I don't think this is a hardware issue."

I was hoping that someone here could provide additional information on the 1st message logged at the time this incident occurred. It seems like the MD3000 would be responsible for this situation and not the OS.

2 Intern

 • 

847 Posts

October 3rd, 2011 09:00

"Our IT department did open a ticket, but I didn't find the answer very satisfying:

"I opened a ticket with Dell support and gave them all the MD3000 storage logs. The ticket number is SR # 842247131. According to the Engineer, the logs showed that there is nothing wrong with the storage array although it showed the operating system getting disconnected at around 10:37AM. This caused the two RAID controllers to automatically run self-test diagnostics. No errors we're found. At this point, I'll keep the ticket open just in case. I don't think this is a hardware issue."

I was hoping that someone here could provide additional information on the 1st message logged at the time this incident occurred. It seems like the MD3000 would be responsible for this situation and not the OS."
From my understanding of the 1st error?
The OS / Host(s) requested stand by pathing, instead of prefered pathing.

No Events found!

Top