1836649 Members
2091 Online
110102 Solutions
New Discussion

Syslog log error message

 
Mohd Farouk Bin Baharim
Occasional Contributor

Syslog log error message

I found there were a lot of lines like below in syslog.log file. This message happends frequently started this week. What's that mean ?


Jan 7 01:14:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:14:28 takaful3 vmunix: lv_readvgdats: Could not read VGDA 1 header & trailer from disk H/W path 10/8.8.0.255.0.0.0 (error = 5)
Jan 7 01:14:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:14:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:14:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:14:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:14:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
Jan 7 01:16:28 takaful3 vmunix: LVM: vg[1]: pvnum=0 (dev_t=0x1f050000) is POWERFAILED
Jan 7 01:16:28 takaful3 vmunix: LVM: PV 0 has been returned to vg[1].
4 REPLIES 4
Cheryl Griffin
Honored Contributor

Re: Syslog log error message

Check the disk is vg01, c5t0d0.

Is the disk ok physically? If this were an external disk, check the cabling.

Test it wtih dd:
# dd if=/dev/dsk/cXdXtX of=/dev/null bs=64 count=1000
If successful, the results of this command will look similar to:
100+0 records in
100+0 records out

If you have diagnostics installed, are there errors be logged against the disk.

"Downtime is a Crime."
Steven E. Protter
Exalted Contributor

Re: Syslog log error message

If Cheryl's test isn't enough(it should be) you might want to try firing up mstm or xstm and exercising the disks.

On a physical level you might have a problem with termination or power flow through your drive cage(if applicable).

I'd be thinking about backing up any data on that drive, doing a make_tape_recovery on the box if the disk is involved in booting.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Fabio Ettore
Honored Contributor

Re: Syslog log error message

Hi,

Cheryl's test could help you to know better reasons of problem; anyway I think that it is a bad disk (/dev/dsk/c5t0d0) and should be substituted as soon as possible.

Best regards,
Ettore
WISH? IMPROVEMENT!
Michael Schulte zur Sur
Honored Contributor

Re: Syslog log error message