Healthck on an A3500FC reports a failed controller even though all other indications are to the contrary. Additionally, not all disks are visible in the RM6 Configuration GUI.

Make sure that you can create LUNs on both controllers, newfs and mount them, then send I/O to them. If this works, it is an obvious message that the controllers are fine. Look carefully at the output of a Save Module Profile. In the particular instance used as an example below, controller A reported itself as an A1000, while controller B showed itself properly as an A3500FCd:

Number of Drives = 8

Parameters Controller A (c2t5d0) Controller B (c1t4d1)

Board Name: Series 3 Series 3

Board ID: 3702 3702

Board Serial Number: 1T03700794 1T03702035

Product ID: StorEDGE A1000 StorEdgeA3500FCd

Often, if an A3500 is upgraded to a 3500FC, the change does not update the NVSRAM, and is thereby not reflected in the product ID field (see bug ID 4310356 for further information) of the module profile. Patch 109232-01 was created to remedy this problem. Even though this was not an upgrade, downloading and applying the patch allowed all disks to be seen, and stopped healthck from reporting a failed controller.

• R.B. Khleif, Storage TSE