Many of the following SRDBs were created initially for the Sun StorEdge
9910/9960 Array, but they may also pertain to the 9970/9980 Array.
||Sun StorEdge[TM] 9900:Error: Installation of Additional Parity Group[s] Fails due to Insuficient License Capacity
||Sun StorEdge[TM] 9900 HiCommand Software:Symptom:2.1 Fails to Reflect new LDEVs after adding DKU
||Mapping a Sun StorEdge[TM] 9900 WWN to port location.
||Sun StorEdge[TM] 9900 Shadowimage error "No allotable reserved volumes"
||Sun StorEdge[TM] 9900 and Solstice Disksuite[TM]:Symptom:Metainit Errors out Stating That one Device is Overlapping
||SE99x0 ENVIRONMENTAL ERROR SIM identifies multiple hardware
failures; Cause may be bent pin
||Sun StorEdge[TM] 9900:Symptom:Command Device Type does not show Label Correctly in Format for 9900v System
||Sun StorEdge[TM] 9970/9980 System: Symptom:Does not see Recently Added LUN
||Sun Cluster[TM] 3.0: HDS 99xx with ASC=25 error causes Veritas Volume Manager hangs
||Sun StorEdge[TM] 9900 (99x0 Product line) - cfgadm -al reports uncon
figured failed with SE9960 connected
||ShadowImage / Sun StorEdge[TM] 9900 TruCopy pair sync status never shows 100%, stays at 99%
||SE99x0: Multiple Disks Failing in same HDU;
Same disk slot fails consistently
||Why can't I see newly mapped LUNs on a Sun
StorEdge[TM] 9900 series array?
||Sun StorEdge[TM] 9900 Series Remote Console
does not accept password after installation.
||Tru64 4.0x cannot see Hitachi luns, but Tru64
||FD REMAINS IN FDD error on SE9900 series array
||Sun StorEdge[TM] 9900 Series DKC does not power
down at end of installation
||Solaris[TM] missing LUNs 8 and 9 with Sun StorEdge[TM]
||Why can't I see newly mapped LUNs on a StorEdge