rgc@wam.umd.edu (Ross Garrett Cutler) (09/16/90)
Hello,
We have a VAXstation 3200 (ba23) with the following devices:
- 300 MB HD (MSCP)
- 600 MB HD (SCSI, but looks like a MSCP)
- 600 MB optical (SCSI, but looks like MSCP)
- line printer (lp0)
- 9 track tape drive (digi-data)
- ethernet (delqa)
- TK50
- vcb02 video subsystem (graphics console)
- 16 MB RAM
We've been getting an "RX-50" error (shown below, after the config file)
that we don't know what to make of. A RX-50 is a DEC floppy drive,
but we don't have one. Since our system works fine, we didn't
worry about it much; and we hoped that it would disapear with ULTRIX 4.0.
But it's still here, and it's filling up our error logger file. Any ideas?
Thanks much...
--- config file ---
ident "NEUROVAX"
machine vax
cpu "VAX3600"
maxusers 32
processors 1
maxuprc 50
physmem 16
timezone 5 dst 1
options EMULFLT
options QUOTA
options INET
options NFS
options RPC
options DLI
options UFS
options UWS
config vmunix root on ra0a swap on ra0b dumps on ra0b
adapter uba0 at nexus?
controller uda0 at uba0
controller uq0 at uda0 csr 0172150 vector uqintr
disk ra0 at uq0 drive 0
controller klesiu0 at uba0
controller uq16 at klesiu0 csr 0174500 vector uqintr
tape tms0 at uq16 drive 0
controller zs0 at uba0 csr 0172520 vector tsintr
tape ts0 at zs0 drive 0
device qd0 at uba0 csr 0177400 flags 0xf vector qddint qdaint qdiint
device qe0 at uba0 csr 0174440 vector qeintr
device lp0 at uba0 csr 0177514 vector lpintr
controller uda1 at uba0
controller uq17 at uda1 csr 0160334 vector uqintr
disk ra1 at uq17 drive 0
disk ra2 at uq17 drive 1
disk ra3 at uq17 drive 2
disk ra4 at uq17 drive 3
controller hl0 at uba0 csr 0174400 vector rlintr
disk rl0 at hl0 drive 0
scs_sysid 1
pseudo-device nfs
pseudo-device rpc
pseudo-device dli
pseudo-device pty
pseudo-device loop
pseudo-device ether
pseudo-device ufs
pseudo-device inet
--- sample error logger entry ---
********************************* ENTRY 9. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 102. DISK ERROR
SEQUENCE NUMBER 0.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Sun Sep 16 11:33:57 1990 EDT
OCCURRED ON SYSTEM neurovax.med
SYSTEM ID x0A000004 MICROCODE REV = 4.
SYSTYPE REG. x01530102
FIRMWARE REV = 83.
PROCESSOR TYPE KA650
----- UNIT INFORMATION -----
UNIT CLASS DSA DISK
UNIT TYPE RX50
CONTROLLER NO. 0.
UNIT NO. 0.
ERROR SYNDROME DISK TRANSFER ERROR
********************************* ENTRY 10. *********************************
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 102. DISK ERROR
SEQUENCE NUMBER 1.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Sun Sep 16 11:33:57 1990 EDT
OCCURRED ON SYSTEM neurovax.med
SYSTEM ID x0A000004 MICROCODE REV = 4.
SYSTYPE REG. x01530102
FIRMWARE REV = 83.
PROCESSOR TYPE KA650
----- UNIT INFORMATION -----
UNIT CLASS DSA DISK
UNIT TYPE RX50
CONTROLLER NO. 0.
UNIT NO. 0.
ERROR SYNDROME DISK TRANSFER ERROR
********************************* ENTRY 11. *********************************
--
Please email -- I'll summarize.
Ross Cutler
University of Maryland, College Park
Internet: rgc@wam.umd.eduenvbvs@epb2.lbl.gov (Brian V. Smith) (09/18/90)
In article <1990Sep16.163246.3545@wam.umd.edu>, rgc@wam.umd.edu (Ross Garrett Cutler) writes: |> Hello, |> We have a VAXstation 3200 (ba23) with the following devices: |> - 300 MB HD (MSCP) |> - 600 MB HD (SCSI, but looks like a MSCP) |> - 600 MB optical (SCSI, but looks like MSCP) |> - line printer (lp0) |> - 9 track tape drive (digi-data) |> - ethernet (delqa) |> - TK50 |> - vcb02 video subsystem (graphics console) |> - 16 MB RAM |> |> We've been getting an "RX-50" error (shown below, after the config file) |> that we don't know what to make of. A RX-50 is a DEC floppy drive, |> but we don't have one. Since our system works fine, we didn't |> worry about it much; and we hoped that it would disapear with ULTRIX 4.0. |> But it's still here, and it's filling up our error logger file. Any ideas? |> Thanks much... We are also getting those RX-50 errors on our VAXstation II (ba23), and we have no RX-50. If anyone knows that the heck is going on, I would also like to know. -- Brian V. Smith (bvsmith@lbl.gov) Lawrence Berkeley Laboratory I don't speak for LBL; they don't pay me enough for that.