Plugged in the serial cable, this is how far it get's:

Reset, Power-Up Diagnostics - Loop 1 of 1

3600 Processor DRAM

    01 Data lines                                                  Passed

    02 Address lines                                               Passed

3300 NVSRAM

    01 Data lines                                                  Passed

5900 Ethernet 91c111 #1

    01 Register read                                               Passed

    02 Register test                                               Passed

3A00 NAND Flash

    06 Bad Blocks Test                                             Passed

2310 Application Accelerator Unit

    01 AAU Register Test                                           Passed

6D00 LSI SAS 1068 IOC--Base Board

    01 IOC Register Read Test                                      Passed

    02 IOC Register Address Lines Test                             Passed

    03 IOC Register Data Lines Test                                Passed

6F01 QLOGIC EP4032 CHIP 0

    01 Register Read Test                                          Passed

    02 Register Address Lines Test                                 Passed

    03 Register Data Lines Test                                    Passed

3900 Real-Time Clock

    01 RT Clock Tick                                               Passed

Diagnostic Manager exited normally.

Current date: 12/10/14  time: 06:36:08

Send for Service Interface or baud rate change

12/10/14-14:30:24 (GMT) (tRAID): NOTE:  Set Powerup State

12/10/14-14:30:24 (GMT) (tRAID): NOTE:  SOD Sequence is Normal, 0

12/10/14-14:30:24 (GMT) (tRAID): NOTE:  SOD: removed SAS host from index 0

12/10/14-14:30:24 (GMT) (tRAID): NOTE:  In iscsiIOQLIscsiInitDq.  iscsiIoFstrBase = 0x0

12/10/14-14:30:24 (GMT) (tRAID): NOTE:  Turning on tray summary fault LED

12/10/14-14:30:26 (GMT) (tRAID): NOTE:  SYMBOL: SYMbolAPI registered.

esmc0: LinkUp event

12/10/14-14:30:27 (GMT) (tNetCfgInit): NOTE:  Acquiring network parameters for interface esmc0 using DHCP

^[[28~12/10/14-14:30:29 (GMT) (tRAID): NOTE:  Initiating Drive channel: ioc:0 bringup

12/10/14-14:30:32 (GMT) (tRAID): NOTE:  IOC Firmware Version: 00-24-63-00

Hello erichuyn,

Typically when you experience your issue it is usually due to one of the controllers being at a different firmware level then the controller currently in the MD3000i.  It normally sense if the new controller is at a lower version & will attempt to upgrade the controller to match the current controllers firmware but in your case it seems like the MDis not able to do so.  So what you can try to do is to put the newer controller into slot 0 and then perform a manual firmware upgrade.  Do you know what the current version of firmware you are running on your MD3000i currently?

Please let us know if you have any other questions.

Hi Sam,

the firmware was the first thing I did, should have mentioned that, because of possible problems.

File I used was MD3000i_FW_RC_07353860_1532.dlp. The 'old' controller works fine btw in any bay, it;s just when the new controller is introduced that things go haywire.

As mentioned I also connected the DELL serial cable and the data posted above is what the good controller spits out.

I've also learned this morning that the new controller just gives me a line of white blocks in Putty and then stops sending anything so I thing the controller is dead?

Last thing I tried today was to remove the battery in the new controller to see if it was a settings issues, but sadly that did nothing as well.