I'm trying to get a scsi tape device (Sony SDX-D500V) working on my dell 2450 running centos 4.2. I can see the device (ch1, id2) using the dell bois raid utility, but once booted into linux I can't see any mention of it in the logs or dmesg.
Do you know if the generic kernel (2.6.9-22.0.1.ELsmp) supports this tape device? Can anyone give me any pointers in getting this device working.
Regards, Marc
See a recent thread in the archives. You might have to modprobe for it.
2005/12/13, Marc Peiser marcpeiser@gmail.com:
I'm trying to get a scsi tape device (Sony SDX-D500V) working on my dell 2450 running centos 4.2. I can see the device (ch1, id2) using the dell bois raid utility, but once booted into linux I can't see any mention of it in the logs or dmesg.
Enrico, Texas A&M University
Marc Peiser marcpeiser@gmail.com wrote:
I'm trying to get a scsi tape device (Sony SDX-D500V) working on my dell 2450 running centos 4.2. I can see the device (ch1, id2) using the dell bois raid utility, but once booted into linux I can't see any mention of it in the logs or dmesg.
Is it the same SCSI controller as the SCSI disks? Are the SCSI disks in a hardware RAID configuration?
Just FYI, some Linux drivers for SCSI cards with RAID only have disk/block support, and not more advanced support for rich peripherals like optical/tape on the same controller.
[ I don't know if that is your case, I haven't researched your Dell model/configuration. ]
Do you know if the generic kernel (2.6.9-22.0.1.ELsmp) supports this tape device?
Yes. But I think you're issue is something else (as above).
Can anyone give me any pointers in getting this device working.
If you do an "lsmod", we can find out more about your SCSI controller.
Now if your tape is attached to a different controller (not just a different channel on the same controller) than your disks, then it's probably just the fact the SCSI driver isn't loaded.
In either case, I need to know what disk controller.
On 13/12/05, Bryan J. Smith thebs413@earthlink.net wrote:
Marc Peiser marcpeiser@gmail.com wrote:
I'm trying to get a scsi tape device (Sony SDX-D500V) working on my dell 2450 running centos 4.2. I can see the device (ch1, id2) using the dell bois raid utility, but once booted into linux I can't see any mention of it in the logs or dmesg.
Is it the same SCSI controller as the SCSI disks? Are the SCSI disks in a hardware RAID configuration?
Yes, you're right. I'm using the onboard scsi controller. Channel/scsi 0 has 5 disks (id 0-4) in RAID 5 configuration, the tape drive is connected to the channel 1, id 2.
Just FYI, some Linux drivers for SCSI cards with RAID only
have disk/block support, and not more advanced support for rich peripherals like optical/tape on the same controller.
[ I don't know if that is your case, I haven't researched your Dell model/configuration. ]
Just had another look at the output from dmesg and see the following:
SCSI subsystem initialized ACPI: PCI interrupt 0000:05:04.0[A] -> GSI 31 (level, low) -> IRQ 217 ACPI: PCI interrupt 0000:05:04.1[B] -> GSI 30 (level, low) -> IRQ 225 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec aic7899 Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 <Adaptec aic7899 Ultra160 SCSI adapter> aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005) megaraid: 2.20.4.6 (Release Date: Mon Mar 07 12:27:22 EST 2005) megaraid: probe new device 0x101e:0x1960:0x1028:0x0493: bus 2:slot 0:func 0 ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 193 megaraid: fw version:[1.57] bios version:[3.13] scsi2 : LSI Logic MegaRAID driver scsi[2]: scanning scsi channel 0 [Phy 0] for non-raid devices Vendor: DELL Model: 1x5 U2W SCSI BP Rev: 1.30 Type: Processor ANSI SCSI revision: 02 scsi[2]: scanning scsi channel 1 [Phy 1] for non-raid devices scsi[2]: scanning scsi channel 2 [virtual] for logical drives Vendor: MegaRAID Model: LD0 RAID5 38712R Rev: 1.57 Type: Direct-Access ANSI SCSI revision: 02 SCSI device sda: 284082176 512-byte hdwr sectors (145450 MB) sda: asking for cache data failed sda: assuming drive cache: write through sda: sda1 sda2 Attached scsi disk sda at scsi2, channel 2, id 0, lun 0 kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Attached scsi generic sg0 at scsi2, channel 0, id 6, lun 0, type 3 Attached scsi generic sg1 at scsi2, channel 2, id 0, lun 0, type 0
I'm not sure what this means, but looks to me like LSI Logic MegaRAID driver should find my tape device. Is that correct?
Do you know if the generic kernel (2.6.9-22.0.1.ELsmp)
supports this tape device?
Yes. But I think you're issue is something else (as above).
Can anyone give me any pointers in getting this device working.
If you do an "lsmod", we can find out more about your SCSI controller.
[root@vindaloo ~]# lsmod Module Size Used by md5 8001 1 ipv6 240097 28 autofs4 22085 0 i2c_dev 14273 0 i2c_core 25921 1 i2c_dev sunrpc 139173 1 microcode 11873 0 dm_mod 58949 0 button 10449 0 battery 12869 0 ac 8773 0 ohci_hcd 23889 0 tg3 85061 0 e100 38209 0 mii 8641 1 e100 floppy 58065 0 sg 38113 0 ext3 118729 1 jbd 59481 1 ext3 megaraid_mbox 37073 2 megaraid_mm 17905 1 megaraid_mbox aic7xxx 146425 0 sd_mod 20545 3 scsi_mod 116429 4 sg,megaraid_mbox,aic7xxx,sd_mod [root@vindaloo ~]#
Now if your tape is attached to a different controller (not
just a different channel on the same controller) than your disks, then it's probably just the fact the SCSI driver isn't loaded.
In either case, I need to know what disk controller.
Yes, same controller, different channel. I've included the output of dmesg for you to look at.
Thanks for your help.
--
Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, 14 Dec 2005 09:03:38 +0000 Marc Peiser marcpeiser@gmail.com wrote:
Just had another look at the output from dmesg and see the following:
<snip>
Try:
# modprobe st
or
# modprobe sg
See if anything new shows up in dmesg (or /var/log/messages) output.
Vanja
-
Bryan J. Smith -
Marc Peiser -
Salvatore Enrico Indiogine -
Vanja Hrustic