Missing LV and VG icons in SAM

[Tim Woods_2]

We have a refurbished N4000 running 11.0 that we just received. I setup a new vg on it's SC10, and when I went to setup the lv's freom my script, it gave me an error and I saw that there was no -D option listed for lvcreate.

I probably made my mistake when I copied lvcreate over from one of our other boxes and setup my lv's. After changing the time zone, I rebooted the box, only to have it come up without my new vg active.

I can activate the vg and mount the lv's and they work fine, but that obviously a problem. In SAM the icons for Volume Groups and Logical Volumes under Disks and File Systems are now missing. They won't show in the pull down menu under List either.

I deleted the newer version of lvcreate that I put on the system and renamed the old verion back and rebooted, but I still get the same results. I'm wondering if anyone has any idea what happened and if there is a way to fix it.

We can operate with it the way it is, since it's a test box, but obviously everything is not right on it.

[John Palmer]

Hi Tim,

Suggest you apply the latest Supportplus patch bundle. The -D option to lvcreate was implemented by a patch a long time ago (> 18 months).

Regards,
John

[Tim Woods_2]

Forgot to mention patches. We have the Hardware Enablement Bundle from Dec 2001, the Quality Pack from Sept 2001, and General Release from June 2001. on the system.

That's why I didn't understand why it wouldn't let me use the -D option. The strange part is, after moving the files back to the way they were, it now shows -D as an option.

[James R. Ferguson]

Hi Tim:

I'm not sure why you copied the object for 'lvcreate' from another server. Perhaps you can describe why?

As for the volume group not activating at bootup, have a look at '/etc/lvmrc'. You can choose to activate all volume groups or you can customize the list. Set AUTO_VG_ACTIVATE=1 to activate all (the usual default for non MC/SG environments).

Regards!

...JRF...

[Helen French]

Hi Tim:

The problem might be because of your file copy (lvcreate). The command versions and the patch release version may not match in all cases, if you just copy the files from one system to another. I would suggest you to install the latest patch bundles and then do a 'cleanup' to remove all old patches from the system. The GRE releases are not available now.

HTH,
Shiju

[John Palmer]

Try running 'what /usr/sbin/lvcreate'. On a September 2001 release, I get:-
$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
$Revision: 82.26.1.9.1.111 $ MIRROR PRODUCT
PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmboot.o pvck.o pvchan
ge.o pvcreate.o pvdisplay.o pvmove.o pvremove.o sdstolvm.o vgchgid.o vgcfgbackup
.o vgcfgrestore.o vgchange.o vgcreate.o vgdisplay.o vgexport.o vgextend.o vgimpo
rt.o vgreduce.o vgremove.o vgscan.o lvchange_m.o lvcreate_m.o lvextend_m.o lvmer
ge_m.o lvmmain_m.o lvreduce_m.o lvsplit_m.o lvsync_m.o nomwcsyncd_m.o vgsync_m.o
hpux_rel_m.o 01/06/25

You also need to be aware of the fact that the 'lvcreate' binary is not only used for lvcreate. If you check its link count:-
-r-sr-xr-x 31 root sys 561152 Apr 24 20:07 lvcreate
it has 31 names and an inode search shows that it's also know as:-
/usr/sbin/lvchange
/usr/sbin/lvcreate
/usr/sbin/lvdisplay
/usr/sbin/lvextend
/usr/sbin/lvlnboot
/usr/sbin/lvreduce
/usr/sbin/lvremove
/usr/sbin/lvrmboot
/usr/sbin/pvchange
/usr/sbin/pvck
/usr/sbin/pvcreate
/usr/sbin/pvdisplay
/usr/sbin/pvmove
/usr/sbin/vgcfgbackup
/usr/sbin/vgcfgrestore
/usr/sbin/vgchange
/usr/sbin/vgcreate
/usr/sbin/vgdisplay
/usr/sbin/vgexport
/usr/sbin/vgextend
/usr/sbin/vgimport
/usr/sbin/vgreduce
/usr/sbin/vgremove
/usr/sbin/vgscan
/usr/sbin/lvmerge
/usr/sbin/lvsplit
/usr/sbin/lvsync
/usr/sbin/vgsync
/usr/sbin/nomwcsyncd
/usr/sbin/pvremove
/usr/sbin/vgchgid

So be very careful when you copy binaries from another system.

Regards,
John

[Tim Woods_2]

James: When I issued the lvcreate command, it gave me an error and when I looked at the arguments, it didn't have -D as an option, so that's when I copied it over.
The AUTO_VG_ACTIVATE is set to 1.

Shiju: I am in the process of downloading the current patches. I'll let you know what happens when I get them on the system and do a cleanup.

John: This what I get when I did a what:

$Revision: 80.6 $ $Date: 97/04/28 18:00:45 $
$Revision: 82.26.1.9.1.61 $ MIRROR PRODUCT
PATCH_11_00: lvdisplay.o lvlnboot.o lvremove.o lvrmboot.o pvck.o pvchange.o pvcreate.o pvdisplay.o pvmove.o pvremove.o sdstolvm.o vgchgid.o vgcfgbackup.o vgcfgrestore.o vgchange.o vgcreate.o vgdisplay.o vgexport.o vgextend.o vgimport.o vgreduce.o vgremove.o vgscan.o lvchange_m.o lvcreate_m.o lvextend_m.o lvmerge_m.o lvmmain_m.o lvreduce_m.o lvsplit_m.o lvsync_m.o nomwcsyncd_m.o vgsync_m.o hpux_rel_m.o 00/01/19

It's a little different, so we'll see what the patches can do for me. I know copying binaries isn't a smart thing to do, but I guess I just proved that I'm not as smart as I think I am. :)

[Tim Woods_2]

I have installed the latest patch bundles, the Quality Pack from March 2002 and the Hardware Enablement from June 2002.

My 'what' on lvcreate now matches John's, but my vg still isn't activated on boot and I still can't see Volume Groups or Logical Volumes in SAM (motif or text). I also noticed that when I look at Disk Devices in SAM, it shows all my disks but it says they are all unused, even the disk with vg00 which the system boots from.

[Tim Woods_2]

After talking with several people on the issue, I determined that the original install was at fault and not my copy. Reinstalled OS and everything is fine.