Disconnected command timeout for Target
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.
-------------------==== Posted via Deja News ====-----------------------
http://www.**-**.com/ ; Search, Read, Post to Usenet