* [EMAIL PROTECTED] <[EMAIL PROTECTED]> (Tue, Feb 20, 2001 at
09:28:20AM +0100)
> I'm using Amanda-2.4.1p1 with SuSE Linux 7.0 (Kernel 2.2.16) and a Onstream
> ADR50i SCSI Device (latest Firmware 2.33).
> Following error occured while amdump, showing by amcheck Daily:
>
> /var/log/messages says:
> ---/var/log/messages---
> Feb 20 04:19:39 fordprefect kernel: scsi : aborting command due to timeout :
> pid 1653712, scsi0, channel 0, id 2, lun 0 Write (6) 01 00 00 40 00
> Feb 20 04:19:41 fordprefect kernel: SCSI host 0 abort (pid 1653712) timed
> out - resetting
> Feb 20 04:19:41 fordprefect kernel: SCSI bus is being reset for host 0
> channel 0.
> Feb 20 04:19:44 fordprefect kernel: (scsi0:0:2:0) Synchronous at 40.0
> Mbyte/sec, offset 8.
> Feb 20 04:19:44 fordprefect kernel: st0: Error with sense data: [valid=0]
> Info fld=0x0, Current st09:00: sense key Unit Attention
> Feb 20 04:19:44 fordprefect kernel: Additional sense indicates Power on,
> reset, or bus device reset occurred
> ---/var/log/messages---
> Does someone know, how to fix?
SCSI - errors:
1) check termination.
2) check cables.
3) recheck termination.
4) check cable length.
5) check drivers.
6) check termination.
7) check hardware (disk/tape)
8) check if all hardware on the chain is indeed reporting correct Xfer
speeds. [1]
[1] If you have a chain where a wide scsi device is connected to a wide
scsi capable PC card, through a narrow scsi cable make sure it expects
narrow scsi Xfer rates (some devices negotiate wide scsi in this situation,
because they don;t see there's only a narrow cable in between.
Gerhard, <@jasongeo.com> == The Acoustic Motorbiker ==
--
__O If your watch is wound, wound to run, it will
=`\<, If your time is due, due to come, it will
(=)/(=) Living this life, is like trying to learn latin
in a chines firedrill
