Kevin Hemenway <[EMAIL PROTECTED]> wrote:
I'm answering both messages here, so read on...
>To update everyone, we rebooted the server on Monday, server being a RH6.0
>machine with 2.25smp. In the past, when we rebooted the machine (after
>losing functionability of the tape drive), everything would clear up and we
>would get one use out of it.
Which specific version of the kernel are you using? 'rpm -q kernel' should
tell you.
>This time, however, we didn't even get that. The tape/drive/st0 gave us the
>exact same error as was before. Now, to clear up some of the things that
>were floating around the list which you guys were waiting for me to give you
>more info <g>:
I'm still wondering about hardware issues/problems (Cabling, termination,
the actual tape drive, etc.). I know you said it was working under 5.2 -
are there any other devices hanging off the SCSI bus other than the tape
drive? If so, have they been giving you any problems? I'd be tempted to
shut down the machine and double-check all the internal cabling.
>b) Thank you all for the clarification of the kerneld being built into the
>new kernels. Saved some sanity on that one.
Given the problem at hand, you may need all you can get. ;-)
>> Run lsmod before using tape drive.
>> Run lsmod after using tape drive.
>Welp, since the tape drive never worked, I can only give you this: This is
>before we rebooted the server:
> Module Size Used by
> dummy1 716 1
> dummy0 716 1
Network devices. Are you running multiple IP addresses (AKA "virtual
hosting") on the same physical card or something of that sort? If you're
running several different websites with different domain names, this is
probably why these are loaded.
> nfsd 151192 8 (autoclean)
NFS daemon. Are you running NFS?
> lockd 31336 1 (autoclean) [nfsd]
Used by the NFS daemon.
> sunrpc 53572 1 (autoclean) [nfsd lockd]
RPC portmapper for NFS and other RPC type services.
> eepro100 12272 1 (autoclean)
Driver for your network card.
> ncr53c8xx 52752 4
The SCSI card driver.
> nls_iso8859-1 2020 (autoclean)
Native language support for "Latin 1; Western European Languages" according
to the information I have. Are you mounting strange CD-ROM's or
filesystems? I can't think of any other reason why this module would be
loaded.
>Fun thing, with the exception of a new dummy interface, the above is EXACTLY
>what I see when I run it after rebooting the machine. Likewise, running it
>just now, after our BRU backup failed produces the same results.
Ah-ha! Another BRU user. I use it here as well and I think it's great.
I'll assume for the moment that /etc/brutab isn't hosed. If you're getting
errors from mt, then that's probably not it either. Which version of BRU
are you running - 15.0 or the newer 15.1?
Have your tried tar or cpio to write to the tape? This would at least rule
out BRU as the problem.
>d) Eric suggested that I could unload the SCSI tape support driver without
>effecting the drivers for the hard drives and so on. How would I go about
>tracking down these drivers and then unloading/reloading them?
No can do without a kernel recompile. I just checked the kernel that comes
with 6.0. SCSI disk, tape and CD-ROM support are compiled in. The SCSI
card drivers modularized though. This at least eliminates the possibility
of the SCSI tape module being un/loaded as the cause of your problem.
>e) Chris suggested that since I am indeed getting tape messages back (see
>'mt -f /dev/nst0 status' below), that "the st code is present ... this is
>either the tape drive having problems with the st code or the st code having
>problems with the tape drive". Is there anyway I can diagnose this to see if
>this is my problem?
I can't image the tape drive code has changed that much?!? I suppose it's
possible, but I think unlikely. Tell us a little more about the tape drive
- make, model, age, etc.
-Eric
Eric Sisler
Library Computer Technician
Westminster Public Library
Westminster, CO, USA
[EMAIL PROTECTED]
Linux - don't fear the Penguin.
Want to know what we use Linux for?
Visit http://gromit.westminster.lib.co.us/linux
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
