| Alert
|
Synopsis
|
Last Modified Date
|
| 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
|
| 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
|
| 1000652.1 |
Sun StorEdge 3310/3510/3511 Disk Rebuild Operation Fails to Complete |
2012-07-27
|
| 1000500.1 |
Dual-Bus Sun StorEdge 3310 JBOD Configurations May Lose SCSI Termination in a Multi-Initiator Environment |
2012-07-27
|
| 1000319.1 |
Data Inconsistencies May Occur When Persistent SCSI Parity Errors are Generated Between the Host and the SE33x0 Array |
2012-07-27
|
| 1000307.1 |
Sun StorEdge 3310 Controller With Firmware 3.66 Cannot Cross-Load With 3.25 Firmware |
2012-07-27
|
| 1000296.1 |
For Sun StorEdge 3310, Running SSCS and sccli(1M) In-Band at the Same Time May Cause SCSI Errors |
2012-07-27
|
| 1000221.1 |
Sun StorEdge T3 and Sun StorEdge 3310 SCSI Array's Controller May Disable Without Warning When Probed with Third Party Network Security Software |
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
|
