| Alert
|
Synopsis
|
Last Modified Date
|
| 1017421.1 |
Using Certain sccli(1M) Commands to Manage a Sun StorEdge 3510 or 3511 Fiber Channel Array May Cause the Controller to Hang |
2012-07-27
|
| 1001239.1 |
Sun StorEdge 3310/3510/3511 FC Array Controllers May Incorrectly Offline Drives |
2012-07-27
|
| 1001199.1 |
DRAM Parity Errors or SDRAM ECC Errors on Sun StorEdge 3310, Sun StorEdge 3510 or 3511 FC Arrays May Cause File System Integrity Issue |
2013-03-04
|
| 1001167.1 |
Sun Cluster 3.x Nodes May Panic Upon Controller Failure/Replacement Within Sun StorEdge 3510/3511 Arrays |
2012-07-27
|
| 1001061.1 |
Performance Degradation Reported in Controller Firmware Releases 4.1x on Sun StorEdge 3310/351x Arrays for All RAIDTypes and Certain Patterns of I/O |
2012-07-27
|
| 1001052.1 |
Logical Drives May be Lost if "auto-global-spare" is Enabled |
2012-07-27
|
| 1000856.1 |
Disks May be Marked as Bad Without Explanation After "Drive Failure," "Media Scan Failed" or "Clone Failed" Events |
2012-07-27
|
| 1000703.1 |
Loss of Access to 3510 or 3511 FC Storage After Power Cycle of Host Using 1 Gb PCI Dual FC Host Adapter(+) HBA |
2012-07-27
|
| 1000652.1 |
Sun StorEdge 3310/3510/3511 Disk Rebuild Operation Fails to Complete |
2012-07-27
|
| 1000559.1 |
SE3310/SE3320/SE3510/SE3511 Storage Arrays May Experience Data Integrity Events |
2012-07-27
|
| 1000382.1 |
Sun StorEdge 3510/3511 Arrays May Fail to Boot Upon Reset/Power Cycle When Connected in a Sun Cluster 3.x Environment With 3+ Nodes |
2012-07-27
|
| 1000318.1 |
Sun StorEdge 3511 Array with SES Devices Using DP0554e Firmware may go Offline |
2012-07-27
|
| 1000281.1 |
Sun StorEdge 3510 JBOD or 3511 RAID Connected With LP10000 HBA May Experience I/O Interruption |
2012-01-31
|
| 1000192.1 |
Logical Volumes Created With 3.27x Firmware Are Incompatible with 4.11I Firmware |
2012-07-27
|
| 1000006.1 |
Changing the Cache Optimization Mode Incorrectly on Sun StorEdge 3310, 3510 or 3511 May Cause Issues Affecting Filesystem Availability and Data Integrity |
2012-07-27
|
