My original question (abbreviated) was:
I am in the process of upgrading a workstation from v4.0E PK#4 to v4.0F.
Everything went fine until the end. I got:
86 of 86 subset(s) installed successfully.
/updmnt/isl/upeng: /var/adm/patch/event.log: cannot create
and the upgrade stops. This happened because /var/adm/patch/ was a
symbolic to an nfs mounted file system, my dumb mistake.
I asked if there was a way I could continue the upgrade successfully.
Indeed, I waited for an installupdate of a similar machine to complete
and the checked the logs to see what I might have to do. Based on this
I fixed /etc/sysconfigtab to the new version, did doconfig and got a
working kernel. The machine still thought that the 4.0E patches were
installed, but this was fixed by removing the relevant OSFPAT* files
from /usr/.smdb.
Dr. Tom Blinn suggested that I might have been able to just re-run
installupdate. Alternatively, I could have looked at the updeng script
from the isl directory in the update kit. figured out where it stopped,
fix the error and continue from there, then continue the rest of the
installupdate script manually. Unfortunately I was not in the state of
mind necessary for all this analysis. Tom later reassured me that what
I had done was probably all right and that the listed 4.0E patches
weren't really still installed. Based on his suggestions, I did some
checks to confirm that this was the case.
So I have a working system (patched meanwhile), everything looks good
and until something goes wrong, I'll assume that it's all right. I do
not recommend this method.
Regards,
Peter Stern
Received on Mon Dec 11 2000 - 15:25:32 NZDT