1831645 Members
1944 Online
110029 Solutions
New Discussion

Re: Error in syslog

 
Utpal Krishna
Advisor

Error in syslog

Hi ,

I am getting the following error messages in Syslog from one of our HP-9000 serever.


billing cmclconfd(19588):unable to read disk c10t12d5

billing cmclconfd(19588):unable to read disk c10t12d6

billing cmclconfd(19588):unable to read disk c10t12d7

billing cmclconfd(19588):unable to read disk c10t13d0

billing cmclconfd(19588):unable to read disk c10t13d1

billing cmclconfd(19588):unable to read disk c10t13d2



Here our hostname is billing.
Can any one tell me the probable reason for it?


Thanks

Utpal
To know the best on HP-UX
5 REPLIES 5
Rajeev  Shukla
Honored Contributor

Re: Error in syslog

You are probably having problem with the disks on the system, means that the system can not see these disks.
can you have a look at ioscan -fnCdisk, do you see these disks as online,
how are these disks configured, i mean to what volume group or package they belong.
RAC_1
Honored Contributor

Re: Error in syslog

Seems to be problem with disk -- > /dev/dsk/c10t13d2

Check ioscan and if the disk is claimed.

Also check syslog,dmesg for errors associated with thid disk.

Check what diskinfo for this returns.
There is no substitute to HARDWORK
Elmar P. Kolkman
Honored Contributor

Re: Error in syslog

Problem could also be with your (SCSI/Fiber) controller, since all disks are on controller number 10, so take a look at that in the ioscan output as well.
If it is a fiber controller, and the controller is working well but all disks on it are showing as NO_HW instead of claimed, it could very well be a cable problem. This is more likely on fiber than old SCSI, since the cables are more fragile.
Every problem has at least one solution. Only some solutions are harder to find.
doug mielke
Respected Contributor

Re: Error in syslog

you can run a sar -d, and look at access times for those disks compared to others. A drive / controllor / cable going bad may make access time creep up over time.
If these drives are meaningful to your system, you'd think you'd have many errors over the day, including application level.
If you only get this message during boot, it could be that the drives have not 'spun up' yet before the system tries to read them.
David Andrews_1
Advisor

Re: Error in syslog

It looks like you probably have an issue with one of your arrays.

Run:

/opt/hparray/bin/amdsp -i

To tell you what array(s) you have on your machine. Shows Serial Number and Alias

Run:

/opt/hparray/bin/amdsp -a {Alias or Serial Number}|lp

This will show all information on your Array including Status of Contollers and disk availability/status

PS You need to be root to use this stuff.