[5471] in linux-scsi channel archive
Re: Exabyte 8[25]00 8mm Tape drives & 53c810a , Troubles ?
daemon@ATHENA.MIT.EDU (Richard Waltham)
Tue Dec 22 23:03:47 1998
From: Richard Waltham <dormouse@farsrobt.demon.co.uk>
To: babydr@nwrain.net (Mr. James W. Laferriere)
Date: Wed, 23 Dec 1998 00:39:19 +0000 (GMT)
Cc: groudier@club-internet.fr, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.96.981221213231.110A-100000@filesrv1.baby-dragons.com> from "Mr. James W. Laferriere" at Dec 21, 98 09:38:57 pm
Mr. James W. Laferriere wrote:
>
>
> Hello Gerard , Please find below a dmesg from a very bad tar
> attempt to the tape drive mentioned . Also I tried the 8500
> everything else same except used 8500 instead . IE:
>
> Vendor: EXABYTE Model: EXB-850085QANXRC Rev: 06X0
> Type: Sequential-Access ANSI SCSI revision: 02
>
> Command used :
>
> tar --same-owner -cpf /dev/st0 /etc/passwd /[0-9A-Za-oq-z]*
>
> a few minutes after the 'command processing resumed'
> the timeouts resumed & didn't stop , truth be told couldn't
> be stopped with out 'reset switch' . :-{
As the tape drive is on a different controller to the disks and it is the
disks timing out I would suspect a problem with the controller/scsi bus the
disks are on, not the tape unit.
I use an almost identical exb-8500, slightly different firmware level, with
no problems. My disk is on its own controller SYM8951U and tape and CD on a
second controller SYM8751SP - similar, but not identical, set up to yours.
A typical set up that is almost certain to generate timeouts is to have disk
and tape on the same bus with the tape set up to _not_ disconnect. However
with the tape on a different controller to the disks it is possible to set
the tape to disconnect or not disconnect and there should be no timeouts.
I would check out the disk scsi bus just in case you disturbed something
when adding the tape unit.
Bye for now
Richard
>
> Tia, JimL
> +-----------------------------------------------------------------------+
> | James W. Laferriere - Network Engineer - babydr@baby-dragons.com |
> | System Techniques - 25416 - 22nd S. - Des-Moines, WA 98198 |
> | Give me VMS -or- Give me Linux -but- only on AXP |
> +-----------------------------------------------------------------------+
>
> scsi0 : sym53c8xx/version 1.0
> scsi1 : sym53c8xx/version 1.0
> scsi : 2 hosts.
> ncr53c875J-0: command processing resumed
> Vendor: Quantum Model: XP31070W Rev: L912
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
> ncr53c875J-0-<0,0>: tagged command queue depth set to 8
> ncr53c875J-0-<1,0>: tagged command queue depth set to 8
> Vendor: EXABYTE Model: EXB-8200 Rev: 262Z
> Type: Sequential-Access ANSI SCSI revision: 01
> Detected scsi tape st0 at scsi1, channel 0, id 4, lun 0
> Vendor: PIONEER Model: CD-ROM DR-124X Rev: 1.06
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi1, channel 0, id 6, lun 0
> scsi : detected 1 SCSI tape 1 SCSI cdrom 2 SCSI disks total.
> ncr53c875J-0-<0,*>: WIDE SCSI (16 bit) enabled.
> ncr53c875J-0-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 2203480 [1075 MB] [1.1 GB]
> ncr53c875J-0-<1,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 4124736 [2014 MB] [2.0 GB]
> ncr53c810a-1-<4,*>: SYNC transfers not supported.
> scsi : aborting command due to timeout : pid 9454, scsi0, channel 0, id 1, lun 0 Read (6) 14 f2 2e 02 00
> ncr53c8xx_abort: pid=9454 serial_number=9473 serial_number_at_timeout=9473
> scsi : aborting command due to timeout : pid 9456, scsi0, channel 0, id 1, lun 0 Read (6) 14 f2 44 18 00
> ncr53c8xx_abort: pid=9456 serial_number=9475 serial_number_at_timeout=9475
> scsi : aborting command due to timeout : pid 9457, scsi0, channel 0, id 1, lun 0 Read (6) 14 f4 e4 2c 00
> ncr53c8xx_abort: pid=9457 serial_number=9476 serial_number_at_timeout=9476
> scsi : aborting command due to timeout : pid 9460, scsi0, channel 0, id 1, lun 0 Read (6) 14 f5 10 0a 00
> ncr53c8xx_abort: pid=9460 serial_number=9479 serial_number_at_timeout=9479
> scsi : aborting command due to timeout : pid 9461, scsi0, channel 0, id 0, lun 0 Write (6) 04 eb 98 06 00
> ncr53c8xx_abort: pid=9461 serial_number=9480 serial_number_at_timeout=9480
> SCSI host 0 abort (pid 9456) timed out - resetting
> SCSI bus is being reset for host 0 channel 0.
> ncr53c8xx_reset: pid=9456 reset_flags=2 serial_number=9475 serial_number_at_timeout=9475
> ncr53c875J-0: resetting, command processing suspended for 2 seconds
> ncr53c875J-0: restart (scsi reset).
> ncr53c875J-0: enabling clock multiplier
> ncr53c875J-0: Downloading SCSI SCRIPTS.
> ncr53c875J-0: command processing resumed
> ncr53c875J-0-<1,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
> ncr53c875J-0-<0,*>: WIDE SCSI (16 bit) enabled.
> ncr53c875J-0-<0,*>: FAST-10 WIDE SCSI 20.0 MB/s (100 ns, offset 15)
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
>
--
Richard Waltham | Work: richard@digitalinterface.demon.co.uk
At home in | Home: dormouse@farsrobt.demon.co.uk
Southampton UK | 100421.1276@compuserve.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
