topic Re: syslog error in Operating System - HP-UX

syslog error

madhuchakkaravarthy — Mon, 05 Jul 2010 15:45:15 GMT

gettting alert for production servers running 11iv1 and 11 iv3

output for 11iv3

message from dmesg

LVM: VG 64 0x080000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
<31 0x0a1200>
LVM: VG 64 0x080000: Reestablished quorum.
LVM: VG 64 0x070000: Lost quorum.
This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
<31 0x0a1100>
LVM: VG 64 0x070000: PVLink 31 0x0a1100 Failed! The PV is not accessible.
LVM: VG 64 0x070000: Reestablished quorum.
LVM: VG 64 0x070000: PVLink 31 0x0a1100 Recovered.

--------------------------------------------------------------------------------------------------------------
syslog error

Jul 5 21:24:46 INDRSWIFT02 vmunix: LVM: VG 64 0x080000: Lost quorum.
Jul 5 21:24:46 INDRSWIFT02 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jul 5 21:24:46 INDRSWIFT02 vmunix: <31 0x0a1200>
Jul 5 21:24:46 INDRSWIFT02 vmunix: LVM: VG 64 0x080000: Reestablished quorum.
Jul 5 21:24:48 INDRSWIFT02 vmunix: LVM: VG 64 0x070000: Lost quorum.
Jul 5 21:24:48 INDRSWIFT02 vmunix: <31 0x0a1100>
Jul 5 21:24:48 INDRSWIFT02 vmunix: LVM: VG 64 0x070000: PVLink 31 0x0a1100 Failed! The PV is not accessible.
Jul 5 21:24:48 INDRSWIFT02 vmunix: LVM: VG 64 0x070000: Reestablished quorum.
Jul 5 21:24:48 INDRSWIFT02 vmunix: This may block configuration changes and I/Os. In order to reestablish quorum at least 1 of the following PVs (represented by current link) must become available:
Jul 5 21:24:48 INDRSWIFT02 vmunix: LVM: VG 64 0x070000: PVLink 31 0x0a1100 Recovered.

------------------------------------------------------------------------------------------------------------

output for 11iv3 is attached

Re: syslog error

madhuchakkaravarthy — Mon, 05 Jul 2010 15:46:35 GMT

attaching demesg.log output

Re: syslog error

Suraj K Sankari — Mon, 05 Jul 2010 15:57:44 GMT

Hi,
Run the below command
$ ll /dev/*/group

and check the VG and LV, with vgdisplay and lvdisply

vgdisplay -v
lvdisplay -v lvname

Suraj

Re: syslog error

madhuchakkaravarthy — Mon, 05 Jul 2010 16:02:23 GMT

Is there any major issue from the above log will it affect the performance of the server

Re: syslog error

Bill Hassell — Tue, 06 Jul 2010 00:00:24 GMT

> Is there any major issue from the above log will it affect the performance of the server

Yes, you have a defective disk. It appears that this disk is part of a disk mirror so the other disk is still working. That means that your system is still working. But you'll need to get the bad disk replaced as soon as possible. The details are very different depending on how the disk is connected.

Re: syslog error

nightwich — Tue, 06 Jul 2010 09:22:54 GMT

Hi madhuchakkaravarthy

YOu have a LUN with problems.

The system is responding because the LUN ha redundancy.

I don't know what type of storage you use.

But you need to identify the problem it the lun and replace the affected disk's.

Regards.

Re: syslog error

Mike Miller_8 — Tue, 06 Jul 2010 19:49:47 GMT

Look for bolt messages in your syslog.log file. My guess would be that you have a bad disk(s). If the disk is in an array you may have lost the array as well. Take a look at the "When good disks go bad" pdf to see if there's something in it that would help.

Re: syslog error

madhuchakkaravarthy — Wed, 07 Jul 2010 03:33:57 GMT

hi guys

yes ,,, disk failed in storage.

thanks for ur reply

regads

MC