topic Re: System showing Disk error in Operating System - Tru64 Unix

System showing Disk error

admin1979 — Wed, 01 Jul 2009 06:19:51 GMT

Hello Experts,

We are using Digital UNIX V4.0F. We noticed a Disk error in binary log as shown here.

PLUTO@/> sizer -v
Digital UNIX V4.0F (Rev. 1229); Tue Aug 20 16:26:52 MET DST 2002

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

EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 5316.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Wed Jul 1 03:03:07 2009
OCCURRED ON SYSTEM PLUTO
SYSTEM ID x00070016
SYSTYPE x00000007
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000

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

CLASS x0033
SUBSYSTEM x0000 DISK
BUS # x0001

************ ENTRY 2. ************
----- EVENT INFORMATION -----

EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 5315.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Wed Jul 1 03:03:07 2009
OCCURRED ON SYSTEM PLUTO
SYSTEM ID x00070016
SYSTYPE x00000007
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000

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

CLASS x0033
SUBSYSTEM x0000 DISK
BUS # x0001

But the disk info not giving complete path as Bus/Target/LUN. So the question is which disk is failing?

Here is the output you may require,

PLUTO@/> scu show edt

CAM Equipment Device Table (EDT) Information:

Device: RRD46 Bus: 0, Target: 5, Lun: 0, Type: Read-Only Direct Access
Device: BD018635C4 Bus: 3, Target: 0, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 1, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 2, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 3, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 4, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 5, Lun: 0, Type: Direct Access
Device: BD0366459B Bus: 3, Target: 6, Lun: 0, Type: Direct Access

Please let us know if you need any more info.

Thanx,
admin

Re: System showing Disk error

Rob Leadbeater — Wed, 01 Jul 2009 10:49:38 GMT

Hi admin,

The full output of uerf might provide more information...

# uerf -R -o full | more

Cheers,

Rob

Re: System showing Disk error

admin1979 — Wed, 01 Jul 2009 11:32:05 GMT

Hello,

This is what I got after the command,

********************************* ENTRY 1. *********************************

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

EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 5316.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Wed Jul 1 03:03:07 2009
OCCURRED ON SYSTEM bwgc457
SYSTEM ID x00070016
SYSTYPE x00000007
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000

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

CLASS x0033
SUBSYSTEM x0000 DISK
BUS # x0001

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

ROUTINE NAME spo_process_ccb

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

A SCSI bus reset has been done

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

Unknown frame - SIMPORT_SOFTC

Thanx,
admin

Re: System showing Disk error

admin1979 — Thu, 02 Jul 2009 04:21:06 GMT

Anyone please?

Re: System showing Disk error

Pieter 't Hart — Thu, 02 Jul 2009 06:37:48 GMT

the event logs bus #1
>>>
CLASS x0033
SUBSYSTEM x0000 DISK
BUS # x0001
<<<
devices only in use on bus #0 and bus #3 .
>>>
Device: RRD46 Bus: 0, Target: 5, Lun: 0, Type: Read-Only Direct Access
Device: BD018635C4 Bus: 3, Target: 0, Lun: 0, Type: Direct Access
Device: BD018635C4 Bus: 3, Target: 1, Lun: 0, Type: Direct Access
<<<

maybe a cable to bus#1 loose on the system ?
maybe to a tapeunit, because it don't show up in scu show edt.

Re: System showing Disk error

admin1979 — Thu, 02 Jul 2009 06:39:56 GMT

Thanks for the reply. Is there any way to find out the Bus # in the system. I have no idea how to know what Bus number the devices are connected.

Re: System showing Disk error

Pieter 't Hart — Thu, 02 Jul 2009 07:23:12 GMT

your "scu show edt" output displays the bus# for the devices, the target# is the scsi-id on the bus.

you can try "scu show path-inquiry all"
to display all available interfaces.

you'll have to match this with the physical information.

Re: System showing Disk error

admin1979 — Thu, 02 Jul 2009 08:16:13 GMT

Hello,

Sorry. But I have no idea what to match.

Version Number For The SIM/HBA: 2.5
SCSI HBA Capabilities Flags: 0x12
0x10 = Supports SDTR message.
0x2 = Supports tag queue message.
Target Mode Support Flags: 0
Miscellaneous HBA Feature Flags: 0
The HBA Engine Count: 0
Targets Supported by HBA: 8
LUNs Supported by HBA: 8
Vendor Unique Capabilities: 0 0 0 0 0 0 0 0 0 0 0 0
Size of SIM Private Data Area: 56
Async Callback Capabilities: 0xf3 Reasons for generating async event:
0x80 = New devices found during rescan.
0x40 = SIM module de-registered.
0x20 = SIM module registered.
0x10 = Sent bus device reset to target.
0x2 = Unsolicited reselection.
0x1 = Unsolicited SCSI bus reset.
Highest HBA Path ID Assigned: 0
SCSI Device ID of Initiator: 7
The Vendor ID of the SIM: DEC OSG BSD/V1
The Vendor ID of the HBA: DEC WSE BSD/V1
The OSD Usage Pointer: 0

Thanks,
admin

Re: System showing Disk error

Pieter 't Hart — Thu, 02 Jul 2009 09:07:54 GMT

root@eagle # scu sho path-inquiry all

Path Inquiry Information:

Bus Initiator HBA Vendor ID Version Targets LUNs
--- --------- ------------- ------- ------- ----
0 255 KGPSA-CA 4.05 255 255
1 7 Symbios 53C895 4.12 16 8
2 7 ACER M1543C 2.05 2 1
3 7 ACER M1543C 2.05 2 1

root@eagle #

I don't think output will be very different from V5.1B instead 4.0F
maybe you didn't give the "all" option?

Re: System showing Disk error

admin1979 — Thu, 02 Jul 2009 10:22:31 GMT

Hello,

Maybe you are bit right. I tried the same command on V4.0G and it gave the desired output. But this system is V4.0F. Moreover I also checked the scu help by going in scu menu.
The all option is not listed even in help pages. See here the relevant part.

show subtopic: path-inquiry

show path-inquiry

This command displays the CAM Path Inquiry information. If the nexus
information is omitted, then the path inquiry information associated
with the selected device is displayed.

Format:

scu> show path-inquiry [nexus-information] <<<>>>

Example:

% scu show path

Path Inquiry Information:

Version Number For The SIM/HBA: 4.12
SCSI HBA Capabilities Flags: 0x12
0x10 = Supports SDTR message.
0x2 = Supports tag queue message.
Target Mode Support Flags: 0
Miscellaneous HBA Feature Flags: 0
The HBA Engine Count: 0
Targets Supported by HBA: 8
LUNs Supported by HBA: 8
Vendor Unique Capabilities: 0 0 0 0 0 0 0 0 0 0 0 0
Size of SIM Private Data Area: 56
Async Callback Capabilities: 0xf3 Reasons for generating async event:
0x80 = New devices found during rescan.
0x40 = SIM module de-registered.
0x20 = SIM module registered.
0x10 = Sent bus device reset to target.
0x2 = Unsolicited reselection.
0x1 = Unsolicited SCSI bus reset.
Highest HBA Path ID Assigned: 0
SCSI Device ID of Initiator: 6
The Vendor ID of the SIM: DEC OSG BSD/V1
The Vendor ID of the HBA: DEC WSE BSD/V1
The OSD Usage Pointer: 0

%

Another investigation leads me to interesting level, I did scu show log and got the error as ,

scu: All or part of device nexus information (bus/target/lun) is NOT setup!.

Could this be the reason for all the missing outputs ??

Thanks,
admin