MD3220 will not bring up Service Interface

Hello Dan,

What you can try to do is to remove one of the controller on the MD3220 & boot it with a single controller in it.  Once it has finished booting then you can insert the second controller and it should clear the error.  If the error still remains then I would suggest that you contact support and open a case as they will need the serial cable attached to the working controller so that they can reset the MD & clear the error.

Please let us know if you have any other questions.

Is it possible to swap controllers between the MD3220 units, to see whether the issue you are getting follows the controller, or whether it stays where it is?  That would at least tell you whether the controller is at fault, or whether the problem is in the MD3220 chassis somehow (i.e. the I/face where the controller plugs in).

Yes, I've tested every module in a single array since I last posted. Two of the modules work, the other five give the same error. I tested them in another array to be safe and the modules all behave consistently.

I should probably test all the arrays with the good modules to be thorough, but there is clearly something wrong with modules. I just hope it's something I can set rather than bad hardware.

I think you're going to have to get some assistance direct from Dell's engineering people.  Sounds like either (a) the firmware in the controller(s) is incompatible with whatever is in the chassis (probably unlikely); or maybe (b) they got 'fried' in some kind of electrical event and maybe the firmware needs to be reloaded on them from scratch?  I'm not an engineer, just a customer, so I'm usually stuck with a strategy of "plug it in; if it doesn't work, call Dell".

These are out of warranty from Dell. We decided to go back our vendor and see if we can't get a solution or replacements. Thanks for everyone's help.

Did you ever get any answers? I am in a similar situation with a handful of MD3200s and 3220s (same controllers). I have had success with lemClearLockdown on a few of them. But I have a whole stack of controllers that give a different lockdown code, SODReboot Lockdown state.

I cannot do anything to them at this point, cannot enter the service interface,  I get the prompt after CTRL+Break but shift+S takes me nowhere, it never asks for the password. I don't even get a console, I cannot enter even the most basic commands through serial. There is no cursor, it just lets me enter text into puTTy but nothing happens. That is why these are dead in the water, I can ping them all day, but MDSM doesn't pick them up. I have one controller that works fine, I have been swapping it simplex/duplex and trying the other controllers. (have tried 5+ chassis and multiple sets of HDDs)

Anyway, they do not just magically mirror like the MD3KxS do when you simplex/duplex them and re-install the "faulty" controller. I've got one MD32XX under warranty so I believe I will have to go into chat.

Hello JW,

Have you tried to remove the raid battery from the controllers?  If not then what you can do is to remove the controller from the back of the MD and then remove the raid battery & leave it out for about 10 minutes.  Once that is done then put the raid battery back into the MD controller and put the controller back into the MD and then power on the MD & see if it completes post & comes up will both controllers online and Drives online as well.

Please let us know if you have any other questions.

Hi friends

I have the similar problem MD3200i with controllers in LockDown mode but I can´t get the prompt from serial console to run clearlockdowm command ( I press shift+S but nothing happens ). Can You help me ?

Tks

MarcioLM

Hello marciolm10,

What is the Baud rate that you are using to connecting to your MD3220?  You should be using 115200-8-n-1.  Also, terminal emulation software to make the connection?  Last is which lockdown state are you showing on your controller?

Please let us know if you have any other questions.