Dual 5302 in a ML530

[Nick Hromyak]

I can't get a second array controller to recognize one of my arrays.

I have a mirror(2 drives - 9.1GB) and a RAID-5 (4 drives 72 GB) in one cage on one channel.

Then in the other cage, I have RAID-5 (six drives) in the other cage on the other channel.

I want to reduce my DISK ques from my SQL server using another 5302 controller.

When I put the second 5302 controller in, I have tried different channels on each controller, but no matter what, the CAGE-2 six drives are recognized, but NOT the ARRAY.

Suggestions?

Both controllers are on 3.54 (latest) firmware. The drives that are NOT being recognized are on B020 and the latest is B022A (36.4GB drives)

[Oleg Koroz · Accepted solution]

Assuming your system Completely Up to Date.
Steps:
1. Disconnect second Cage from Controller A !
2. Install Controller B in server
3. Update F10 Partition with Newly added HW
4. Power Up to O/S â access to ACU delete Array from CAGE B
5. Power Down server
6. Reconnect SCSI cable from Controller B to Cage B
7. Power Up accept drive Position has been changed
8. Should work

[Oleg Koroz]

Step 4 should be read as:
4. Power Up to O/S, access to ACU delete failed Array from CAGE B if it shows up still

[Nick Hromyak]

Curious, is it because the array is not deleted from Controller A that it doesn't show up on post?

The drives show up, just not the array.

Thanks for the clarification.

[Oleg Koroz]

Do you have any problems with seeing both array's if Controller B used Instead A ?

[Nick Hromyak]

I am not sure if we tried BOTH arrays on controller B.

We did try swapping arrays around f
Controller A port2 Array C vs
Controller A port1 Array C
and with
Controller B port1 Array C vs
Controller B port 2 Arrray C

Drives are always recognized not sure if the array was though. I actually didn't do the work, my colleague did. :/

Previously, we went through one bad array controller (a B controller). It was replaced in warranty, now we are trying it again (third time).

[Oleg Koroz]

If you do have access to Cage A&B with Controller A, try on your Own all steps as Listed.

[Nick Hromyak]

I just found out, the person who did this, deleted the array from Controller A in the BIOS (F2) for array controller.

Would this be the same as doing it in the Array Configuration Utility (ACU)?

Or would it be different?

[Oleg Koroz]

As you see step #1 Disconnect Cable from Cage B, where when you boot from ACU maximum what you see is failed Array, however you don't have access to it.
When Cable disconnected you only Modify RIS table for Array Configuration around all drives, but you don't loose data.
Where at reconnecting Cable: Back to Controller Redetect Previous Array and automatically Update RIS.

If Cable was connected all Delete option from F8 or ACU will destroy actual Array.
Than you right; you will see all Drives, but no Logical Drives.
First Sign from POST: if Array Detected, is #x of Logical Drives.

[Nick Hromyak]

Steps performed previously:

1. Power down server
2. Disconnect second Cage from Controller A
3. Install Controller B in server
4. Update F10 Partition with Newly added HW
5. POST to ARRAY Controller BIOS delete Array from Controller A
6. Power Down server
7. Reconnect SCSI cable from Controller B to Cage B
8. Power Up Server, Controller A recognizes two Arrays, Controller B recognizes drives, but not the third array.

So in the steps you outlined, is changing the ACU for the array the same as changing the array in the Array Controller's BIOS?

1. Disconnect second Cage from Controller A !
2. Install Controller B in server
3. Update F10 Partition with Newly added HW
4. Power Up to O/S â  access to ACU delete Array from CAGE B
5. Power Down server
6. Reconnect SCSI cable from Controller B to Cage B
7. Power Up accept drive Position has been changed
8. Should work

Thanks for your replies, just trying to get a handle on this, before our maintenance w