Storage Boards Cleanup
To make it easier to find information about HPE Storage products and solutions, we are doing spring cleaning. This includes consolidation of some older boards, and a simpler structure that more accurately reflects how people use HPE Storage.
Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

MSA 2312i vscrub failed after firmware upgrade

Luca
Advisor

MSA 2312i vscrub failed after firmware upgrade

We recently added a second controller to our 2312i. The partner firmware update was enabled so it started to flash Controller A. However it entered a continuous loop (it completed the flash process reporting success but then starting over after a few seconds) so we disabled it. Upon checking the firmwares they differed only in the Management Code Controller version. The original installed controller had version W441R06 while the newly installed one had W441R25 all the rest was identical. At this point we left the controllers as they were leaving the second unconnected with the following versions:

Controller A Versions
---------------------
Storage Controller CPU Type: Athlon 2600+ 1600MHz
Storage Controller Code Version: M111R06
Memory Controller FPGA Code Version: F300R22
Storage Controller Loader Code Version: 19.009
Management Controller Code Version: W441R06 *****
Management Controller Loader Code Version: 12.015
Expander Controller Code Version: 1109
CPLD Code Version: 8
Hardware Version: 53

Controller B Versions
---------------------
Storage Controller CPU Type: Athlon 2600+ 1600MHz
Storage Controller Code Version: M111R06
Memory Controller FPGA Code Version: F300R22
Storage Controller Loader Code Version: 19.009
Management Controller Code Version: W441R25 *****
Management Controller Loader Code Version: 12.015
Expander Controller Code Version: 1109
CPLD Code Version: 8
Hardware Version: 53

The following day, no scrub errors were logged and all was normal. We then downloaded the latest firmware from the hp support site (M111R06-07) and went ahead and flashed controller B manually first, which succeeded and subsequently flashed controller A which succeeded to the following versions:

Storage Controller Code Version M111R06
Memory Controller FPGA Code Version F300R22
Storage Controller Loader Code Version 19.009
Management Controller Code Version W441P28
Management Controller Loader Code Version 12.015
Expander Controller Code Version 1109
CPLD Code Version 8

We re-enabled the partner firmware update and everything looked normal and no update was triggered as expected. We then configured the second controller I/O interfaces (A1 same subnet as B1, A2 on B2) and connected them and configured the ESX 4.1 hosts accordingly and all seemed well.

However, the following vscrub we received the error:

2011-01-21 21:06:09 A1273 207 Scrub failed on vdisk : vd01, SN: 00c0ffd886b40000a5d31f4b00000000 1 parity mismatches were detected. If a disk fails data may be at risk. Action required - See Events Descriptions Reference Guide for recovery procedure

Then vdisk verification started and approx 10 hours later:

2011-01-22 07:26:13 A1285 21 Vdisk verification failed. Command failed. (error code: 1) 1 error(s) were found. (vdisk: vd01, SN: 00c0ffd886b40000a5d31f4b00000000)

There is only 1 error on this vdisk. What action would anyone recommend to take (apart from backing up the vdisk, destroying it and recreating it which is unthinkable of at this moment)?

I understand that the partner firmware upgrade looped most probably because it failed somehow to upgrade the Management Controller Code version - why though is a mystery. Possibly some bug in the revision of the second controller? Manually they both updated fine. This MSA has been running for over a year without any kind of problem.

Thanks for any feedback.
1 REPLY
Johan Guldmyr
Honored Contributor

Re: MSA 2312i vscrub failed after firmware upgrade

Hey,

just one scrub error is maybe not the end of the world.

If the amount of errors doesn't increase and you haven't seen any problems accessing any data (maybe run a file check on the file system?) I don't see why you have to re-build the vdisk at this moment.