Big problem with the declaration of a DAT on SCO 5.0.3

[gess42]

Hello,

I have a very strange Problem! I can't acces my SCSI tape with the device nodes /dev/rct1.

It only works with /dev/rmt0 but i need to use rct1.

I found some documentations but it doesn't work...

I use the "mkdev tape" command but that command don't create the rct1 in /dev directory.

Someone could give me the solution? Step by step if it's possible?

Thanks

 

[PHV]

i need to use rct1
but it doesn't work
Any chance you could elaborate ?
If you have only one SCSI tape you may link the device nodes created by mkdev tape to meet your requirements, e.g.:
ln /dev/rStp0 /dev/rct1

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ181-2886

 

[gess42]

Thanks for your answer

In fact, i have made that command but it didn't work!

Now, i just want to create the /dev/rct1 because it disapear :-(

 

[stanhubble]

if the sym link doesn't work (???) you can use mknod

/etc/mknod /dev/rct1 c MM mm

where MM is the major device number
and mm is the minor device number (ls -al /dev/rmt0)

are you sure that it is version 5.0.3 ?? (uname -X)

 

[gess42]

Yes, sorry for the mistake!

It's a 5.0.6 Environment.


Do you think that i must reboot after any "mkdev tape" command? At the end, i must compilate the kernel and i never reboot!

Perhaps it's the reason of my problems!

Last time, a kernel error occured when i compilate it

 

[motoslide]

Can you provide any history of this problem? Has the tape drive worked for years, then suddenly quit working? Is this a 2nd tape drive?

Please post the results of these commands:

hwconfig -h

mkdev .scsi (Display current SCSI configuration)

IMPORTANT: On the "mkdev .scsi" menu, do not run any other option. Just do the "Display" and exit!

 

[gess42]

Like you said, it suddenly stop working.
There's just one tape drive on the server.


I have used to much time the "mkdev tape" commands and now i'm "afraid" with it

Last time, i have a kernel panic and my /etc/default/boot file has disapear...

That's why i would like some help before breaking my system^^




# hwconfig -h
device address vec dma comment
====== ======= === === =======
kernel - - - rel=3.2v5.0.6 kid=2000-07-27
cpu - - - unit=1 family=6 type=gt PentIII
cpuid - - - unit=1 vend=GenuineIntel
tfms=0:6:11:1(4)
fpu - 13 - unit=1 type=80387-compatible
pci 0xcf8-0xcff - - am=1 sc=1 buses=11
PnP - - - nodes=0
clock - - - type=TSC/1263442701Hz
serial 0x3f8-0x3ff 4 - unit=0 type=Standard nports=1 fifo=yes
serial 0x2f8-0x2ff 3 - unit=1 type=Standard nports=1 fifo=yes
console - - - unit=vga type=0 num=12 scoansi=1
scroll=50
floppy 0x3f2-0x3f7 6 2 unit=0 type=135ds18
kbmouse 0x60-0x64 12 - type=Keyboard|PS/2 mouse id=0xFF
parallel 0x378-0x37a 7 - unit=0
adapter 0x1f0-0x1f7 14 - type=IDE ctlr=primary dvr=wd
csmu - - - Compaq SCSI-2 Management driver (rev
5.44a)
cled - - - Compaq ProLiant Storage System (rev
5.44a)
pcibios - - - PCI BIOS (2.16), Hardware Mechanism 1
cpqw 0x1800-0x18ff 5 - Compaq Wellness driver (ver 5.44a)
crom - - - Compaq rom driver (rev 5.44a)
n100c0 0x2000-0x201f 10 - type=Compaq 10/100 00:0e:7f:b0:39:ec
adapter 0x3400-0x34ff 11 - type=ad160 ha=0 slot=0 bus=0 id=7
fts=sto
adapter 0x3000-0x30ff 11 - type=ad160 ha=1 slot=0 bus=0 id=7
fts=sto
adapter 0x3800-0x3900 11 - type=ciss ha=0 PCI slot=5 (rev 5.44a)
cd-rom - - - type=IDE ctlr=pri cfg=mst dvr=Srom->wd
tape - - - type=S ha=0 id=6 lun=0 bus=0 ht=ad160
tape - - - type=S ha=0 id=5 lun=0 bus=0 ht=ad160
disk - - - type=S ha=0 id=0 lun=0 bus=0 ht=ciss
Sdsk - - - cyls=8716 hds=255 secs=32 fts=stdb







The configuration file currently has entries for the following devices:

Host
Adapter Adapter
Type Device Number ID LUN Bus
-------------------------------------------
ciss disk 0 0 0 0
wd cd-rom 0 0 0 0
ad160 tape 0 6 0 0

Press any key to continue:


Ps: ad160 is my SCSI card (adaptec)

 

[motoslide]

The "mkdev tape" can be a problem if it doesn't finish cleanly each time. You've already got a kernel which is confused. The "hwconfig" shows 2 tape entries, but "mkdev .scsi" only shows 1. Check out all the links in this page (thanks to Tony Lawrence (aka pcunix)):

http://aplawrence.com/Unixart/tapes.html

Your system is running the Compaq EFS. Personally (and I'll probably get flamed for saying this), I dispise these utilities, as they seem to muddle things up more than they help. Admittedly, this is probably because I've never taken the time to learn what each of these utilities can do. In your case, you may want to hear from somebody who knows the Compaq EFS well enough to know if these would affect how you correct the broken kernel files.

 

[gess42]

I have test Tony Lawrence's posts but my problem is always present.

Now, i have a ghost tape drive that appear with the "mkdev tape" command, but i can't delete it....

And i can't read/write anymore

 

[gess42]

I have delete it and create a new /dev/rct0

But i can't read/write on my tape drive.

Grrrrrrrrr

 

[motoslide]

Did you read those 4 articles referenced on Tony's page? Did any of them appear to apply to the symptoms you get while trying to re-compile the kernel?
Earlier you had asked if you needed to reboot after running "mkdev tape". Yes, that would be required.
I think your first concern is to get the kernel to re-compile without errors. If you feel you are unable to safely perform the steps outlined in those SCO articles, I'd recommend you seek a local support person.

For future reference: If you have a tape drive which suddenly fails, the odds are VERY GOOD that the drive is simply bad. You should be able to replace the drive with a similar device set to the same SCSI ID and leave it at that. You only need to run "mkdev tape" if you are adding an additional device, moving the drive to a different SCSI channel (or SCSI ID), or something similar.