bundle aborted at install phase

[Roy Phelps_1]

Basically I'm trying to figure out the swinstall process.
What are it's steps and what do I do when it fails. Please answer questions 1-3 and a
summary question 4 based on the 'GIVEN:' below.
My questions are:

1)When swinstall aborted at the install phase
what steps were left to complete?

2)If I fix the corrupt patches, configure the
unconfigured ones, and configure the
installed ones like the check_patches output
says to do, what else do I need to do to
complete the process?
2a)Reboot? 2b)Rebuild kernel?

3)OR, do I just do another swinstall with
the same parameters but this time with a
valid bundle? With different parameters?

4) I know what happened to a point. I know
what all the log files say. I need to know
what was supposed to happen and what needs to
happen now, specifically.

#bundle aborted at install phase

GIVEN:
HP-UX 11.23 on Itanium rx5670 box.
used swinstall to install patches
#swinstall -x autoreboot=true -x patch_match_target=true -s /cdrom/...

install of patchset August 2004 11i v2(B.11.23.0408) was successful.

Install of September 2004 patchset (B.11.23.0409) ended with:

4 files had errors..1 fileset had errors...
The files were not loaded because they were missing from the media.
(cd was probably created with the last files cut off)
PHSS_31840 failed install.
"The Install Phase has suspended. Check above..."
"Aborting the Install Phase"

check_patches reveals:

ERROR:
~
The following patch filesets are in the corrupt state:
PHSS_31840.AUDIO-RUN
PHSS_31840.AUDIO-SHLIBS
PHSS_31840.AUDIO-SRV
Run swverify to find cause and how to correct.
~
WARNING:
One or more active patch filesets are in the installed state,
but they include a configure script....Use swconfig...
~large list~
~
NOTE:
One or more patch filesets are in the installed state, but
they do NOT include a configure script.
~long list~
Configure using swconfig.

[Steven E. Protter]

I would do this:

swverify \*

Take a look if any of the problem patches are in the problem list.

I would try to install them individually or as a smallter group.

swinstall -x autoreboot=true -x reinstall=true -s /depot_path \*

Must read the patch notes prior to reinstalling because you never know when reinstall on a patch is damaging.

PHKL_18543 comes to mind.

SEP

[Roy Phelps_1]

SEP,

Just for kicks, would you please answer
my questions. And then throw in what you
think or a better way for me to look at this.

Thank you very much,
Roy

[Patrick Wallek]

Roy,

It's going to be darned near IMPOSSIBLE to give you an exact answer here.

1) It depends greatly on what patches were in the bundle, what patches were selected to be installed, how many patches had already been installed and how many are left to be installed.

2) See #1 -- It depends on where it was in the process.

3) You can certainly try installing again with the default parameters and see what it selects for install. I would NOT use any reinstall options though.

4) See #1

I know you're probably not going to like my answers as they're not specific enough for you, but without having your machine and that specific patch bundle in front of me, it's very difficult.

[Roy Phelps_1]

Patrick,
Thank you first of all.
Now, The patch bundle (Sept. 04)
was cut off at the end of the file.
4 files in 1 fileset was corrupt.
All the other patches in the bundle
were installed and then the install phase
aborted. The check_patches output says
what to do. I would like to confirm the
process.
-Roy