Asset ID:	1-72-1003576.1
Update Date:	2010-08-04
Keywords:

---

Solution Type  Problem Resolution Sure

Solution  1003576.1 :   Disk Subsystems: Disconnected Command Timeouts on Seagate Drives.  


PreviouslyPublishedAs
205033

Symptoms
If your system is using Seagate disk drive types ST39103LC or ST318203LC,
you may see a disconnected command timeout message similar to this one:

Nov  1 08:47:37 TM220   Disconnected command timeout for Target 0.0
Nov  1 08:47:37 TM220 genunix: [ID 408822 kern.info] NOTICE: glm0: fault
detected in device; service still available
This appears to be a disk firmware problem, and can be corrected with appropriate upgrades.

Resolution
Seagate disk drive types ST39103LC and ST318203LC that are at firmware revisions 034A, 054A, or 054B can cause the problem described in the problem statement.

To correct the problem, install these firmware revisions as per patch 113669-01 for each disk drive type.
That is:
* To fix the ST39103LC drive, upgrade to the 074B firmware revision.
* To fix the ST318203LC drive, upgrade to the 074A firmware revision.

Additional Information
Refer to patch:

13669-01.
Note: The patch 113669-01 doesn't mention any specific bugs fixed relating to the problem but if we see the drive page from the vendor, there are some bugs that fixed in this patch which are related to the above problem.

Product
Disk Subsystems
Sun StorageTek 9176 Disk Subsystem
Sun StorageTek BladeStore Disk Subsystem
Sun StorageTek D173 Disk Subsystem

GLM, Disconnected, Command, Timeout, tagged, Seagate, ST39103LC, ST318203LC
Previously Published As
76115

Change History
Date: 2006-09-05
User Name: 95826
Action: Add Comment
Comment: Hi Don,
this document has been requested to be deleted (see
http://kops.central/kgap/request.jsp?reqid=2508 for details) .
Are you ok that we delete it or do you want to modify it ?
Knowledge Operations
Version: 0
Date: 2006-08-17
User Name: 97961
Action: Approved
Comment: Publishing. No further edits required.
Version: 7
Date: 2006-08-17
User Name: 97961
Action: Accept
Comment:
Version: 0
Date: 2006-08-17
User Name: 86700
Action: Approved
Comment: Have made some changes and added a few more lines to add clearity. Also included the case no which suffered with this problem and resolution worked for tracking. Finally added some more keywords to make it clearer.

Ok for final review

-Sailesh
Version: 0
Date: 2006-08-15
User Name: 115361
Action: Approved
Comment: Hi Sailesh
As agreed in your email, I'am sending it to your queue.
Sacha
Version: 0
Date: 2006-08-07
User Name: 86700
Action: Rejected
Comment: Dear Updater,

I am afraid I will have to reject the document on the following grounds :-

1. First of all, what bug the patch 113669-01 fix? I couldnt find any bug listed mentioning the problem described here in this SRDB

2. Couldnt this problem be of glm driver itself?

3. What if we get this error message when NO Seagate drives is present in the system? A quick search in sunsolve could make us hit many cases with this symptom? What about such cases?

4. Can the Escalation which prompted to create this SRDB be listed in the internal section?

I am sorry I have to reject the document unless the above queries are clarified to make this a complete document.

rgds

-Sailesh
Version: 0
Date: 2006-08-03
User Name: 86700
Action: Accept
Comment:
Version: 0
Date: 2006-08-03
User Name: 115361
Action: Approved
Comment: Disk FW and drive type are mixed up:

* To fix the ST39103LC drive, upgrade to the 074A firmware revision.
* To fix the ST318203LC drive, upgrade to the 074B firmware revision.

Should be the other way round, like this:
ST39103L -> 074B
ST318203L -> 074A

(see also FW patch readme 113669-01)
Version: 0
Date: 2006-08-03
User Name: 115361
Action: Update Started
Comment: Disk FW are mixed up, should eb the other way round, like this:
ST318203L -> 074A
ST39103L -> 074B

(see also FW patch readme 113669-01)
Version: 0
Date: 2004-07-21
User Name: 13128
Action: Approved
Comment: Update is fine
Version: 3
Date: 2004-07-21
User Name: 13128
Action: Accept
Comment:
Version: 0
Date: 2004-07-21
User Name: 87848
Action: Approved
Comment: approved-only keywords corrected
Version: 0
Date: 2004-07-21
User Name: 87848
Action: Accept
Comment:
Version: 0
Date: 2004-07-21
User Name: 87848
Action: Approved
Comment: only keywords updated per KGAP request 405
Version: 0
Date: 2004-07-21
User Name: 87848
Action: Update Started
Comment: accepting per KGAP 405
Version: 0
Date: 2004-06-24
User Name: 13128
Action: Approved
Comment: Update is fine, looks like corrective action was taken.
Version: 0
Date: 2004-06-23
User Name: 13128
Action: Accepted
Comment:
Version: 0
Date: 2004-06-21
User Name: 70984
Action: Approved
Comment: Corrected drive type to match patch description as requested.
Version: 0
Date: 2004-06-15
User Name: 25440
Action: Reassigned
Comment: Putting copy in Don's draft queue for him to investigate
Version: 0
Date: 2004-06-15
User Name: 25440
Action: Updated
Comment: sunSolve feedback says there's an inconsistency:
Customer comment from [tse@asia] via the [Internal Customer Feedback Form]

----------------------------------------------------------------------

Email: tse@asia
Contact: Ian Tang
Comments: In SRDB 76115

One of the drive model number should be ST318203L instead of
ST18203L according to patch readme 113669-01

-Ian
Version: 0
Date: 2004-05-21
User Name: C125716
Action: Approved
Comment: I shortened the title, added a few sentences, checked for trademarks, and fixed the keywords.
Version: 0
Date: 2004-05-14
User Name: C125716
Action: Accepted
Comment:
Version: 0
Date: 2004-05-14
User Name: 38701
Action: Approved
Comment: Looks good.
Version: 0
Date: 2004-05-14
User Name: 38701
Action: Accepted
Comment:
Version: 0
Date: 2004-05-11
User Name: 70984
Action: Approved
Comment: Please review and approve or contact me for any changes.
Version: 0
Date: 2004-05-11
User Name: 70984
Action: Created
Comment:
Version: 0

Attachments

This solution has no attachment