Hello,

After writing out an email and checking that I hadn't overlooked anything I now have got this tape drive going, but I do have a question.

The initial problem was that the kernel was detecting the tape drive as device sg0 rather than st0 this occurred when the tape support was complied into the kernel as an experiment I changed it to a module and ran modprobe st and got a st device in dev and the drive works fine. no reboots even! :-)

So I guess my question is why would the st device not show up in dev when compiled into the kernel but works fine as a module? The drive is backing up data now and as I mention below there is still no entry in /proc/scsi the scsi directory does not exist. Interesting I have another gentoo machine with the same tape drive and it works fine with tape support compiled into the kernel and has a /proc/scsi entry and /dev/st0

Thanks
Simon.


nb kernel version 2.6.24-gentoo-r8

Original message..


I have setup a new linux machine running gentoo for use as a small network based server at home and its running very well.
I want to store backup data on a SCSI tape drive which I have installed.
I have everything installed and appears to detected o.k.
Termination and cabling has been checked and correct this is also the only device on the bus. The scsi card is a NCR810 PCI using the SYM53C8XX driver compiled into the kernel and detected on boot as sym0: <810> rev 0x2 at pci 0000:00:09.0 irq 19 The tape drive is Sony DDS3 SDT-9000 and detected as scsi 0:0:5:0: Sequential-Access SONY SDT-9000 0400 PQ: 0 ANSI: 2
SCSI tape support is also compiled into the kernel.

The problem is that the device is being detected as sg0 rather than normal st0 I have tried running a backup using tar with the sg0 device but it fails with this message tar: /dev/sg0: Cannot write: Numerical argument out of domain

The device in dev is listed as crw-rw---- 1 root tape 21, 0 Jun 23 18:27 /dev/sg0
There is no st0 device link or other wise.
I have attempted to create the device with mknod -m 666 /dev/st0 c 9 0 and then using tar get the error tar: /dev/st0: Cannot open: No such device or address

One odd thing I have noticed is that there is no /proc/scsi directory, I found a kernel option [*] legacy /proc/scsi/ support which I have added and recompiled but does not make any difference and does not create the /proc/scsi entry.

I suspect this is related to udev is my best guess but thats where I get stuck.

Reply via email to