Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Oct 1997 20:29:19 -0700 (PDT)
From:      Stephen Rose <rose@dml.com>
To:        Chris Shenton <chris@absinthe.i3inc.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: Broken Amanda/Archive DAT chio/seagate-changer
Message-ID:  <199710170329.UAA00371@locus.dml.com>

next in thread | raw e-mail | index | archive | help
> Problem is I can't get the changer part to work. I'm running
> FreeBSD-2.2-Stable, cvsupped a week about a week ago.  I compiled in
> support for ch0 in the kernel and it's recognized at boot:

>     (ncr0:6:0): "ARCHIVE Python 28849-XXX 4.CM" type 1 removable SCSI 2
>     st0(ncr0:6:0): Sequential-Access
>     st0(ncr0:6:0): 5.0 MB/s (200 ns, offset 8)
>     density code 0x13, 512-byte blocks, write-enabled

>     (ncr0:6:1): "ARCHIVE Python 28849-XXX 4.CM" type 8 removable SCSI 2
>     ch0(ncr0:6:1): Medium-Changer 4 slots, 1 drive, 1 picker

> Some of the chio commands don't work, most notably "status":

>     operator@thanatos<17> chio status
>     chio: /dev/ch0: CHIOGSTATUS: Input/output error

There is a problem with the ncr driver and the chio status command.  I 
discovered this months ago from a search in the archives.  I've been 
meaning to get some debug data for Stefan, but just haven't gotten around
to it.  I believe the chio driver has always worked well with the Adaptec
driver, although I don't know that from experience.

Steve Rose



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710170329.UAA00371>