Hi If the cluster has 127111 or 127112 ( sparc | x86 KU ), and if 120011-14 is also being installed, then a reboot is required after applying 120011-1 4, otherwise corruption will occur, if the cluster does contain 127111|127113 then get the latest cluster as these have been removed, pending a fix to the patch tools.
Enda Stewart, Tom L. wrote: > Ahh, > > Now it makes sense.... > > The error was ( I had to change the server name to protect the > innocent). > > zoneadm: /zones/xxxxx: No such file or directory > could not verify zonepath /zones/xxxxx because of the above errors. > zoneadm: zone xxxxxx failed to verify > > I didn't even think of that as I did do a shutdown and booted back to > single user. > > Many thanks, > > Tom > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 19, 2007 10:50 AM > To: Stewart, Tom L. > Cc: firstname.lastname@example.org > Subject: Re: [zones-discuss] Question on new Nov patch cluster for a > zoned system. > > Stewart, Tom L. wrote: > >> All, >> >> I have a T2000 with a couple of zones and when I tried to install the >> patch cluster from Nov 07 in the Global zone, it failed. >> >> > > any idea why it failed, are there logs, patchadd output? > it should not have failed > >> According to the CLUSTER_README >> >> WARNING!! IT IS HIGHLY RECOMMENDED that the installation of this patch >> > > >> cluster be performed in single-user mode (Run Level S). >> >> So I shutdown the zones and rebooted to single user mode. The >> install_cluster process took less than a minute and gave errors on >> trying to patch the first zone. >> >> Do I need to run the patch in normal mode or is this some sort of bug? >> >> > if you boot to Single User Mode ( as opposed to dropping to Single User > from Multi User ) then you need to run the filesystem/local:default SMF, > > or mountall -l > As otherwise the zone's zonepath will not be mounted. > > What errors did you see? > Enda > >> Thank you, >> Tom >> _______________________________________________ >> zones-discuss mailing list >> email@example.com >> >> > > > _______________________________________________ > zones-discuss mailing list > firstname.lastname@example.org > _______________________________________________ zones-discuss mailing list email@example.com