strange massege in the syslog

[I.Delic]

Hi,

Today i got this strange massage in my syslog file. It is something about disk. I send you the output of my ioscan file too. We have 8 disk in our machine.
The are on the another hardware path thah this massage says. I dont get it.
Is something wrong with my systeem? We did use a lot our tape device to backup en restore some files.

if i use vgdisplay -v vg00 i see al mu disk (2)
And if i use vgdisplay -v vg01 i see the another 6 disk. They are al available and sync.

Sorry about my english lenguage it is not very wel but i'm working on it

thank you in advance

Idriz

[I.Delic]

this is my iocan

[Robert-Jan Goossens]

Hi Idriz,

Looks like your controller logged a failure. If you look at the hardware address from ioscan you can match them. 0/0/1/0.1.0 to c0t1d0 etc...


disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 9 0/0/1/0.1.1 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d1 /dev/rdsk/c0t1d1
disk 10 0/0/1/0.1.2 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d2 /dev/rdsk/c0t1d2
disk 11 0/0/1/0.1.3 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d3 /dev/rdsk/c0t1d3
disk 12 0/0/1/0.1.4 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d4 /dev/rdsk/c0t1d4
disk 13 0/0/1/0.1.5 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d5 /dev/rdsk/c0t1d5
disk 14 0/0/1/0.1.6 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d6 /dev/rdsk/c0t1d6
disk 15 0/0/1/0.1.7 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d7 /dev/rdsk/c0t1d7


You could run next command to get some more info.

# /opt/resmon/bin/resdata -R 322109563 -r /storage/events/disks/default/0_0_1_0.1.7 -n 322109475 -a

Regards,
Robert-Jan

[Devender Khatana]

Hi Idriz,

The error details can be get by executing the following commands on the same system.

#/opt/resmon/bin/resdata -R 322109545 -r /storage/events/disks/default/0_0_1_0.1.1 -n 322109469 -a

#/opt/resmon/bin/resdata -R 322109548 -r /storage/events/disks/default/0_0_1_0.1.2 -n 322109470 -a

#/opt/resmon/bin/resdata -R 322109551 -r /storage/events/disks/default/0_0_1_0.1.3 -n 322109471 -a

#opt/resmon/bin/resdata -R 322109554 -r /storage/events/disks/default/0_0_1_0.1.4 -n 322109472 -a

#/opt/resmon/bin/resdata -R 322109557 -r /storage/events/disks/default/0_0_1_0.1.5 -n 322109473 -a

# /opt/resmon/bin/resdata -R 322109560 -r /storage/events/disks/default/0_0_1_0.1.6 -n 322109474 -a

#/opt/resmon/bin/resdata -R 322109563 -r /storage/events/disks/default/0_0_1_0.1.7 -n 322109475 -a

All these outputs can be also found in /var/opt/resmon/log/event.log

Either post the output of all these commands or attach the file to help further.

HTH,
Devender

[Sameer_Nirmal]

As shown in the syslog , the most recent event to be noticed is I/O probe done by kernel for "0/0/1/0.1 tgt" bus and LUNs ( disks ).
Moreover in ioscan all those disks in "0/0/1/0.1 tgt" bus are not showing the their Description field. This may be because of the a troubling device on that bus or the bus itself which hampers reading of Description field of all disks.

Similarly in syslog , there is an event which shows I/O timeout on c0t1d0. I am suspecting this disk is troubling disk ( nearing to die sometime!!! )

I would advice to run those commands to know the detailed EMS event description first.
Then
#ioscan -fn
#diskinfo -v (all those disks on that bus)
( Check their firmware version as well )

Let us know about these to help you further.

[Sameer_Nirmal]

Run cstm/mstm to verify system hardware as well.

[I.Delic]

hi,

this is our event.log file

thank you in advance

idriz

[Sameer_Nirmal]

The event log shows "software configuration" error for all disks except "c0t1d0" on account wrong LUN ( 0 in this case ).
Again I suspect the disk c0t1d0 as culprit here. This disk is creating problem which in turn causing the SCSI command to run for testing a drive ( Operation code : TEST UNIT READY ) with LUN 0 on 0/0/1/0.1 taget bus.

Since all other disks are being targeted ( part of the bus query ) with LUN 0 , they can't fulfill the request. Hence the Product/Device information is not being shown in the ioscan and you see those EMS events.

I assume that all those disks are supported by HP. Am I right?

If possible take out that disk c0t1d0 from your system ( following LVM commands to remove a disk ) and observe if you are getting those EMS events.

Did you run cstm/mstm , diskinfo , ioscan
commands?

[I.Delic]

we have only 8 disk's

