Sun Storage 9990 System
 
Sun Storage 9985 System
 

GCS>Sun Microsystems>Sun FAB>Standard>Reactive
 

New Parity Group installs which cause the number of PDEVs in the RAID500's Shared Memory PDEV table to exceed 2560 total PDEVs may result in the configuration data for Parity Group 1-1 being compromised. The PDEV entries in the SM table can consist of any the following:

• Existing RAID500 internal Parity Groups. Each HDD in a parity group is considered a single PDEV in the SM table.
• External Storage Groups that are assigned to the RAID500 as external storage. Each External Storage Group is entered into the RAID500 SM table as a single PDEV.
• New installation of additional RAID500 internal Parity Groups. Each HDD in a parity group is considered a single PDEV in the SM table.

For this issue to occur ALL the following must be satisfied:

1. Microcode level lower than 50-04-44-00/00
2. The installation of additional Parity Groups internally in the RAID500 causes the sum of the number of all entries in the RAID500 Shared Memory PDEV Table to exceed 2560.
3. After the new parity group installation fails, the CE attempts the internal parity group installation a second time.

Note: The attachment to the RAID500 of additional External Storage Groups will not cause this issue to trigger, only adding internal storage.

The new Parity Group(s) addition will fail with the message ONL2231E - "Logical error has occurred". After that, the Maintenance Status window on SVP may display the original Parity Group 1-1 as X-1 incorrectly and the RAID level may also show incorrectly (for example Raid 5 may show as Raid 1), which will be inconsistent with the original configuration information for PG 1-1. If you repeat of the same PDEV addition again the configuration information of Parity Group 1-1 becomes abnormal.

If you have attempted a parity group installation and this condition occurs do not perform drive maintenance or DCR settings. Please turn off Dynamic Sparing and Correction Copy from SVP screens until the subsystem has been recovered. This will avoid the possibility that data integrity might be lost due to the abnormal configuration information. Once this condition has been triggered escalate this issue to PTS for a resolution action plan.

The fix for this issue is located in microcode level 50-04-44-00/00 and higher. In order to prevent this condition from occurring, microcode should be verified to be at least this level prior to attemping an upgrade that will trigger this condition.

None.

• URL: http://pts-americas.west/nws/products/T99x0/documentation.html
  http://sejsc.ebay/AL/USP_044672R4.htm

This solution has no attachment