After these errors, I placed a DLT drive on the end of the SCSI
cable and it worked fine on the Linux computer, then I took THIS
drive and cable to a computer running NT 4.0 SP5 (and using an
Adaptec 2930) and it worked. We backed up and restored data
just fine.
We used the same media in all cases.
Since you are the person that ported the driver to Linux, I'll assume
you are saying that there most likely is NOT a problem with the
driver. :)
Thanks for your help. Do you have any other suggestions?
Dennis
>
>
> On Wed, 7 Jun 2000, Dennis DeDonatis wrote:
>
> > If I:
> >
> > mt -f /dev/nst0 retension
> >
> > I get:
> >
> > sym53c876-1: unexpected disconnect
> > sym53c876-1-<2,0>: COMMAND FAILED (8a ff) @df689000.
> > sym53c876-1: unexpected disconnect
> > sym53c876-1-<2,0>: COMMAND FAILED (8a ff) @df689000.
> > scsi1 channel 0 : resetting for second half of retries.
> > SCSI bus is being reset for host 1 channel 0.
> > sym53c8xx_reset: pid=9956 reset_flags=1 serial_number=0 serial_number_at_timeout=0
> > scsi1: device driver called scsi_done() for a syncronous reset.
> > sym53c876-1: restart (scsi reset).
> > sym53c876-1: Downloading SCSI SCRIPTS.
> > sym53c876-1: unexpected disconnect
> > sym53c876-1-<2,0>: COMMAND FAILED (8a ff) @df689000.
> > sym53c876-1: unexpected disconnect
> > sym53c876-1-<2,0>: COMMAND FAILED (8a ff) @df689000.
> > sym53c876-1: unexpected disconnect
> > sym53c876-1-<2,0>: COMMAND FAILED (8a ff) @df689000.
> > st0: Error 2707007f (sugg. bt 0x20, driver bt 0x27, host bt 0x7).
>
> The device disconnected from the SCSI BUS when the host was not expecting
> it to do so (while a SCSI transaction was in progress). This is the usual
> and recommended way for a SCSI device to report severe errors that cannot,
> for some reason, be reported by the normal SCSI error reporting protocol
> (status CHECK CONDITION followed by a REQUEST SENSE command).
>
> As a result, there is no means to know about the reason of the problem,
> since no information about the error is transmitted to the host by the
> device. :(
>
> > Here are the startup messages:
> >
> > scsi : 0 hosts.
> > scsi : detected total.
> > md.c: sizeof(mdp_super_t) = 4096
> > Partition check:
> > RAMDISK: Compressed image found at block 0
> > autodetecting RAID arrays
> > autorun ...
> > .. autorun DONE.
> > VFS: Mounted root (ext2 filesystem).
> > sym53c8xx: at PCI bus 0, device 6, function 0
> > sym53c8xx: 53c876 detected
> > sym53c8xx: at PCI bus 0, device 6, function 1
> > sym53c8xx: 53c876 detected
> > sym53c876-0: rev=0x14, base=0xc6ffcf00, io_port=0x2000, irq=5
> > sym53c876-0: ID 7, Fast-20, Parity Checking
> > sym53c876-0: on-chip RAM at 0xc6fff000
> > sym53c876-0: restart (scsi reset).
> > sym53c876-0: Downloading SCSI SCRIPTS.
> > sym53c876-1: rev=0x14, base=0xc6ffce00, io_port=0x2400, irq=10
> > sym53c876-1: ID 7, Fast-20, Parity Checking
> > sym53c876-1: on-chip RAM at 0xc6ffe000
> > sym53c876-1: restart (scsi reset).
> > sym53c876-1: Downloading SCSI SCRIPTS.
> > scsi0 : sym53c8xx - version 1.3g
> > scsi1 : sym53c8xx - version 1.3g
> > scsi : 2 hosts.
> > Vendor: COMPAQ Model: BD009122C6 Rev: B016
> > Type: Direct-Access ANSI SCSI revision: 02
> > Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> > sym53c876-0-<0,0>: tagged command queue depth set to 8
> > Vendor: ARCHIVE Model: Python 28388-XXX Rev: 4.28
> > Type: Sequential-Access ANSI SCSI revision: 02
> > sym53c876-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
> > SCSI device sda: hdwr sector= 512 bytes. Sectors= 17773524 [8678 MB] [8.7 GB]
> > sda: sda1 < sda5 sda6 sda7 sda8 sda9 sda10 > sda3
> > autodetecting RAID arrays
> > autorun ...
> > .. autorun DONE.
> > VFS: Mounted root (ext2 filesystem) readonly.
> >
> > Can anyone help me figure out what is wrong? What other
> > information do you need? I am running RedHat v6.1 with kernel
> > 2.2.14-12.
>
> May-be the drive has mechanical problems or encountered a problem with the
> media.
>
> G�rard.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]