1833698 Members
3802 Online
110062 Solutions
New Discussion

regarding dump

 
SOLVED
Go to solution
Sridhar R
Regular Advisor

regarding dump


Below is my syslog.log file which shows the warning for DUMP.

What could be the problem and the possible solution??


Feb 11 05:38:42 cdbap101 vmunix: Logical volume 64, 0x3 configured as ROOT
Feb 11 05:38:42 cdbap101 vmunix: Logical volume 64, 0x2 configured as SWAP
Feb 11 05:38:42 cdbap101 vmunix: WARNING: Logical volume for Dump expected but not found.
Feb 11 05:38:42 cdbap101 vmunix: Swap device table: (start & size given in 512-byte blocks)
Feb 11 05:38:42 cdbap101 vmunix: entry 0 - major is 64, minor is 0x2; start = 0, size = 33554432
Feb 11 05:38:42 cdbap101 vmunix: Dump device table: (start & size given in 1-Kbyte blocks)
Feb 11 05:38:42 cdbap101 vmunix: entry 0000000000000000 - major is 31, minor is 0x1000; start = 1563508, size = 16777
212


Thanks in Advance!!


Sridhar
4 REPLIES 4
Torsten.
Acclaimed Contributor

Re: regarding dump

To check the settings run

# lvlnboot -v

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Sridhar R
Regular Advisor

Re: regarding dump

Hi,

Kindly find the output of lvlnboot, it shows fine! But why am i getting that messages in syslog.log??


cdbap101#lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t1d0s2 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c0t0d0s2 (0/1/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Root: lvol3 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Swap: lvol2 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Dump: lvol2 on: /dev/dsk/c0t1d0s2, 0
Ramesh S
Esteemed Contributor
Solution

Re: regarding dump

Hi

In this instance, running the following command on the volume group in question
corrected the errors:

lvlnboot -R /dev/vg00

Rebooting the system shows the error is no longer occurring in /var/adm/syslog/syslog.log.


Thanks & Regards

Ramesh
Sridhar R
Regular Advisor

Re: regarding dump

Excellent Ramesh! It got resolved.