Problem Document
|
Former IBIS ID
|
Synopsis
|
Last Modified Date
|
1020286.1 |
255568 |
SE35xx and SE33xx arrays - causes for slow LD rebuilds |
2009-10-24
|
1020033.1 |
251226 |
SE3xxx - After growing LD, new size is not reflected on host |
2009-06-14
|
1012692.1 |
217449 |
Sun StorEdge [TM] 351x Array: Devices Missing from se3kxtr show_frus and show_ses-devices outputs due to Duplicate Box IDs |
2009-12-27
|
1012603.1 |
217345 |
Sun StorEdge[TM] 3000 series array: controller panic with message "WARNING: BBU cached data error!" |
2009-02-15
|
1012505.1 |
217226 |
Sun StorEdge[TM] 3000 family: Resolving "Memory Not Sufficient to Fully Support Current Config" problem. |
2009-09-21
|
1011981.1 |
216417 |
Sun StorEdge[TM] 3310:Unable to see a 3310 After Installing Patches and Rebooting |
2009-11-08
|
1011232.1 |
215427 |
Recovering From a Failed SAF-TE Firmware Update on Sun Storage 33x0 RAID Arrays |
2010-12-22
|
1010881.1 |
215020 |
Fujitsu Disk Firmware Upgrade fails with Patch 116815-07 on Sun Storage 3510 Arrays |
2010-11-29
|
1010855.1 |
214991 |
Sun Storage 3310/3320/3510/3511 Arrays:Identifying and Resolving an Incorrect "Controller Unique Identifier" |
2010-07-06
|
1010521.1 |
214456 |
Sun StorEdge[TM] 3310/3320/3510/3511: Running sccli command may result in SCSI timeouts |
2010-05-31
|
1010467.1 |
214381 |
Sun StorEdge[TM] 33x0 and 35x0:Symptom:SCCLI Fails to Find Controller |
2010-08-04
|
1009497.1 |
213111 |
Resolving Data unavailability issues in a Sun StorEdge[TM] 3310/3510/3511/3320 due to different default Cylinder/Head/Sector settings after firmware upgrade. |
2009-01-20
|
1009430.1 |
213031 |
Sun StorEdge[TM] 3310/3510/3120/3511 Array: Monitoring from more than one host using Sun StorEdge[TM] Configuration Service can cause the controller to not respond |
2009-01-19
|
1009395.1 |
212991 |
Sun StorEdge[TM] 3310: Some sccli commands run in-band give error: ?this operation is only supported on RAID primary controllers? |
2009-01-19
|
1009343.1 |
212925 |
SUNWjfca will not have any bug fixed |
2011-01-10
|
1009322.1 |
212902 |
Sun StorEdge[TM] 3310/3320/3510/3511 Array: Running concurrent/simultaneous se3kxtr scripts, may cause the array to hangup. |
2008-10-20
|
1009137.1 |
212646 |
Sun StorageTek[TM] 351x/33x0: Resolving Drive NONE USED status for Raid 5 logical drives |
2011-04-06
|
1008956.1 |
212345 |
Sun StorEdge[TM] 3310 (SE3310) - Solaris[TM] unable to see any mapped LUNs, or LUNs other than LUN 0 |
2009-02-18
|
1008359.1 |
211430 |
Sun StorageTek[TM] 3xxx Arrays - Unable to change controller assignment on LogicalDisk |
2009-03-10
|
1008108.1 |
211152 |
Sun StorEdge[TM] 3310, 3510 and 3511: Avoiding double drive failure conditions on 3.x firmware |
2010-01-12
|
1008091.1 |
211134 |
vxvm 3.5/4.0/4.1 hangs during install on systems with a Sun StorEdge[TM] 3310 running firmware rev 325W |
2009-09-22
|
1007982.1 |
211012 |
Sun StorEdge[TM] 3310 without configured lun0 shows narrow channel setting. |
2009-09-24
|
1007803.1 |
210793 |
Sun Storage 3510/3511/3310/3320:"sccli>show-disks" : disk has NONE USED status by RAID 1 |
2011-04-06
|
1007691.1 |
210658 |
[3310] ssmon can generate ASC: 0x29 (power on, reset, or bus reset occurred) |
2011-04-28
|
1006888.1 |
209553 |
Fujitsu (Allegro) drives in Sun StorEdge[TM] 3310 SCSI array connected with Ultra[TM] 320 SCSI HBA can cause scsi bus resets and transport errors. |
2011-01-18
|
1006649.1 |
209273 |
Sun StorEdge[TM] 3000 Arrays: 3.2x and 4.x Firmware Differences in Handling Media Errors |
2011-05-19
|
1006542.1 |
209143 |
Sun StorEdge[TM] 3310 SCSI Array/JBODs: Connecting to the onboard SCSI port on Sun Enterprise[TM] 3x00/4x00/5x00/6x00 servers may give SCSI errors |
2009-02-11
|
1006445.1 |
209034 |
Sun StorEdge[TM] 3310 SCSI Array: SCSI error message "f/w initiated BDR fails" |
2009-09-13
|
1004867.1 |
206829 |
Sun StorEdge[TM] 3310:Symptom:3310 not seen when connected to LVD SCSI-3 (jasper) HBA |
2009-09-13
|
1004789.1 |
206648 |
Sun StorEdge[TM] 3310:Symptom:ssconsole unable to discover array |
2009-02-12
|
1004782.1 |
206640 |
probe-scsi-all can see disks, but boot -r, devfsadm , and drvconfig, fail to add disks to OS |
2011-05-27
|
1004263.1 |
205891 |
Sun StorEdge[TM] 3310 SCSI Array: Unrecoverable media errors not passed to the host |
2009-03-01
|
1003771.1 |
205306 |
Sun StorEdge[TM] Diagnostic Reporter: "Server not online" error |
2009-09-23
|
1003736.1 |
205265 |
Avoiding SCSI transport errors while running explorer/extractor/sccli with Sun Storage 3310 Arrays |
2010-10-14
|
1003547.1 |
204988 |
Sun StorEdge[TM] 3510/3511/3310/3320: Getting "soft errors" reported by iostat |
2011-01-06
|
1003518.1 |
204945 |
Resolving "NVRAM CRC Error: NVRAM Must be Reinitialized" on Sun StorEdge[TM] 3510 Array |
2009-11-08
|
1002403.1 |
203365 |
Sun StorEdge[TM] 3310 Array: Controller Unique Identifier not properly updated with 1159/1170 SAF-TE firmware installed |
2009-02-11
|
1002332.1 |
203269 |
Checking the Actual Cache Status of The Sun Storage 3000 Array |
2010-11-15
|
1002296.1 |
203223 |
Sun StorEdge[TM] 3310/3320/3510/3511: Duplicate disk entries from show disks output |
2009-02-05
|
1002220.1 |
203139 |
Sun StorEdge[TM] 3000 Arrays: Battery Not Fully Charged |
2009-12-27
|
1001846.1 |
202529 |
Sun StorEdge[TM] 3510/3511 FC Array/3310/3320 SCSI Array: Battery Display on Firmware GUI Appears to Be Incorrect |
2009-11-08
|