Here are some error messages I see when I try to boot after installing
VXVM 4.0 on one of the boxes. I am working on one of the submirrors. I
also collapsed the filesystems /var,/opt,/usr into / onto the
submirror that gets installed with 4.0. I am wondering if any VXVM
information is being carried over from the other disk which runs 3.2
when I do the ufsdump.
what could possibly cause the volboot file from not being loaded? I
didnt even get a chance to run vxinstall or vxdiskadm. I get these
errors after I install the 4.0 packages and patches.
vxvm:vxconfigd: V-5-1-7607 vxvm:vxconfigd: WARNING: File
/etc/vx/array.info doesn't exist.
vxvm:vxconfigd: Generating file /etc/vx/array.info.
vxvm:vxconfigd: V-5-1-1589 enable failed: Volboot file not
vxvm:vxconfigd: transactions are disabled.
vxvm:vxconfigd: V-5-1-946 Rootdg cannot be imported during
VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup...
V-5-1-7607 vxvm:vxconfigd: WARNING: File /etc/vx/array.info doesn't
Generating file /etc/vx/array.info.
VxVM vxconfigd ERROR V-5-1-1589 enable failed: Volboot file not loaded
transactions are disabled.
VxVM vxvm-startup2 ERROR V-5-2-3656 Vold is not enabled for
No volumes started
I installed all the packages and then rebooted the box. The other
mirror on this box still have a 3.2 VXVM. I have entered that into
/etc/vx/disks.exclude file. How come its trying to import Rootdg
which is not a mandatory diskgroup any more in 4.0?