juke box problem - "chio: /dev/ch0: CHIOMOVE: Device not configured"

[Kenneth D. Merry]

On Wed, Oct 14, 2009 at 02:53:09 -0400, Paul Chvostek wrote:
> Hi Sean,
> 
> On Sat, Oct 10, 2009 at 02:49:19PM -0700, Sean Bruno wrote:
> > 
> > On Sat, 2009-10-10 at 17:14 -0400, Paul Chvostek wrote:
> > > 000031L4
> > 
> > Huh ... have you tried moving the tape by "voltag" ??
> > 
> > e.g.
> > 
> > move voltag 000020L4 drive 0
> 
> I have now, but with the same result:
> 
>   # chio status -v | grep drive
>   drive 0: <ACCESS,FULL> voltag: <000039L4:0>
>   drive 1: <ACCESS,FULL> voltag: <000030L4:0>
>   #
>   # chio move voltag 000030L4 slot 44
>   chio: /dev/ch0: CHIOMOVE: Device not configured
>   #
>   # tail -6 /var/log/messages
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): MOVE MEDIUM. CDB: a5 0 0 0 0 2 4 15 0 0 0 0 
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): CAM Status: SCSI Status Error
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): SCSI Status: Check Condition
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): ILLEGAL REQUEST asc:25,0
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Logical unit not supported
>   Oct 14 02:48:16 nas kernel: (ch0:isp0:0:0:1): Unretryable error

Typically a "Logical unit not supported" error means that that particular
LUN (in this case LUN 1) isn't supported/doesn't exist.  (Which would be
strange, given that it does probe.)

Could the changer be in autoloader mode?  That's the only thing I can think
of that would cause an error like that.  The only other explanation is that
they're misusing that error to say that it doesn't like the particular move
you're trying to do.

> Is there a way to determine whether this problem is with the device or
> with FreeBSD?  Note that I *can* move the tapes around using the juke
> box's web gui, so it's not a physical problem.
> 
> For reference:
> 
>   # grep 'at isp0' /var/run/dmesg.boot 
>   sa0 at isp0 bus 0 target 0 lun 0
>   ch0 at isp0 bus 0 target 0 lun 1

Ken
-- 
Kenneth Merry
ken at kdm.org