> Here's the output:
> [EMAIL PROTECTED] ~]# lsscsi
> [20:0:0:0]   tape    SEAGATE  ULTRIUM06242-XXX 1613  /dev/st0
> [21:0:0:0]   mediumx STK      L20              0215  /dev/sch0
> [22:0:0:0]   tape    SEAGATE  ULTRIUM06242-XXX 1613  /dev/st1
> 
> As you can see, it does not maintain devids but each one becomes id
> 0.  As a result, I get the following message when the changer loads:

Yeah, this is the fault of your storage. It converst the SCSI Ids
in each seperate target.

> ch0: type #1 (mt): 0x0+1 [medium transport]
> ch0: type #2 (st): 0x3e8+20 [storage]
> ch0: type #3 (ie): 0xa+0 [import/export]
> ch0: type #4 (dt): 0x1f4+2 [data transfer]
> ch0: dt 0x1f4: ID 9, LUN 0, Huh? device not found!
> ch0: dt 0x1f5: ID 10, LUN 0, Huh? device not found!
> ch0: INITIALIZE ELEMENT STATUS, may take some time ...
> ch0: ... finished
> ch 21:0:0:0: Attached scsi changer ch0
> ch 21:0:0:0: Attached scsi generic sg2 type 8
> 
> Seems like it's pretty picky about having the right IDs.  Maybe there
> are some module parameters for the ch module that would let me tell it
> where to try to find the drives?

Try 'modinfo ch'. The 'dt_id' and 'dt_lun' looks promising.

> 
> -Nick
> 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to