advfs I/O error (followup)

From: Gerhard Nolte <gnolte_at_gwdg.de>
Date: Wed, 21 May 1997 16:58:41 +0200

Hi Gurus,

I wrote

   I get lots of error messages like

   May 21 14:56:53 libra vmunix: advfs I/O error: setId 0x32734589.000b1b77.1.8001 tag 0x00005da4.8001u page 0
   May 21 14:56:53 libra vmunix: vd 1 blk 14144384 blkCnt 96
   May 21 14:56:53 libra vmunix: read error = 5
   May 21 14:56:57 libra vmunix: advfs I/O error: setId 0x32734589.000b1b77.1.8001 tag 0x00005de3.8001u page 24
   May 21 14:56:57 libra vmunix: vd 1 blk 14150736 blkCnt 128
   May 21 14:56:57 libra vmunix: read error = 5
   May 21 14:57:04 libra vmunix: advfs I/O error: setId 0x32734589.000b1b77.1.8001 tag 0x00012847.8002u page 0
   May 21 14:57:04 libra vmunix: vd 2 blk 24768 blkCnt 128
   May 21 14:57:04 libra vmunix: read error = 5

   What do they mean (bad disk?).
   The errors started at the day, when I added a second 9 GB disk to the user
   filespace.

   Configuration is:
   Alphastation 255
   DU 3.2D-1
   2 Fujitsu 2949SYU in an external expansion box.

Following Allan Rollow (alan_at_nabeth.cxo.dec.com, thank's) I found with
uerf -R -o full
errors
********************************* ENTRY 32. *********************************

----- EVENT INFORMATION -----

EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 7547.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Wed May 21 16:26:37 1997
OCCURRED ON SYSTEM libra
SYSTEM ID x0006000D CPU TYPE: DEC 7000
SYSTYPE x00000000

----- UNIT INFORMATION -----

CLASS x0030
SUBSYSTEM x0000 DISK
BUS # x0000
                              x0030 LUN x0
                                        TARGET x6

----- CAM STRING -----

ROUTINE NAME psiop_hardintr

----- CAM STRING -----

                                        PARITY ERROR

----- UNSUPPORTED ENTRY -----

CAM ENTRY x00000430

----- UNSUPPORTED ENTRY -----

CAM ENTRY x00000431

----- UNSUPPORTED ENTRY -----


----- UNSUPPORTED ENTRY -----

CAM ENTRY x0000040E SIM_WS

********************************* ENTRY 33. *********************************

It seemed to be always the SCSI-ID 6 (the new disk) and a probelm
in the psiop_hardintr Routine

Bad hardware?

Gerhard
Received on Wed May 21 1997 - 17:19:16 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:36 NZDT