Problem Document
|
Synopsis
|
Last Modified Date
|
1916789.1 |
Sun Storage 3000 Arrays: JBOD SES Device Links Are Missing |
2014-09-04
|
1601641.1 |
Sun Storage 3000 Arrays: How to Resolve the Degraded Status of a Redundant (RAID-5 or RAID-1) Logical Drive |
2017-09-19
|
1020286.1 |
Sun Storage 3000 Arrays: Smaller Stripesizes May Cause Slow Logical Drive (LD) Rebuild Time |
2014-03-12
|
1020033.1 |
Sun Storage 3000 Arrays: After Growing a Logical Drive (LD), New Size is not Reflected on Host |
2014-03-18
|
1012774.1 |
On Sun StorEdge 35xx Arrays running 3.27R firmware, setting the value 'Auto Global Spare' to enabled may result in existing Logical Drives to be lost |
2013-08-12
|
1012505.1 |
Sun Storage 3000 Arrays May Lose Data Host Access After Reporting "Memory Not Sufficient to Fully Support Current Config" |
2013-08-12
|
1011232.1 |
Recovering From a Failed SAF-TE Firmware Update on Sun Storage 33x0 RAID Arrays |
2013-08-12
|
1010855.1 |
Sun Storage 3310/3320/3510/3511 Arrays: Identifying and Resolving an Incorrect "Controller Unique Identifier" |
2013-08-12
|
1010521.1 |
Sun StorEdge 3310/3320/3510/3511: Running sccli command may result in SCSI timeouts |
2018-04-24
|
1010467.1 |
Sun StorEdge[TM] 33x0 and 35x0:Symptom:SCCLI Fails to Find Controller |
2017-01-04
|
1009967.1 |
Sun Storage 3000 Arrays: sccli Utility Reports "network connection setup failed" |
2013-11-12
|
1009497.1 |
Sun StorEdge 3310/3510/3511/3320: Resolving Data Unavailability issues due to different default Cylinder/Head/Sector settings after firmware upgrade. |
2013-08-12
|
1009343.1 |
SUNWjfca HBA will not have any bug fixes |
2018-01-08
|
1009322.1 |
Sun StorEdge[TM] 3310/3320/3510/3511 Array: Running concurrent/simultaneous se3kxtr scripts, may cause the array to hangup. |
2017-07-31
|
1008359.1 |
Sun StorageTek[TM] 3xxx Arrays - Unable to change controller assignment on LogicalDisk |
2013-08-12
|
1007691.1 |
[3310] ssmon can generate ASC: 0x29 (power on, reset, or bus reset occurred) |
2018-01-03
|
1006649.1 |
Sun StorEdge[TM] 3000 Arrays: 3.2x and 4.x Firmware Differences in Handling Media Errors |
2016-04-14
|
1006414.1 |
Sun StorEdge 351x/33x0 Arrays: Mute Button Held During Reset of Array Will Cause False Battery Failure Messages |
2017-12-11
|
1003547.1 |
Sun StorEdge[TM] 3510/3511/3310/3320: Getting "soft errors" reported by iostat |
2017-03-06
|
1003518.1 |
Resolving "NVRAM CRC Error: NVRAM Must be Reinitialized" on Sun StorEdge[TM] 3510 Array |
2015-05-08
|
1002332.1 |
Sun Storage 3000 Arrays: Checking the Actual Cache Status |
2013-08-12
|
1002296.1 |
Sun StorEdge[TM] 3310/3320/3510/3511: Duplicate disk entries from show disks output |
2014-05-09
|
1002220.1 |
Sun Storage 3000 Series Arrays: Events Logged For "Battery Board Not Fully Charged" |
2017-08-01
|
1001846.1 |
Sun StorEdge[TM] 3510/3511 FC Array/3310/3320 SCSI Array: Battery Display on Firmware GUI Appears to Be Incorrect |
2013-08-12
|