11.31 update-ux preview fails for VxVM

[bpsmith7]

My server has 11.31.0809 BOE and I'm running update-ux preview for 11.31.1003 BOE. I'm getting this error:

* Running "/var/adm/sw/pre_update/VXVM-VXFS.100".
ERROR: You must select both Base-VxVM-50 and Base-VxTools-50 bundles for the
upgrade to proceed.
ERROR: The script "/var/adm/sw/pre_update/VXVM-VXFS.100" returned a value of "1" (ERROR)
* Running "/var/adm/sw/pre_update/VXVM-VXFS.100". failed with 2 errors.
* Running "/var/adm/sw/pre_update/VirtualPartition.100".
* The script "/var/adm/sw/pre_update/VirtualPartition.100" returned a value of "0" (SUCCESS).
* Running any scripts found in directory "/var/adm/sw/pre_update". failed with 2 errors.

My products:
# swlist|grep -i vx
Base-VXFS B.11.31 Base VxFS File System 4.1 Bundle for HP-UX
Base-VXVM B.4.10.032 Base VERITAS Volume Manager Bundle 4.1 for HP-UX

We don't use VxVM (may have been installed by a prior admin), just LVM and OnlineJFS. How do I get around this error?

Thanks.

[chris huys_4]

Hi,

Log a call with HP support.

Greetz,
Chris

[Srimalik]

please run update-ux as:
update-ux -s Base-VxVM-50 and Base-VxTools-50

-Sri

[Steven E. Protter]

Shalom,

Sadly this update fails a lot.

You are better off with a cold install of 11.31.

If you must update-ux remove all the vxvm software with swremove, boot your system and then try again with update-ux.

Expect other issues to pop up and make this frustrating.

cold install is the way to go.

SEP

[Srimalik]

SEP,

this particular failure is due to missing selections ( Base-VxVM-50 and Base-VxTools-50 ).

[bpsmith7]

Thanks all, points assigned. I think I'll go with Srimalik's option, as I don't want to go through a cold install. Very odd there isn't built-in error handling for what I would call a "simple" update from late 2008 to early 2010 WITHIN the same OE type...or at least an easy way out. My early '08 FOE update was easy to this same March 2010 BOE.

Anyway, I'll post the results after I finish. I respect all of the answers--have been reading you folks for close to a decade.

[chris huys_4]

> Very odd there isn't built-in error handling
> for what I would call a "simple" update from
> late 2008 to early 2010 WITHIN the same OE
> type.

Maybe it isnt that easy a "update" as one might think, if im not mistaken, with the sept 2009 release of 11.31, vxvm 5.0, became the default vxvm version, while earlier versions of the 11.31 release still came with vxvm 4.1, as the default release, so what you are doing is an effective vxvm upgrade.

And there is something else also, these are OS dvd's, patching dvd's is not possible, so what is normally done, is swcopying the contents of the OS dvds to a separate directory and then, giving the customer a updated in this case VxVM-VXFS.100 script, which should then replace the existing VxVM-VXFS.100 script, so that the update-ux can work.

Thats, why I advised to log a HP support call.

Greetz,
Chris