VC keeps failing to activate during firmware updates

[bradshr]

I have had a couple of enclosures updating firmware from 3.18 to 3.60. Both times, the update has frozen up during activation. The first time, the VCSU timed out and reported one module not updated. From checking the logs, I found that that the active module 1 failed over to module 2 then waited for module 1 to sync.  It looped like this for 1.5 hours before timing out.

[Thu Jun 07 16:31:51 2012] (1984)[VcsuCore.cpp:3325] : VCM configuration is not in sync
[Thu Jun 07 16:32:51 2012] (1984)[VcsuCore.cpp:3327] : Retrying again
[Thu Jun 07 16:33:37 2012] (1984)[VcsuCore.cpp:4473] : checkCheckPoint SUCCESS
[Thu Jun 07 16:33:37 2012] (1984)[VcsuCore.cpp:4473] : ErrorCode :0 Error :The operation was successful
[Thu Jun 07 16:33:39 2012] (1984)[VcsuCore.cpp:4496] : Check Point is VALID
[Thu Jun 07 16:33:39 2012] (1984)[VcsuCore.cpp:3319] : Checkpoint Validation Succeeded
[Thu Jun 07 16:33:39 2012] (1984)[VcsuCore.cpp:1955] : Primary VCM found in enclosure GB8807BNAX, bay 2
[Thu Jun 07 16:33:40 2012] (1984)[VcsuCore.cpp:648] : Module interface compatibility version: 2.00

I restarted module 1 and it completed its firmware update.

My question is: given that this seems to keep happening, is there any way of finding out what the modules are doing during a firmware update. My second enclosure update has frozen at 40% like the last one. I dont really want to wait another 1.5 hours for it to time out and dump the entries above in the VCSU log. The VCSU log is not giving me any useful info at the moment(in real time). The system log on the active module 2 is also not useful. Is there anything else I can do to check the status of module 1 in real time? I want to know if I can restart the module if it is not activating.

[Casper42]

This was a known bug in 3.60.
If you updated to 3.30 first and then to 3.60 it would have worked fine.

The workaround is either that or to use Manual Activation if you want to jump straight to 3.60.
If anyone else hits this you can manually reset the module that won't activate from the OA and it will give it the kick in the rear it needs to finish.

[Torsten.]

>> If you updated to 3.30 first and then to 3.60 it would have worked fine.


or

If you updated to 3.51 first and then to 3.60 it would have worked fine.



Meanwhile the version 3.70 resolves this issue.