Sankar: You can try that and see whether this resolves your issues.
When s10u6 ships, 121431-25 will be updated again to a later revs. Sankar Chanda wrote: > Hello Mary, > > Is this the one you are referring to? > > http://sunsolve.sun.com/search/document.do?assetkey=1-21-121431-25-1 > > Thanks, > Sankar. > > Sankar Chanda > > 1900 South Norfolk Street, Suite #320 > San Mateo, CA, USA, 94403 > Tel: +1 (650) 522-9922 > Fax: +1 (650) 522-9929 > > www.telesys.com > > ATTENTION: Confidential - Need to Know Basis Only: This message and any > attachments contain information that is confidential and proprietary to > teleSys Software, Inc. No part of this information may be disclosed, used, > copied, or transmitted in any form or by any means without prior written > permission from teleSys Software, Inc. If you received this message in error, > please contact Sankar Chanda by email or collect and destroy this message and > all attachments. > > > > mary ding wrote: >> Sankar: >> >> This is a known live upgrade flash issue in s10u5. This had been >> fixed in s10u6. >> >> YOu should apply the latest live upgrade patches to the T5240 and then >> retrieve the flash archive again and see whether it works. >> >> >> Sankar Chanda wrote: >>> We are having some issues with Live Upgrade procedures on SUN >>> Enterprise T5240 servers. >>> We have successfully performed those procedures earlier on SUN Fire >>> v240 using Solaris 10 Update 3. However, it seems like not working on >>> Solaris 10 update 5. >>> >>> >>> >>> Here is the problem statement: >>> >>> *********************************************************************************************** >>> >>> >>> >>> 1. Created a Flar image successfully >>> 2. Installed on a T5240 machine from InstallServer and using >>> jumpstart profile using a sysidcfg and flash_prof >>> 3. The first installation is successful and system picks up >>> configuration information from sysidcfg file on the install server. >>> 4. Now we use lucreate to create another BE (Boot Environment) BE_2. >>> 5. BE_2 is upgraded with luupgrade using the same flar as used in >>> step 2. >>> 6. Issuing command: >>> luactivate -s BE_2 >>> 7. After a init 6, system tries to boot from BE_2. This time instead >>> of copying system files from BE_1 due to -s options specified, it >>> instead runs the sysconfig command that asks for all the >>> configuration options again. >>> 8. When we were using these steps in Solaris 10 update 3, everything >>> was working fine. The system config was available in BE_2 without >>> any issue. >>> *********************************************************************************************** >>> >>> >>> -- >>> This message posted from opensolaris.org >>> _______________________________________________ >>> install-discuss mailing list >>> install-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/install-discuss >> >>
