Quote:
Originally Posted by rhfrommn
I've not seen a problem like yours before, but I have one idea you could check out. Were the other systems that worked ok V440 or were they older hardware? I've had a jumpstart problem before where the version of Solaris I was installing wasn't the latest hardware release, so newer systems were screwed up. Either they wouldn't jumpstart or were flaky when they were done. Maybe you have a situation like that where some missing HW support package wasn't causing problems before but now that patch expected it to be there and broke.
A longshot I know, but something you could check.
Yea, after some thought, I was coming up with something similar. Most of the other systems are UltraAX-i2's with a 60 and a couple of Ultra4's thrown in for good measure. These are new systems. I didn't set up the jumpstart for them, but I believe we had to go to a newer version of 8 to support the hardware.
I thought of that and the patch installation directory. We typically install from /tmp or /var/tmp but the patchadd docs do say it's expecting it from /var/sadm/spool/patch and it does act odd sometimes if it's not in /tmp (ownership issues since patchadd is su'ing to nobody to run pkgadd).
Thanks for the reply though.
Carl