Re: Disk errors using ANALYZE or DIAGNOSE
From: Nic Clews (sendspamhere_at_[127.0.0.1)
Date: 05/13/04
- Next message: Dr. Dweeb: "Re: You'll never guess what HP advertised"
- Previous message: Nic Clews: "Re: Help required with CLD file"
- In reply to: Sinobato: "Disk errors using ANALYZE or DIAGNOSE"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 13 May 2004 10:28:15 +0100
Sinobato wrote:
> Is there a documentation out there that will give you some hints on 1.
> what particular section of an ANALYZE/ERROR or DIAGNOSE to look at,
> and 2. the specific disk errors that are produced when you do an
> ANALYZE/ERROR or DIAGNOSE? For example:
No - read on...
>
> ERROR SEQUENCE 7297. LOGGED ON: SID
> 13002602
> DATE/TIME 11-MAY-2004 00:31:13.74 SYS_TYPE
> 04130002
> SYSTEM UPTIME: 47 DAYS 15:08:22
> SCS NODE: MYNODE VAX/VMS
> V5.5-2H4
>
> DEVICE ERROR KA49 CPU Microcode Rev # 2. CONSOLE FW REV# 1.3
> Standard Microcode Patch Patch Rev # 19.
>
> GENERIC DK SUB-SYSTEM, UNIT _MYNODE$DKA100:
This is the first issue, GENERIC DK, so not a recognized VMS device [for
this VMS version]...
>
> HW REVISION 34303131
> HW REVISION = 1104
> ERROR TYPE 05
> EXTENDED SENSE DATA RECEIVED
> SCSI ID 01
> SCSI ID = 1.
> SCSI LUN 00
> SCSI LUN = 0.
> SCSI SUBLUN 00
> SCSI SUBLUN = 0.
> PORT STATUS 00000001
> %SYSTEM-S-NORMAL, NORMAL
> SUCCESSFUL
> COMPLETION
> SCSI CMD 3D000028
> 0000F9B6
> 0001
> READ EXTENDED
> SCSI STATUS 02
> CHECK CONDITION
>
> EXTENDED SENSE DATA
>
> EXTENDED SENSE 000300F0
> 0AF9B63D
> 00000000
> 80EA0011
> 1100
> MEDIUM ERROR
> UNRECOVERED READ ERR IN DATA
It is contained in the above fields. You will need the manufacturer data
for the drive you are using, and you should be able to decode the
extended sense data into something meaningful.
The text, well, I would be dubious of its accuracy as you've no
guarantee that a generic device reports the same sense codes as a
"Digital Storage Architecture" compliant device would.
> UCB$B_ERTCNT 00
> 0. RETRIES REMAINING
> UCB$B_ERTMAX 00
> 0. RETRIES ALLOWABLE
> ORB$L_OWNER 00010004
> OWNER UIC [001,004]
> UCB$L_CHAR 1C4D4008
> DIRECTORY STRUCTURED
> FILE ORIENTED
> SHARABLE
> AVAILABLE
> MOUNTED
> ERROR LOGGING
> CAPABLE OF INPUT
> CAPABLE OF OUTPUT
> RANDOM ACCESS
> UCB$W_STS 0000
> UCB$L_OPCNT 02817364
> 42038116. QIO'S THIS UNIT
> UCB$W_ERRCNT 000B
> 11. ERRORS THIS UNIT
> IRP$W_BCNT 0200
> TRANSFER SIZE 512. BYTE(S)
> IRP$W_BOFF 0000
> TRANSFER PAGE ALIGNED
> IRP$L_PID 0060008B
> REQUESTOR "PID"
> IRP$Q_IOSB 00000000
> 00000000 IOSB, 0. BYTE(S) TRANSFERRED
>
> This error seems to be critical due to the MEDIUM ERROR message, but
> it also seems to be non-critical as the port status says it had a
> normal successful completion.
>
> I have already tried looking at the VMS manuals but there are no such
> information there. Hopefully, by knowing at least some ideas on the
> criticality of these error messages, I will know when to escalate to
> the vendor or just ignore an error message.
But are you seeing the first attempt at the read failed logged, then the
second attempt was successful?
-- Regards, Nic Clews a.k.a. Mr. CP Charges, CSC Computer Sciences nclews at csc dot com
- Next message: Dr. Dweeb: "Re: You'll never guess what HP advertised"
- Previous message: Nic Clews: "Re: Help required with CLD file"
- In reply to: Sinobato: "Disk errors using ANALYZE or DIAGNOSE"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
