dmesg errors

gobi23 — Fri, 30 Dec 2011 21:07:33 GMT

seen some dmesg errors. what could this mean??? please help

Dec 28 14:36
...
700 Recovered.
LVM: VG 64 0x010000: PVLink 31 0x0a0100 Recovered.
LVM: VG 64 0x010000: PVLink 31 0x080100 Recovered.
LVM: VG 64 0x020000: PVLink 31 0x0a3300 Recovered.
LVM: VG 64 0x020000: PVLink 31 0x083300 Recovered.
LVM: VG 64 0x020000: PVLink 31 0x0a1100 Recovered.
LVM: VG 64 0x020000: PVLink 31 0x081100 Recovered.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 2 I/O error entries were lost.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 1 I/O error entries were lost.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 3 I/O error entries were lost.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 0 I/O error entries were lost.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 4 I/O error entries were lost.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000258794000), from raw device 0x1f062200 (with priority: 0, and current flags: 0x40) to raw device 0x1f082200 (with priority: 1, and current flags: 0x0).
LVM: VG 64 0x030000: PVLink 31 0x062200 Failed! The PV is still accessible.
LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000258794000), from raw device 0x1f082200 (with priority: 1, and current flags: 0x0) to raw device 0x1f062200 (with priority: 0, and current flags: 0x80).
LVM: VG 64 0x030000: PVLink 31 0x062200 Recovered.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 8 I/O error entries were lost.

Re: dmesg errors

Dennis Handly — Fri, 30 Dec 2011 21:26:12 GMT

Are you still seeing them in syslog.log?

Re: dmesg errors

gobi23 — Fri, 30 Dec 2011 21:59:15 GMT

yes what could this mean? thanks

Re: dmesg errors

Bill Hassell — Fri, 30 Dec 2011 23:32:19 GMT

Something went wrong with one of the links between your computer and your disk. It appears that you have at least one alternate link and HP-UX switched to working link. Has someone removed a cable?

Re: dmesg errors

basant — Mon, 02 Jan 2012 12:56:17 GMT

Threse error comes , when there is some issue with physical disk

1. check for I/O error in /var/adm/syslos/syslog.log

2. check no_hw in following command output

# ioscan -fnC disk | grep -i no_hw

3. # vgdisplay -v

in the output check for disk showing unavailable.

topic Re: dmesg errors in Operating System - HP-UX

dmesg errors

Re: dmesg errors

Re: dmesg errors

Re: dmesg errors

Re: dmesg errors