[wplug] SDT-9000 Sony Tape drive and Adaptec 2930U
Vanco, Donald
VANCOD at PIOS.com
Fri Feb 7 12:31:07 EST 2003
Wulf Consulting Linux wrote:
> Because of this:
>
>>>> blk: queue f794b414, I/O limit 4095Mb (mask 0xffffffff)
>>>> Vendor: SONY Model: SDT-9000 Rev: 0400
>>>> Type: Sequential-Access ANSI SCSI revision: 02
>>>> blk: queue f7863214, I/O limit 4095Mb (mask 0xffffffff) scsi : 1
>>>> host left.
I'm really confused - you said that the info in /proc/scsi did not show the
device. Yet it's in the text above (the output of dmesg)?
Are you certain of what is in /proc/scsi?
> That means that the OS sees the drive doesn't it?
At first glance I'd say yes - but if it's not in /proc then the
running kernel is not aware of it's presence.
> During boot the Card sees the drive on ID 6.
Standard fare for tapes / optical
> insmod says that the module is already loaded...
Can you send the output of lsmod and the contents of
/etc/modules.conf?
Then it's all a matter of the device node. Look at you old system
and see what the device name & major / minor numbers were:
(on my box)
[root at cdburner dev]# ls -la /dev/st0
crw-rw---- 1 root disk 9, 0 Apr 11 2002 /dev/st0
Major------------------------------------^ ^
Minor-----------------------------------------|
...look at the new system to insure those major / minor numbers are not
taken. If there is a device there, remove it and re-create it with mknod as
instructed in the prior email.
in /dev:
mknod st0 c 9 0
You said you were trying to use mt - what happens if you try
tar/cpio? I'm not familiar with mt - but don't you need to supply an
additional command in your example below??? (like mt -f /dev/st0 eject)
Simply telling it "mt -f /dev/st0" should get you a syntax error - not a
device error.
[root at cdburner root]# mt -f /dev/st0
usage: mt [-v] [--version] [-h] [ -f device ] command [ count ]
Don
>> Lorentz W. Hinrichsen wrote:
>>> no - I only see the IDE CDRW
>>
>> Well, then you've got bigger issues as it's not even being seen by
>> the bus. Here's what I might try:
>>
>> Verify switch settings per my last email. I know it worked in the
>> other box, but it's worth looking at.
>>
>> At boot, go into the controller BIOS set up and use the bus scan
>> utility to insure that the controller is seeing the device.
> If it's not -
>> you've got a dead drive or have not connected system power to it or
>> it's ID'd wrong - but I'm assuming the controller is intelligent
>> enough to warn (or at least hang ;) ) on duplicate SCSI ID's.
>>
>> If you can't get the controller to see the device then there's not
>> much point diddling in Linux as the OS is not at fault.
>>
>> But - If that's all well then it is certainly an OS issue -
>> - try running "insmod st"
>> [root at cdburner root]# insmod st
>> Using /lib/modules/2.4.18-19.7.x/kernel/drivers/scsi/st.o
>> - as suggested, try using mknode to generate the node (/dev/st0)
>> - try using all "known" tape devices (/dev/nst0, /dev/rmt0, etc)
>> .....that being said, the fact that the OS does not see it on the
>> bus is not a good thing - making nodes and loading modules will not
>> make it appear on the bus.
>>
>> At that point I don't even know that re-installing is going to gain
>> you anything. However - even before a re-install I'd run an upgrade
>> - yes, it takes longer than a fresh install (due to it making sweet,
>> sweet love to the RPM database) but it requires less intervention
>> and will not nuke any config work you may have done to this point.
>> An NFS or FTP upgrade would be even easier as there's no disk
>> swapping.
>>
>> As an aside FYI - RH8.0 can be installed via ISO images on FTP, NFS,
>> HTTP shares. Also - if installing on a system with multiple CD
>> drives you can put two disks in and the install will find them in
>> turn, allowing you to replace the first disk with the third disk at
>> your leisure as the install progresses. If you have 3 CDs in one
>> box... you need to hit eBay.
>>
>> YMMV
>> Don
>>
>>
>>>
>>> On Thu, 2003-02-06 at 14:57, Vanco, Donald wrote:
>>>> When you do a less on /proc/scsi/scsi do you at least see the
>>>> device??
>>>>
>>>> EG:
>>>> [root at cdburner scsi]# less scsi
>>>> Attached devices:
>>>> Host: scsi0 Channel: 00 Id: 00 Lun: 00
>>>> Vendor: IBM Model: DCAS-34330 !# Rev: S69D
>>>> Type: Direct-Access ANSI SCSI revision: 02
>>>> Host: scsi0 Channel: 00 Id: 01 Lun: 00
>>>> Vendor: YAMAHA Model: CRW2100S Rev: 1.0N
>>>> Type: CD-ROM ANSI SCSI revision: 02
>>>> Host: scsi0 Channel: 00 Id: 06 Lun: 00
>>>> Vendor: IBM Model: CDRM00203 !K Rev: 8B08 Type: CD-ROM
>>>>
>>>>
>>>> Don
>>>>
>>>> Lorentz W. Hinrichsen wrote:
>>>>> Hello all,
>>>>>
>>>>> We brought up a Red Hat 8.0 box as a Samba server.. we've been
>>>>> very successful so far. We didn't have the Adaptec 2930U when we
>>>>> installed so we added it after and it seemed to go ok if I do a
>>>>> "dmesg | less" I can find this reference to the card and drive:
>>>>>
>>>>> ahc_pci:1:10:0: Someone reset channel A
>>>>> scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8
>>>>> <Adaptec 2930CU SCSI adapter>
>>>>> aic7860: Ultra Single Channel A, SCSI Id=7, 3/253 SCBs
>>>>>
>>>>> blk: queue f794b414, I/O limit 4095Mb (mask 0xffffffff)
>>>>> Vendor: SONY Model: SDT-9000 Rev: 0400
>>>>> Type: Sequential-Access ANSI SCSI revision:
>>>>> 02 blk: queue f7863214, I/O limit 4095Mb (mask 0xffffffff) scsi :
>>>>> 1 host left.
>>>>>
>>>>> I was hoping that it would be like my test box at home which has a
>>>>> similar setup except - dds2 and 2940UW, I can get the status by
>>>>> doing "mt -f /dev/st0 status" and I can use TAR to backup and
>>>>> restore....
>>>>>
>>>>> When I do a "mt -f /dev/st0" I just get a "no such device" in the
>>>>> dmesg on my test box it does list the drive as st0.
>>>>>
>>>>> Another friend recommended I reinstall Red Hat with the controller
>>>>> and drive in the system as opposed to trying to add it after the
>>>>> fact.
>>>>>
>>>>> Any help is appreciated...
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --wulf
More information about the wplug
mailing list