Sorry for the delay, we had a server go down.

Somewhere in the last few messages, the things I tried must have shaken
something loose.  Now, the tape drive shows up in /proc/scsi/scsi, and
the device /dev/st0 exists.  I now hold in my hot little hands the first
tape backup of this system.  (It was a different one that went down,
BTW.)

Now comes the real worry.  It works, but I don't know why.

If you have any insights as to what might have changed, let me know. 
The initial problem seems to have been that the aic7xxx module didn't
load.  After loading it manually, the st module loaded and the rest of
the stuff appeared.  Now it seems to be loading itself.  I'd really like
to know why it wasn't loading before and why it's loading now.  What
controls the loading of modules?

Again, thanks for your continued help.

-Paul

>>> [EMAIL PROTECTED] 09/17/02 06:19PM >>>
Paul Weber wrote:

>Here's the output from the various checks:
>
># cat /proc/scsi/scsi
>Attached devices:
>Host: scsi0 Channel: 00 Id: 00 Lun: 00
>  Vendor: DELL     Model: PERCRAID Mirror  Rev: 0001
>  Type:   Direct-Access                    ANSI SCSI revision: 02
>Host: scsi1 Channel: 00 Id: 05 Lun: 00
>  Vendor: ARCHIVE  Model: Python 04106-XXX Rev: 735B
>  Type:   Sequential-Access                ANSI SCSI revision: 02
>
># cat /proc/interrupts
>           CPU0       CPU1
>  0:   16155163   15826058    IO-APIC-edge  timer
>  1:        267        268    IO-APIC-edge  keyboard
>  2:          0          0          XT-PIC  cascade
>  5:          0          0   IO-APIC-level  usb-ohci
>  8:          1          0    IO-APIC-edge  rtc
> 12:       1236       1267    IO-APIC-edge  PS/2 Mouse
> 14:    1817051    1673203    IO-APIC-edge  ide0
> 20:   56327201   55696969   IO-APIC-level  aic7xxx
> 21:         15         15   IO-APIC-level  aic7xxx
> 28:     221337     216238   IO-APIC-level  eth0
> 30:    1229823    1232718   IO-APIC-level  aacraid
>NMI:          0          0
>LOC:   31980511   31980510
>ERR:          0
>MIS:          0
>
># ps ax | grep mt
> 3509 ?        D      0:00 mt -f /dev/st0 stat
>15834 pts/2    S      0:00 grep mt
>
>Note the mt command is still running from yesterday.
>
>  
>
Hmmm. Could you do a 'dmesg | grep scsi'  and let me know what it says?

Also, an 'lspci' ?

Is this a new drive, or has it been working on another machine? Can you

test it on another machine to verify it's working?

I have a symlink for /dev/tape to /dev/st0, and mt stat comes back 
immediately for me:

# mt stat
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (41010000):
 BOT ONLINE IM_REP_EN

# mt -f /dev/st0 stat
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 512 bytes. Density code 0x13 (DDS (61000 bpi)).
Soft error count since last status=0
General status bits on (41010000):
 BOT ONLINE IM_REP_EN

One more thing: what does 'uname -r' return?


>  
>




_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED] 
https://listman.redhat.com/mailman/listinfo/seawolf-list



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to