An error in dmesg

[Veron Le]

I face with this error. What does it mean???
Pls help.
Veron.
----------------dmesg---------------------

........
btlan4: Initializing 10/100BASE-TX card at 8/8/2/0....
HP EISA Mux Driver, FILESET EISA-MUX-KRN Version B.11.00.03
Copyright (c) 1997 Hewlett-Packard Company
eisa_mux0: Driver Enabled for board 1 at HW path (8/20/5/7).
btlan4: Initializing 10/100BASE-TX card at 8/8/1/0....
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 4194304
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x5000; start = 310112, size = 2097152
Starting the STREAMS daemons-phase 1
btlan4: NOTE: MII Link Status Not OK - Check Cable Connection to Hub/Switch at 8/8/2/0....
Create STCP device files
Starting the STREAMS daemons-phase 2
B2352B/9245XB HP-UX (B.11.00) #1: Thu Nov 6 01:58:21 PST 1997

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 1048576 Kbytes, lockable: 873656 Kbytes, available: 908132 Kbytes

scb->cdb: 12 00 00 00 80 00
scb->cdb: 12 01 80 00 ff 00
scb->cdb: 12 00 00 00 80 00
scb->cdb: 12 01 80 00 ff 00
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. 9 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. 7 I/O error entries were lost.

-------------------end of dmesg---------------

[Mark Grant]

Pretty much what it says.

Some hardware is producing errors and you need to run "stm" to find out what it is and use the "logtool" utility.

[dbk]

Hello Veron,

You also might take a look at syslog -- any errors in there ?? If so what are they ?

Regards,
dbk.

[T G Manikandan]

Just check the /var/adm/syslog/syslog.log file.
Looks like hard disk have gone bad.

Also make sure that the network configuartion is ok. server and the switch match with speed and duplex.

[dbk]

Veron,
One other thing - if you do have an error message in syslog with the format --

dev=0x1f123456

You can do the following to find out what device it is.

ll /dev/* | grep 123456

Regards,
dbk

[Veron Le]

Hi,

This is syslog.log file.
Pls help

[Mark Grant]

Have you tried running this command

/opt/resmon/bin/resdata -R 157548584 -r /storage/events/disk_arrays/High_Availability/8_12.5 -n 163250177 -a

[Mark Grant]

Do you have more than three packages configured in your service guard cluster?

[Veron Le]

Mark,

customer say that they cannot run that command due to not find this folder: /storage/events/disk_arrays/High_Availability/.....

Otherwise, pls refer to array_log_error file that is attached here.
Thanks

[Mark Grant]

I think you need to get an HP Engineer in to check out the array. It seems to be not very happy!

[Veron Le]

We connect to Raid directly and check....everything seems to be OK.