Usually, as long as the OS "sees" the tape drive, the st module will be loaded automatically. In your case, I don't think that the the OS is seeing the Tape drive. This is probably due to a problem with the SCSI card. You said that the BIOS is seeing the card, but from your proc/scsi we don't see the tape drive. This indicates that there is a driver problem or a configuration problem with the scsi card that the tape drive is attached to. Therefore it's not attached. I would say, that you should remove the HBA (if possible) and reboot the server. Use the cat /proc/scsi/scsi and the following commands to determine if the Tape Drive is active: cat /proc/scsi/scsi should show something like this: Host: scsi0 Channel: 00 Id: 06 Lun: 00 Vendor: DELL Model: SDLT-320 Rev: 37RH Type: Sequential-Access ANSI SCSI revision: 03 (Note: this is taken from an LTO drive, so it won't be exact) Next command: dmesg | grep Attached Attached scsi tape st0 at scsi0, channel 0, id 6, lun 0 (This would tell us that the st module is loaded) Next command: dmesg | grep Vendor Vendor: DELL Model: SDLT-320 Rev: 022B This would confirm that the tape drive is at least showing somewhere. Lastly, I would say that you should look through your dmesg after a clean reboot. dmesg will usually identify any problems it is having with the scsi bus. Any lines that contain scsi or SCSI will usually tell you what is going on if there is a problem. Regards, Jay Laprade --------------------------------- Yahoo! Mail Use Photomail to share photos without annoying attachments. -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
