MSA1000 hosed itself when expanding array

[leeph]

Added 3 disks to an MSA1000.

Asked it to expand the entire existing array to include the new disks.

Started off OK, then my ESX server lost lost contact with the disks - after waiting a while and rebooting the ESX servers, they report no partition information for the LUNs. Totally hosed itself.

The only other thing I did was issue a command to add a hot spare to the array just after issuing the command to expand and checking that this was in progress.

Is that a big no-no?

If it can't be done (or isn't recommended) why doesn't the CLI refuse to add the spare while an expansion is in progress? I was just trying to save myself time.

Don't see that the MSA1000 is fit for production use if it can hose itself this easily.

leeph

[Jefferson Humber]

Leeph,

What do the LUNs look like from the MSA CLI, are they all online and healthy (The output from SHOW TECH_SUPPORT would be handy) ? Is the unit reporting any issues, what about on the LCD on the controllers ?

I assume you are running v4.48 firmware ?

J

[leeph]

The output from the CLI shows the LUNs are healthy - some of them continue to rebuild their parity status, but at no point did the CLI report that there was a major failure - which is rather worrying as there clearly was one!

Yes, I am running the 4.48 firmware.

The only indication that there was a problem was that when I keyed in the hot spare command, the CLI reported something about LCP timeout I think. At that point, the drives in the storage box started blinking and the ESX servers lost access to their logical drives.

Please see attached tech_support output.