It is currently Sat, 20 Dec 2014 20:42:16 GMT



 
Author Message
 Disconnected command timeout for Target

Hello,

  I have an Ultra Sparc 2 with a Sun DLT-4700 Jukebox attached, running
Solaris 2.5.1 and Solstice Backup (Legato Networker).  When doing backups,
I get the following error message

Apr  8 07:45:23 unix: fas: 4.0: cdb=[ 0x1 0x0 0x0 0x0 0x0 0x0 ]
Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
Apr  8 07:45:23 unix:      Disconnected command timeout for Target 4.0
Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000/st@4,0 (st4):
Apr  8 07:45:23 unix:      SCSI transport failed: reason 'timeout': retryi

This results in the tape being ejected before it is full, or results in
the Jukebox locking up.  The backups never complete.

I have contacted Sun Support and they sent out a replacement mother board,
replacement SCSI cable and also a replacement DLT-4700 tape drive.  I've
patched the machine with the latest jumbo kernel patches, replaced the
SCSI cable and the DLT-4700.  I have yet to replace the motherboard, since
we are still working on getting Sun maintenance for the machine and this
is being treated as a warranty issue, so I would actually have to replace
the motherboard myself.  Not something that I am eager to do.

This is what I have observed about the problem:

1.  The timeout error only happens on the external Jukebox.  I have not
seen or had any problems with the internal scsi drive which is on the
same scsi chain.  The machine is not loaded at all, there are no users
and the only thing that is running on it is Solstice Backup.

2.  A few minutes after the timeout error last night, the tape was
ejected.  But no other tape was loaded.  When I came in this morning, the
message on the Solstice Backup screen was
"Tue 09:08:44 media alert event: Jukebox `dlt-4700-0' failed Destination
component full".  The jukebox went through several slots, but Solstice
backup never mounted any other tape.  The tapes in the jukebox were all
labeled.  The jukebox or software, now seems to be confused.

I did a search at the sunsolve web site and also on dejanews.  On the
Sunsolve site, I found plenty of references to bugs, but no fixes.  There
was reference to increasing the timeout value for the st driver.

If anyone has suggestions on how to correct this problem, I would
appreciate hearing from them.

regards,

->Gerry Schenk
->gsch...@wimsey.com

-------------------==== Posted via Deja News ====-----------------------
      http://www.**-**.com/ ;   Search, Read, Post to Usenet



 Sat, 25 Sep 1999 03:00:00 GMT   
 Disconnected command timeout for Target

Hi,
  Sorry, no answer, if you get a answer, could you forward it to me?
I have a similiar problem.  I have a 2000 with a SA model 101 on
it.  It's root disk does the exact same thing at boot time.
I'm running 2.5 with all of the current patches (including the
SA's).  Sun came out and replaced the root disk 3 times and
all of the disk in the SA.  I swapped cables and controllers
for the root disk (it's a Fast/diff SCSI on a different controller
from the SA).  And still, the problem exist!  It only
happens once during boot, and then the machine runs fine....
  I suspect that these "weird" devices somehow take control
of the SCSI bus/buses and are slightly out of sync with the
regular disk.
                                                -Bob
                                                barn...@erols.com



 Sat, 25 Sep 1999 03:00:00 GMT   
 Disconnected command timeout for Target

: Apr  8 07:45:23 unix: fas: 4.0: cdb=[ 0x1 0x0 0x0 0x0 0x0 0x0 ]
: Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
: Apr  8 07:45:23 unix:      Disconnected command timeout for Target 4.0
: Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000/st@4,0 (st4):
: Apr  8 07:45:23 unix:      SCSI transport failed: reason 'timeout': retryi

Sorry, similar problem here.
Just with ufsdump and a HP DDS-2 DAT tape. After about 1GB data the
error appears, and the backup is never completed.

--

------------------------
ANDREAS KROMKE

.....................................................
Fragen Sie nicht, was Ihr Computer fuer Sie tun kann.
Fragen Sie, was Sie fuer Ihren Computer tun koennen.



 Sun, 26 Sep 1999 03:00:00 GMT   
 Disconnected command timeout for Target

: : Apr  8 07:45:23 unix: fas: 4.0: cdb=[ 0x1 0x0 0x0 0x0 0x0 0x0 ]
: : Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
: : Apr  8 07:45:23 unix:      Disconnected command timeout for Target 4.0
: : Apr  8 07:45:23 unix: WARNING: /sbus@1f,0/SUNW,fas@e,8800000/st@4,0 (st4):
: : Apr  8 07:45:23 unix:      SCSI transport failed: reason 'timeout': retryi
:
: Sorry, similar problem here.
: Just with ufsdump and a HP DDS-2 DAT tape. After about 1GB data the
: error appears, and the backup is never completed.

Just adding a "me too" with an EXB-8500 on an Ultra 1 and a 1533A on an SS20.
Again, both after about a gig.  The SS20 is running 2.4 and the Ultra 2.5.1,
all with latest patches.

--
        Harnad describes the status of Usenet aptly:
                a communication medium with revolutionary intellectual
                potential being used mostly as a global graffiti board.
                [Harnad 1991]



 Sun, 26 Sep 1999 03:00:00 GMT   
 
   [ 4 post ] 

Similar Threads

1. Help!!! Disconnected command timeout for Target <id>.<lun>

2. Disconnecting command timeouts

3. warning: timeout: reset target chno = 1 targ =2

4. MS mail client timeout/disconnect on large downloads

5. timeout eth0 on disconnected laptop fedora core2

6. adsl disconnects due to eth tx timeout

7. Linux won't let my ISDN modem disconnect on timeout

8. No-activity disconnect timeout for pppd...

9. pppd disconnect timeout problem

10. getting PPP to disconnect on LCP timeouts


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software