From: Joseph Tam (tam@math.ubc.ca)
Date: Tue Nov 08 2005 - 21:03:02 EST
I was going to just send the problem part, but I found a solution to my
problem so this might benefit someone else.
It used to be with Solaris <10 you could unpack the latest *_Recommended.zip
and go for coffee while the machine patched its brains out, then
reboot. Nowadays, I can never get through Solaris 10 patch cluster install
without some sort of hiccup.
The latest one occured after I installed the latest Solaris 10 patch cluster
(Oct/24/05) on a nearly fresh Solaris 10 install (sub-core Sun280R), and
after the reboot, the USB keyboard didn't work. The problem turned out to
be that some driver files in patch 118822-20 didn't get installed.
In fact, for patches that updates more than one package, the first applicable
package got installed, but the rest were skipped. Furthermore, patchadd
issued a return code 45, which I guess corresponds to this error message:
Patch <patch-id> failed to be copied to the psool directory.
This difficulty is compounded by the fact you can't reapply the patch with
patchadd (-u doesn't work) since it thinks the patch has already been applied.
The only way that I could find to get the machine back to a consistent
patched state was to manually add back all the missing patch packages,
a long and tedious chore:
for each patch
for each package installed that did not get updated (check patchadd -p)
pkgadd -d /location/of/<patch-id-dir> <packagename>
After reinstalling a fresh OS and playing around with the patching process, it
seems that the -nosave option (do not save updated files so that you can
back out of a patch), which corresponds to adding the '-d' flag to patchadd
command was the culprit. Patching went normally if you left this option out.
*** Late breaking result: workaround ***
After some more digging, it appears that this problem is fixed in, you guessed
it, a patch: 119254-09 (or some previous version). However, this patch will
suffer from the same problem as above, and you get into a catch-22 where
you need to fix the problem before this patch will work (since the SUNWswmt
package gets skipped over). So, use the above manual method to break
the recursive problem:
# This will update SUNWpkgcmdsu but not SUNWswmt
patchadd -d /location/of/patch/119254-09
# Finish installation ...
pkgadd -d /location/of/patch/119254-09 SUNWswmt
The real fix is for Sun to release 119254-10 that will recognize this
situation and install the correct SUNWswmt.
Joseph Tam <tam@math.ubc.ca>
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:35:23 EDT