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!

super urgent tape problem

Status
Not open for further replies.

Nostradamus

Technical User
May 3, 2000
419
SE
I tried to add a different driver when adding a scsi-tape device.
ran mkdev tape and didn´t choose the standard ciss as controller but another... No that driver hangs on bootup. right after the boot: part.
There must be some way to disable that driver from starting at bootup. I´ll remove it as soon as I get to the console.
/Sören
 
A second tape drive, or a replacement tape drive?
Never have been able to get additional or different scsi tape drives right without removing the built in scsi first.
But in SCO's defense, it might be due to my choices of hardware. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 
at the Boot: prompt type hd(40)unix.old to boot from your previous kernel.

hth
stan

 
It was a replacement drive. The old DAT-tape couldn´t take backups larger then 4 Gb, and the mumps-database was to be enlarged. So I was replacing it with a DLT-tape (15 Gb uncomp.)
I removed all drivers before adding anything else. I've heard of strange problems with scsi-tapes if you don't remove old tape, relink, reboot, add tape, relink, reboot, So I even did that.

I tried different ways of booting the old kernel from boot: but I never realised I had to specify the hd(40) first. I'll remember that stan. thanks.
I entered the boot/root floppy, mounted root fs and renamed unix.old to unix. That should do it, I thought.

rebooted and it still tried to load the bloody driver.
I know I didn´t relink the kernel twice, so the unix.old should be ok?

If I renamed unix.safe (and how fun do you think that kernel was? :)) to unix, it booted all right.
I ran mkdev tape and removed the faulty tape with the weird driver. relinked and rebooted. AND IT STILL TRIED TO LOAD THE DRIVER.
I tried a little back and forth. I never understood how to make it go away. Isn't the kernel responsible for all those things loading after Boot:
%serial
%cpu
and so on?

Why did it try to load the driver, when I had removed all devices in mkdev tape

I found two tapes containing root and stand library, which I made when I installed the machine in november 2000.
I've never made any major changes since I installed the machine, have I? I said to myself.

My god, there was a LOT of stuff missing. certain users not added, the NIC was configured with an old IP, backup-scripts in crontab gone, semaphores misconfigured, NFS-mounting not present, no printers added. To name a few problems.
It was a long night but now it´s up and running.
/Sören
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top