SL8500 - Library Failure, Invalid Partitions After RE Switch and/or Reboot of Library or Complex

Asset ID:	1-72-2282723.1
Update Date:	2018-05-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2282723.1 : SL8500 - Library Failure, Invalid Partitions After RE Switch and/or Reboot of Library or Complex

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

MV-Pool definition clashes with Partition definitions.
SL8500 complex of four (4) SL8500s with MV Pool and Partitions defined running firmware FRS_8.59b.
Partitions found invalid after reboot of SL8500 library.

Symptoms

Auto RE switch took place from HBCR-A to HBCR-B.

the following event is an example of the related logging

2017-06-22T10:08:20.570, 1.0.0.0.0, root, default, internal, 0,error, 3204, "System error - Found mismatch among configuration file in thecomplex libraryId = 2, partitionConfigurationVersion = 0,
mediaValidationConfigurationVersion = 14 libraryId = 3,partitionConfigurationVersion = -1, mediaValidationConfigurationVersion =-1 libraryId = 4, partitionConfigurationVersion = -1,
mediaValidationConfigurationVersion = -1, Taking all the libraries in the complex OFFLINE"

Changes

This issue most likely only occurs if following facts are true.

1. SL8500 complex on firmware version FRS_8.5x.
and
2. COMPLEX wide partitions exist.
and
3. MV Pool (Media Validation) pool has been created.

Cause

SL8500 complex never comes ready due to partitions being invalid.

Partition definition and MV pool assignment corrupt after reboot due to MV Pool id value <mvConfigurationVersion> not being in sync across the complex.

For example:
Lib1 and 2 <mvConfigurationVersion> of 23
Lib3 and 4 <mvConfigurationVersion> of 8

Solution

At current status this appears to be a firmware related issue which will be addressed in the future.

Currently there is no soft non-disruptive way out of this condition.

In all cases contact Library L2 support in order to assist with the fix.

For reference please see bug 26332835

Bug 26332835 - Met Office Unexpected switch resulted in partition config error

Recommended Action Plan:

Tested with SLC FRS_6.65 and it worked also. You may lose capacity ( active cells ) after you allow the SLC to remove partitions and MV pool. So this is the procedure to recommend.

1. Reboot the complex or a library, if you only reboot a library you must login with SLC to that one after the reboot.

2. Attempt to enter MV or partition screen, you should get a dialog box that wants to reset partitions and remove MV pool. Select that, after 1 or 2 minutes then you may see a request for a retry, I selected that also. After approximately another 2 minutes that should finish.

3. At this point the library should have no partitions or MV pool. You also will probably not have any capacity.

4. I decided to recover capacity first at this point. SLC still being up from previous steps had "select active cells" disabled, so I logged off of SLC and logged back on then it was enabled. I applied capacity to all libraries in the complex successfully.

5. Then I proceeded to apply MV pool and partitions, should not matter which you do first, I did both ways with no problems.

6. Assuming those steps occurred with out errors, then you can do a reboot test to show that it is possible to reboot without invalid partitions.

Final fix will be in 6.70 firmware.

Attachments

This solution has no attachment