Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Sun Alert Sure Solution 1000881.1 : Disk Drives DK32EJ36N (36GB) and DK32EJ72N (72GB) With Firmware PQ08 in Sun StorEdge A1000, A3x00, S1 and D240 Arrays May Become Unavailable After a System Reboot
PreviouslyPublishedAs 201167 Product Sun StorageTek D240 Media Tray Sun StorageTek S1 Array Sun StorageTek A1000 Array Sun StorageTek A3000 Bug Id <SUNBUG: 4960420> Date of Resolved Release 04-MAY-2004 Impact Disk drives DK32EJ36N (36GB) and DK32EJ72N (72GB) with firmware PQ08 in Sun StorEdge A1000, Sun StorEdge A3x00, Sun StorEdge S1 or Sun StorEdge D240 arrays may become unavailable after a system reboot. Contributing Factors This issue can occur in the following releases: SPARC Platform
Note: This issue only occurs when the above mentioned drive types are in the StorEdge A1000, Sun StorEdge A3x00, Sun StorEdge S1 or Sun StorEdge D240 arrays. To determine the disk firmware revision level, see the specific installation instructions included with the above patches for information on running the firmware download utility. To determine if a Sun system contains this drive type, run the format(1M) command as "root", and use the "inquiry" option from the format menu as shown in the following example: # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0d0 <DEFAULT cyl 611 alt 2 hd 16 sec 38> /pci@19,700000/pci@3/SUNW,isptwo@4 1. c1t1d0 <DEFAULT cyl 1463 alt 2 hd 9 sec 64> /pci@18,700000/pci@3/SUNW,isptwo@4 Specify disk (enter its number): 1 selecting c1t1d0 [disk formatted] FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table ... inquiry - show vendor, product and revision volname - set 8-character volume name quit format> inquiry Vendor: <NAME> Product: DK32EJ36N SUN36G Revision: PQ08 format> quit Symptoms Should the described issue occur after a system reboot, error messages similar to the following may be displayed at the console: interrupt: NOTE: WARN: Failing device 0x2 due to FATAL I/O timeout, opcode= 0x1b interrupt: WARN: interrupt: Received bus reset on channel 0 WARN: DST: timeout on device 00000002, ticks 0x00000FCD WARN: DST: op 02dd1c04, tag 00, opcode 1b, retries 1 ... ... WARN: Failing device 0x2 due to FATAL I/O timeout, opcode= 0x1b interrupt: WARN: interrupt: Received bus reset on channel 0 WARN: DST: timeout on device 00000002, ticks 0x00001EF3 WARN: DST: op 02dd1c04, tag 00, opcode 1b, retries 1 Workaround There is no workaround. Please see the "Resolution" section below. Resolution This issue is addressed in the following releases: SPARC Platform
Modification History Date: 14-JUN-2005 Change History14-Jun-2005:
References<SUNPATCH: 116369-04><SUNPATCH: 116370-04> Previously Published As 101486 Internal Comments
Internal Contributor/submitter [email protected] Internal Eng Business Unit Group NWS (Network Storage) Internal Eng Responsible Engineer [email protected] Internal Services Knowledge Engineer [email protected] Internal Escalation ID 549186 Internal Resolution Patches 116369-04, 116370-04 Internal Sun Alert Kasp Legacy ID 101486, 57549 (Sun Alert) Internal Sun Alert & FAB Admin Info Critical Category: Data Loss, Availability ==> Pervasive Significant Change Date: 2004-05-04 Avoidance: Patch Responsible Manager: [email protected] Original Admin Info: [WF 14-Jun-2005, Dave M; update CF, Product, Impact for additional affected products per ENG and customer] This document has been imported from KMS Creator and may need adjustment before re-publishing. This imported document has been reviewed/adjusted by: Review Name: Review Date: Original KMS Creator attributes below: --- PLEASE DO NOT MAKE ANY CHANGES BELOW THIS LINE! --- Sun Alert ID: 57549 Synopsis: Disk Drives DK32EJ36N (36GB) and DK32EJ72N (72GB) With Firmware PQ08 in Sun StorEdge A1000 or Sun StorEdge A3x00 Arrays May Become Unavailable After a System Reboot Category: Availability, Data Loss Product: Sun StorEdge A1000, Sun StorEdge A3x00 BugIDs: 4960420 Avoidance: Patch State: Resolved Date Released: 04-May-2004 Date Closed: 04-May-2004 Date Modified: Escalation IDs: 549186 Pending Patches: Resolution Patches: 116369-04, 116370-04 FIN: I1076-1 FCO: Date Submitted: 14-Apr-2004 Submitter: [email protected] Responsible Engineer: [email protected] Responsible Manager: [email protected] CTE group: PTS NWS US Responsible Writer: [email protected] Distribution: Public SunSolve Workflow History: WF State: Issued, 26-Apr-2005, Karen Edwards WF Note: i changed the Product WF State: Issued, 04-May-2004, David Mariotto WF Note: released WF State: Draft, 04-May-2004, David Mariotto WF Note: Approved by PTS, sending for release WF State: Draft, 04-May-2004, David Mariotto WF Note: Sending for signoff WF State: Draft, 03-May-2004, David Mariotto WF Note: Both READMEs are OK now. Sending for review, 9am WF State: Draft, 27-Apr-2004, David Mariotto WF Note: Younan sez one of two READMEs are corrected, would like to release by end of week. WF State: Draft, 22-Apr-2004, David Mariotto WF Note: Still waiting to hear back on README corrections. WF State: Draft, 15-Apr-2004, David Mariotto WF Note: Sent to Younan, requested fix for README WF State: Draft, 15-Apr-2004, David Mariotto WF Note: Waiting on addtl information and for BugID to appear in the patch README. Everyone has been notified. No README, no release. WF State: Draft, 15-Apr-2004, David Mariotto WF Note: Article created. Exported from KMS Creator Sat May 21 09:09:52 2005 GMT, [email protected] Internal SA-FAB Eng Submission Disk Drives DK32EJ36N (36GB) and DK32EJ72N (72GB) With Firmware PQ08 in Sun StorEdge A1000 or Sun StorEdge A3x00 Arrays May Become Unavailable After a System Reboot Product_uuid 2a5eee34-0a18-11d6-831b-82d1fe840b21|Sun StorageTek D240 Media Tray 2a6a1264-0a18-11d6-85f5-ebacf433bde4|Sun StorageTek S1 Array 2a792916-0a18-11d6-8d0a-c3d03933af3c|Sun StorageTek A1000 Array 2a7ca41a-0a18-11d6-82f2-e96014c515ea|Sun StorageTek A3000 ReferencesSUNPATCH:116369-04SUNPATCH:116370-04 ReferencesSUNPATCH:116369-04SUNPATCH:116370-04 Attachments This solution has no attachment |
||||||||||||
|