secondary swap

[moon_5]

Hi all~

during system booting, this message in the syslog...

vmunix: LVM: VG 64 0x010000: Unable to identify the latest copy of configuration and status information. Quorum check failed!

0x010000 is secondary volume group number
and secondary swap volume group is deactivated.

what's the problem??

[T G Manikandan]

can you see 0x010000 when you do a

#ll /dev/*/group

[moon_5]

sure i can see

crw-rw-rw- 1 root sys 64 0x010000 Aug 28 2004 /dev/vgswap/group

[Devender Khatana]

Hi,

You have defined a secondry swap in a volume group other then your vg00. More than half of the no. of disks in your that VG are not accessible to system and that is why your that VG is not getting activated and you secondry swap is not accessible to system. Confirm by bdf to see that all file systems are mounted and through swapinfo wheather all swaps are enabled. File systems belonging to one vg in which this secondry swap is defined should be missing from bdf output and atleat this secondry swap also must be missing from swapinfo output.

Also you must have noticed something like Querying Physical Volumes message while booting.

HTH,
Devender

[T G Manikandan]

Try manually,
#vgchange -a y /dev/vgswap

[moon_5]

I'll do that but before why that kind of problems occured? just a curious thing..

[Devender Khatana]

Hi,
It happens because some of physical volumes in your system are not accessible. just do "#strings /etc/lvmtab" and from the output see the disk device file entered below /dev/vgswap and then try to query those physical volumes using 'diskinfo -v /dev/rdsk/cxtydz'. One of these should give error.

HTH,
Devender

[Henk Geurts]

Moon ,
if there are disk problems with you swapVG also check
/var/opt/resmon/log/event.log* for the latest hardwaremessages.

does an
# ioscan -fnC disk
shows anything other then CLAIMED ?

regards

[moon_5]

when I found this log..I checked disks but all disks are nomal...

[Devender Khatana]

Hi,
Is your vgswap activated then? I think there is no reason other a disk timeout at boot which is causing this to happen. Does this vg is listed in the output from

#strings /etc/lvmtab

I think it is not. If the disks allocated to /dev/vgswap volume group are fine. You can try to activate this vg manually by
#vgchange -a y /dev/vgswap


If should not through any error and display Volume group successfully activated. Otherwise if it through error then you will have to proceed having accout that error.

If your vg gets activated then now you can enable your swap manually and confirm it through

#swapinfo -atm ( Shuld display all swaps configured and one should be something like /dev/vgswap/????)

Let us also know the progress.

HTH,
Devender

[moon_5]

thank you for reply~

it's not a machine problem..--
I changed error disk one month ago then I
didn't do vgcfgrestore command.

anyway thaks again guys...^^