Warning found in dmesg

[Andrew Kaplan]

Hi there --

I run a script which e-mails me the results of the dmesg command. The script has been running for some time on one of our servers. The server in question runs HP-UX 11.11.

This morning the following warning message appeared in the e-mail:

WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x21000; start = 314208, size = 4194304 Starting the STREAMS daemons-phase 1 Create STCP device files Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $

This just happened today. Can someone tell what I need to do to correct this? Thanks.

[Tim Nelson]

Looks to me like it is looking for a dump device and there is none configured ( you do not have to have one ). Only for processing crash dumps.

lvlnboot -v /dev/vg00 will tell you what or where dump is configured. If you did not configured then it is sharing space with swap. Effectively will be wiped once the system starts.

[Ramesh S]

Hi Andrew

The message itself means the LVM subsystem detected the dumpdevt[] dump
device table does not match with the LVM BDRA dump device configuration.
and LVM subsystem adjusted the dumpdevt[] based on the Dump LVOL defined in
the BDRA area.So, this warning can be ignored safely.

Possible areas to be checked and tried are
-- LVM BDRA information by lvlnboot commnand. -B option can help to adjust
the BDRA area.
-- setboot to update the boot device information on NVRAM that can be passed
by boot loader. (this would be the initial value of dumpdevt[]).

Thanks & Regards

Ramesh S

[Ramesh S]

Hi

You could try this one first,

# lvlnboot -R /dev/vg00

Thanks & Regards

Ramesh