On Fri, 12 Feb 2010 16:59:46 +0100 Daniel Kamm <y...@ylz.ch> wrote: > Dear all, > > I need some hints, ideas whatever. I have a Quantum Scalar i40 with two > separate LTO-4 SAS drives. I've conneced the drives with two SAS cables > to two separate SAS controller within the backup server. > > # cat /proc/scsi/scsi > Attached devices: > Host: scsi4 Channel: 00 Id: 00 Lun: 00 > Vendor: HP Model: Ultrium 4-SCSI Rev: U51Z > Type: Sequential-Access ANSI SCSI revision: 05 > Host: scsi4 Channel: 00 Id: 00 Lun: 01 > Vendor: QUANTUM Model: Scalar i40-i80 Rev: 100G > Type: Medium Changer ANSI SCSI revision: 03 > Host: scsi5 Channel: 00 Id: 00 Lun: 00 > Vendor: HP Model: Ultrium 4-SCSI Rev: U51Z > Type: Sequential-Access ANSI SCSI revision: 05 > > So far, so good, but mtx is not willing to see the second drive: > > # mtx -f /dev/sg1 status > Storage Changer /dev/sg1:1 Drives, 29 Slots ( 5 Import/Export ) > Data Transfer Element 0:Full (Storage Element 20 Loaded):VolumeTag = > MZ2019 > Storage Element 1:Empty:VolumeTag= > Storage Element 2:Empty:VolumeTag= > [..] >
Yes, there should be a "Data Transfer Element 1" there. > And mtx is not willing to load a tape into the second drive: > > # mtx -f /dev/sg1 load 22 1 > illegal <drive-number> argument '1' to 'load' command > > Any ideas what I did wrong? Any hints where I can start debugging? > Because since Baculas mtx-changer is using mtx, I think I am not able to > use the second drive. > Check dmesg for relevant messages and do something like ls -lah /dev/*st* to see if they're there? Regards, -- Alex Chekholko ch...@pcbi.upenn.edu ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users