> You're sure the tape drive, SCSI card, tape, etc., are all in working
> order? I can't help with the error messages much more than that.
We are under that assumption, yes... the material is all brand new, and the
tape drive is the same make and model as we had in an older machine running
Redhat 5.0...
> I don't have a 6.0 production server to look at, but on my 5.2 box the
init
> process always tries to load the st module, even if it's part of the
module
> and not a kernel. Have a look at /etc/rc.d/rc.sysinit and see if you
have
> something that looks like this:
>
> # If a SCSI tape has been detected, load the st module unconditionally
> # since many SCSI tapes don't deal well with st being loaded and unloaded
<snip>. That's exactly what we have in our sysinit, and someone suggested
that we comment that out...
> >* kerneld is not running.
>
> Why not? Unless you've got a monolithic kernel or have absolutely *no*
> need to load any modules, it should be running. You can run
> /usr/sbin/ntsysv to see if kerneld is started at boot time. (Or you can
> use linuxconf or one of the GUI tools.)
I, personally, didn't know anything about it until I started researching
into this problem. I was under the assumption that it was one of those
things that was default installed (at least the information I read led me
to believe that). Doing a ps doesn't show it though... I'll look into
this...
> >* Someone suggested to rebuild the kernel with st.o support. Other
>
> recommend it - there's nothing quite like the feeling of compiling your
own
> kernel and having it work. It gives you quite a sense of accomplishment.
;-)
Heh, quite true, quite true. However, as this is not my machine, per se,
but rather an ISP machine, the others around are rather hesitant on doing
something that could go wrong, no matter how step by step it could be. Much
less the fact that it's the webhosting machine, and there's a customer who
gets 90,000 hits a week and would be on the phone in a second if his site
wasn't up...
> Something you might try after the next reboot:
>
> 1) Run lsmod and see which modules are listed *before* using the tape
drive
> 2) Run lsmod again just after using the tape drive
>
> Report your findings to the list. This might help determine if indeed st
> is a module or built-in and what other module(s) are also being used.
Can do. I'll attempt this either later today or tomorrow, hopefully...
> >* I took a look back at temporarily unloading the scsi module (for the
tape
> >drive) and then reloading it, but paranoia sets in when I assume that
the
> >same scsi module is running the hard drives attached.
>
> There can be several SCSI modules involved:
>
> 1) The SCSI card driver
> 2) General SCSI support
> 3) SCSI disk support
> 4) SCSI CD-ROM support
Would the SCSI tape support be listed in the /etc/conf.modules under an
alias? We have the following:
alias scsi_hostadapter ncr53c8xx
alias eth0 eepro100
alias parport_lowlevel parport_pc
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
Kevin Hemenway
Total Net NH, LLC
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