see ioscan output
disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 9 0/0/1/0.1.1 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d1 /dev/rdsk/c0t1d1
disk 10 0/0/1/0.1.2 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d2 /dev/rdsk/c0t1d2
disk 11 0/0/1/0.1.3 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d3 /dev/rdsk/c0t1d3
disk 12 0/0/1/0.1.4 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d4 /dev/rdsk/c0t1d4
disk 13 0/0/1/0.1.5 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d5 /dev/rdsk/c0t1d5
disk 14 0/0/1/0.1.6 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d6 /dev/rdsk/c0t1d6
disk 15 0/0/1/0.1.7 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d7 /dev/rdsk/c0t1d7
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 3 0/4/0/0.0.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 4 0/4/0/0.2.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 5 0/4/0/0.4.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
disk 6 0/7/0/0.0.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 7 0/7/0/0.2.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk 8 0/7/0/0.4.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t4d0 /dev/rdsk/c6t4d0

i don't witch divice are connect to the 0/0/1/0.1.1 . maybe our tape device or DVD ?

This is strange to me . Al disk ar good.

idriz

[Fabio Ettore]

Hi Idriz,

disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 9 0/0/1/0.1.1 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d1 /dev/rdsk/c0t1d1
disk 10 0/0/1/0.1.2 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d2 /dev/rdsk/c0t1d2
disk 11 0/0/1/0.1.3 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d3 /dev/rdsk/c0t1d3
disk 12 0/0/1/0.1.4 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d4 /dev/rdsk/c0t1d4
disk 13 0/0/1/0.1.5 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d5 /dev/rdsk/c0t1d5
disk 14 0/0/1/0.1.6 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d6 /dev/rdsk/c0t1d6
disk 15 0/0/1/0.1.7 sdisk CLAIMED DEVICE
/dev/dsk/c0t1d7 /dev/rdsk/c0t1d7



I think you are having troubles about these disks because HP-UX driver for disk (sdisk) doesn't support hose disks. What it is strange for me is why under description there isn't a description for those disks! Like you see by ioscan you have 2 SEAGATE ST318404LC and 6 HP 18.2GST318452LC. So my question is: what are those other disks? What is the vendor? Are you sure they are disks supported by HP? That should explain all situation:


The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.


You are seeing this error just for those disks, sdisk seems to not support them and infact HP-UX doesn't report any description for them. So the message doesn't seem so strange.

Can you check what kind of storage or what kind of disks are connected?

Best regards,
Fabio

[Devender Khatana]

Hi,

If your system has only 8 disks than I think there is some problem. As your system is accessing 16 disks, The other 8 weird disks which are being accessed are accessed as LUNs and the drive for normal disk does not support that giving the error is EMS repeatedy.

This could happen due to some SCSI cable /termination issue. A reboot shall resolve this and start showing only 8 disk devices.

HTH,
Devender

[Andrew Merritt_2]

You've got a very old version of the OnlineDiags installed, A.28.00, which is the September 2001 version.

I'd recommend upgrading to the latest version, which is A.47.00, plus PHSS_32924.

That could well prevent the EMS events being logged, since more recent versions handle the various LUNs associated with virtual arrays much better, among other changes.

I don't know what is creating those LUNs, though, they look very odd. They are definitely associated with the sdisk driver, which is why it is disk_em that is logging the events.

Andrew

[I.Delic]

Hi,

Like i said we have only 8 disk's.
They are all good.(see ioscan).

This is my old ioscan when evrything was well:

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.2.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 3 0/4/0/0.0.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 4 0/4/0/0.2.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t2d0 /dev/rdsk/c5t2d0
disk 5 0/4/0/0.4.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c5t4d0 /dev/rdsk/c5t4d0
disk 6 0/7/0/0.0.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 7 0/7/0/0.2.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t2d0 /dev/rdsk/c6t2d0
disk 8 0/7/0/0.4.0 sdisk CLAIMED DEVICE HP 18.2GST318452LC
/dev/dsk/c6t4d0 /dev/rdsk/c6t4d0


The path disk 0 0/0/1/0.1.0 is an DVD player and ik think he is a couse of my probleem.

sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0


We dont't have a 16 disk . we have only 8 + one dvd palyer.

I hoop it is little bit clear what i mean


thank you all for your responses


idriz

[Fabio Ettore · Accepted solution]

Hi Idriz,

ok I was missing about that ioscan was an old output. Then like Davender said just reboot your system or before of that update the STM version.

I think after those operations you shouldn't obtain anymore messages in syslog.log.

Best regards,
Fabio

[Sameer_Nirmal]

That was exactly what I mentioned in my last post as c0t1d0 0/0/1/0.1.0 is creating problem.

Since EMS event were generated for this device , there has to be physical presence of device as well.

I wished you could have post the output of those commands which I had asked in my first post which would have made the picture clear.

As you compared with old ioscan , things are quite clear now and DVD-ROM is the culprit.

If you could de-attach the DVD-ROM and run ioscan again , you probably won't get that weired ioscan output.

It is better to get STM upgraded to latest version.

[I.Delic]

Thank you for your all responses. My probleem is solved. HP has changed our DVD player . After that evrything was good.

Idriz