Ok, here's some more information concerning the tape drive problems I've
been having. You'll have to check the archives for the original thread if
you've missed it, cos it's a long one <g>...

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.

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>:

a) The tape drive is internal, so I can't "power-cycle" it.

b) Thank you all for the clarification of the kerneld being built into the
new kernels. Saved some sanity on that one.

c) > 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
    nfsd                  151192   8  (autoclean)
    lockd                  31336   1  (autoclean) [nfsd]
    sunrpc                 53572   1  (autoclean) [nfsd lockd]
    eepro100               12272   1  (autoclean)
    ncr53c8xx              52752   4

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.

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?

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?

    <error message here - i'm in a telnet so I can't c-n-p right now>
    SCSI 2 tape drive:
    File number=-1, block number=-1, partition=0.
    Tape block size 0 bytes. Density code 0x0 (default).
    Soft error count since last status=0
    General status bits on (10000):
    IM_REP_EN

There you go. Talk amongst yourselves.

---------------------------------------------------------------------
Total Net NH, LLC             EMAIL: <[EMAIL PROTECTED]>
15 Pleasant St., Suite 11     WEBSITE: <http://www.totalnetnh.net/>
Concord, NH 03301
(603) 225-8422                SEARCH: <http://www.lycos.com/>
---------------------------------------------------------------------



-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to