Trying to setup a tape drive (Dell Powervault in Dell 2550 Poweredge server with ad160 controller). I know the tape is on the second embedded controller as ID 6....1,6,0,0. SCO still however will not recognize the device /dev/rct0 or any other rStp0 xct0 or xStp0. Everything seems to go smoothly with mkdev tape and the kernel relink. Ive followed SCO's instruction, called Dell tech support to verify that I should be calling this adapter 1 (Ive tried about every combo though), Dells tech support instructions were the same as SCO's. An l /dev/rct0 gives the correct response, a view of all related files look correct (mscsi, ../default/tape, etc). I cant cat the device, SCO backup doesnt see a tape device and lonetar cant open tape device.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Tape Drive Nightmare
- Thread starter chikn
- Start date
See if "sconf -v" agrees with the Stp line in /etc/conf/cf.d/mscsi. If it doesn't, edit mscsi, relink, reboot. Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
SCO Unix/Linux Resources tony@pcunix.com
- Thread starter
- #3
sconf -v gives this
Srom wd 0 0 0 0
Sdsk ad160 0 0 0 0
Sdsk ad160 0 0 1 0
unknown ad160 0 0 6 0
0,0,6,0 is the Adapter itself I believe.
mscsi
wd Srom 0 0 0 0
ad160 Sdsk 0 0 0 0
ad160 Sdsk 0 1 0 0
ad160 Stp 1 6 0 0
This is all Channel A, nothing on Channel B is listed using sconf -v. Tape drive only thing on channel B and it is recognized by the controller during boot up Channel B ID 6.
When I specified adapter 1 during mkdev tape it asked me if I wanted to install link-kit, which I did. Does this mean Channel B isnt being recognized for some reason.
Srom wd 0 0 0 0
Sdsk ad160 0 0 0 0
Sdsk ad160 0 0 1 0
unknown ad160 0 0 6 0
0,0,6,0 is the Adapter itself I believe.
mscsi
wd Srom 0 0 0 0
ad160 Sdsk 0 0 0 0
ad160 Sdsk 0 1 0 0
ad160 Stp 1 6 0 0
This is all Channel A, nothing on Channel B is listed using sconf -v. Tape drive only thing on channel B and it is recognized by the controller during boot up Channel B ID 6.
When I specified adapter 1 during mkdev tape it asked me if I wanted to install link-kit, which I did. Does this mean Channel B isnt being recognized for some reason.
The adaptor should be at 7 normally.
sconf shows:
Adaptor bus id lun
and msci is
Adaptor id lun bus
so your device at id 6 is not on adaptor 1 according to sconf.
Modify mscsi to be
ad160 Stp 0 6 0 0
relink, reboot. Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
sconf shows:
Adaptor bus id lun
and msci is
Adaptor id lun bus
so your device at id 6 is not on adaptor 1 according to sconf.
Modify mscsi to be
ad160 Stp 0 6 0 0
relink, reboot. Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
- Thread starter
- #5
This is what happens when I use
Stp 0 6 0 0
cat /dev/rct0
Vender=DELL Product 1x4 U2W SCSI BP
cat: cannot open /dev/rct0: No such device or address (error 6)
Looks to me like its trying to cat the adapter using 0600
This is what SCSI bios says during boot
ChA 0 Fujutsu 160
1 Fujitsu 160
6 1x4 U2W SCSI Async
ChB 6 Python (#'s here) 80
So Im pretty sure that its adapter 1 and not adapter 0.
Thanks for your time.
Stp 0 6 0 0
cat /dev/rct0
Vender=DELL Product 1x4 U2W SCSI BP
cat: cannot open /dev/rct0: No such device or address (error 6)
Looks to me like its trying to cat the adapter using 0600
This is what SCSI bios says during boot
ChA 0 Fujutsu 160
1 Fujitsu 160
6 1x4 U2W SCSI Async
ChB 6 Python (#'s here) 80
So Im pretty sure that its adapter 1 and not adapter 0.
Thanks for your time.
The fact that it returned the vendor string says the driver saw it at the configured address. The "sconf -v" doesn't lie afaik.
Do you have a tape in it ??? Is the cable secure? Properly terminated?
Try "tape status" instead. Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
Do you have a tape in it ??? Is the cable secure? Properly terminated?
Try "tape status" instead. Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
- Thread starter
- #7
Well I still dont know why it wouldnt work the other way, but I have another Adaptec Card (the other embedded) plugged the tape in to it started it back up and its working as 1 6 0 0 (1 0 6 0).
Dont know if there was some controller config problem from the factory with the tape on that controller as ID 6. But channel B on that controller is obviously not considered Adapter 1, my PCI scsi controller is. So I still dont know what channel B ID 6 would be because its obviously not 0 6 0 0 or maybe some sort of conflict with what ever the other device on channel A ID 6. Any way Im done with it.
I had similar problems with my 6450 Dell and the American Megatrends Raid controller and the embedded controller when i was trying to get the tape working on it.
Dell told me from the factory the Tape should be configured as Adapter 1 ID 6. But it would have never worked that way connected to the embedded controller.
Dont know if there was some controller config problem from the factory with the tape on that controller as ID 6. But channel B on that controller is obviously not considered Adapter 1, my PCI scsi controller is. So I still dont know what channel B ID 6 would be because its obviously not 0 6 0 0 or maybe some sort of conflict with what ever the other device on channel A ID 6. Any way Im done with it.
I had similar problems with my 6450 Dell and the American Megatrends Raid controller and the embedded controller when i was trying to get the tape working on it.
Dell told me from the factory the Tape should be configured as Adapter 1 ID 6. But it would have never worked that way connected to the embedded controller.
- Status