Problem attaching tape drive via fibre

[psych-major]

This is at work and the boss is yelling, so I'm unable to search extensively, and am hoping for a quick answer from someone who has actually done this before! That being said...

I am attaching a tape library via fibre on a SuSE 10.0 server. This worked fine on a test workstation with an IDE drive, and the robot came up at sg0, and the drives at st0 thru stN. But when I try it on the server, which has a SATA drive on scsi0 as sda on 0, 0, 0, it also tries to attach the library as sg0 at scsi0 0,0,0. The drives don't show up at all. I assume this is a udev issue, so below is a snippet from my udev rules file. If anyone has seen this type of behavior and can suggest a simple change, it would be much appreciated, otherwise it's back to the workstation until I can research it further.

# misc storage devices (non-block)
KERNEL=="sg*", NAME="%k", GROUP="disk", MODE="640"
KERNEL=="st*", NAME="%k", GROUP="disk"
KERNEL=="nst*", NAME="%k", GROUP="disk"
KERNEL=="initrd", NAME="%k", GROUP="disk"
KERNEL=="qft*", NAME="%k", GROUP="disk"
KERNEL=="nqft*", NAME="%k", GROUP="disk"
KERNEL=="zqft*", NAME="%k", GROUP="disk"
KERNEL=="nzqft*", NAME="%k", GROUP="disk"
KERNEL=="rawqft*", NAME="%k", GROUP="disk"
KERNEL=="nrawqft*", NAME="%k", GROUP="disk"
KERNEL=="pf*", NAME="%k", GROUP="disk"
KERNEL=="sch*", NAME="%k", GROUP="disk"
KERNEL=="pt*", NAME="%k", GROUP="disk"
KERNEL=="npt*", NAME="%k", GROUP="disk"
KERNEL=="pg*", NAME="%k", GROUP="disk"
KERNEL=="evms/block_device*", NAME="%k", GROUP="disk"
KERNEL=="rawctl*", NAME="%k", GROUP="disk"
KERNEL=="osst*", NAME="%k", GROUP="disk"
KERNEL=="nosst*", NAME="%k", GROUP="disk"
KERNEL=="iseries/vt*", NAME="%k", GROUP="disk"
KERNEL=="iseries/nvt*", NAME="%k", GROUP="disk"
KERNEL=="iseries/ibmsis*", NAME="%k", GROUP="disk"

[bwkaz]

If the kernel's SCSI driver is assigning it SCSI "address" 0,0,0, then no, that's not a udev issue, that's a kernel-SCSI-driver issue.

;)

(Unfortunately, I'm not at all sure how to start troubleshooting stuff like this. Are you using the same kernel on both boxes? Might it be possible to copy the desktop box's kernel over to the server?)

[psych-major]

I didn't check the kernel, but I don't think it's the same, but it's a non-issue on the desktop because the boot drive is ide, so therefore /dev/hda.

The good news is that I got the library up and running on the desktop, via fibre and I have full robotics control with the mtx command!

[The Linux Kid]

Does your mobo support fooling the system into saying that the SATA drive is IDE? For example my mobo lets me say that my SATA drive is /dev/hda - then you can have no more issues with the the hdd and tape drive fighting it out over 0,0,0

[psych-major]

That's a good call, I hadn't thought of that. I'll check it out tomorrow when I get to the office.