Hello,
On Fri, 27 Apr 2007 15:42:38 -0700, "Petcher, Daniel" <[EMAIL PROTECTED]> wrote:
> That sounds reasonable. Let me probe around to find which device number the
> This error message takes about a minute to appear (/dev/nst0 behaves the
> same way):
> [EMAIL PROTECTED]:~# mtx -f /dev/st0 inquiry
> cannot open SCSI device '/dev/st0' - Input/output error
As already mentioned, mtx is only for changers, not tape drives. As you mention
in another mail you successfully found the drive under /dev/st0. Still I
recommend NOT to use /dev/st0 and instead use /dev/nst0. The reason for this is
that tape drives are usually represented through two device nodes, one
/dev/st<x> and a corresponding /dev/nst<x> with the n standing for
non-rewinding. What this means is that when you access the device through
/dev/st<x>, it will auto-rewind when it gets closed by the software (and if the
software doesn't expect that it may get very confused). The /dev/nst<x> devices
will only rewind when told so by the software or manually.
> This comes back immediately, but it's not the format you recommend:
> [EMAIL PROTECTED]:/dev# mtx -f /dev/sg2 inquiry
> Product Type: Tape Drive
> Vendor ID: 'IBM '
> Product ID: 'ULTRIUM-TD3 '
> Revision: '5BG2'
> Attached Changer API: No
Yep, that's your tape drive (it is also accessible as a generic device, in
addition to the two aforementioned 'tape' device nodes). As for your changer it
is likely to come after sg2 (try sg3 or sg4) as it is 'behind' the tape drive
in your /proc/scsi/scsi output:
> I don't know if this helps:
> [EMAIL PROTECTED]:/dev# cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: 3ware Model: Logical Disk 0 Rev: 1.2
> Type: Direct-Access ANSI SCSI revision: ffffffff
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
> Vendor: 3ware Model: Logical Disk 5 Rev: 1.2
> Type: Direct-Access ANSI SCSI revision: ffffffff
> Host: scsi2 Channel: 00 Id: 03 Lun: 00
> Vendor: IBM Model: ULTRIUM-TD3 Rev: 5BG2
> Type: Sequential-Access ANSI SCSI revision: 03
> Host: scsi2 Channel: 00 Id: 03 Lun: 01
> Vendor: DELL Model: PV-124T Rev: 0031
> Type: Medium Changer ANSI SCSI revision: 02
Medium Changer = changer device, coming 'after' the tape drive (ULTRIUM-TD3)
Hope that helps.
By the way, if you're having trouble with the devices changing around (sg2
becoming sg1 if your external drive is missing, ...) you should investigate
'scsidev' (On Debian this is part of the 'scsitools' packages). When run, it
will create aliases to your device that are based on the SCSI channel,
ID/target and LUN numbers. That way you could run scsidev at boot time, and
then refer to the 'hardcoded' links.
As an example here's my setup:
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: CERTANCE Model: ULTRIUM 2 Rev: 1914
Type: Sequential-Access ANSI SCSI revision: 03
Host: scsi0 Channel: 00 Id: 05 Lun: 01
Vendor: QUANTUM Model: UHDL Rev: 0043
Type: Medium Changer ANSI SCSI revision: 02
The ULTRIUM 2 is my drive, on host 0, channel 0, ID/target 5 and LUN 0
UHDL is my changer device (as seen in the 'Type) on host 0, channel 0,
ID/target 5 and LUN1
The resulting scsidev device nodes are:
Tape drive: /dev/scsi/nsth0-0c0i5l0
Changer: /dev/scsi/sgh0-0c0i5l1
(Note the beginning of the name that represents 'nst', 'sg', ...)
Greetings,
Michel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
