Thank you Mary. That was my problem. Sorry I missed/forgot the flag day notice.
Thanks, Tyson mary ding wrote: > Tyson: > > Ethan Quach send out a flag date message about using AI in osol_132. > You will need to use installadm create-service -b "install=true" or > installadm create-client -b "install=true" > > > > If you don't use the automated installer on x86 systems, ignore > this message. With the fixes for the following bugs: > > changeset: 707:2274294287c2 > tag: tip > user: Ethan Quach <Ethan.Quach at sun.com> > date: Wed Jan 27 16:15:59 2010 -0800 > summary: > 14082 bootarg for booting automated installs over the network > 13766 AI debug mode can only be activated in conjunction with > service discovery > 4069 The create-service setup doesn't work if a client is > booted using a tip line > > > In build 132, the default behavior of booting x86 systems over the > network into AI images has changed. The default grub menu entry > will no longer start a hands-free automated install. The second entry > must be selected to kick off the hands-free install. The first entry > will > boot into the AI boot image and present console-login, but automated > installation will not start. > > The following table gives the information on what the changes for this > flag day would be and how it impacts your AI server. > > > AI server bld AI image bld Required action > --------------------- ---------------------- > ---------------------------- > pre 132 pre 132 No change. > > > pre 132 132 or later Clients booting this image will not > automatically boot > into a hands- > free automated > install. The work- > around is manual. > You must hand > edit the menu.lst > file associated with > the service and add > a "install=true" > property to the -B > args. If you do > specific > 'create-client' commands for > your x86 clients, > you can instead just > use the -b option to > explicitly add the > "install=true" flag > into its menu. Or > add it to the menu > entry manually at > boot time. > > installadm create-client ... > -b install=true ... > > > 132 or later pre 132 No change. > > > 132 or later 132 or later Clients booting this image will not > automatically boot > into a hands- > free automated > install. This is the > desired new changed > behavior. The > second grub menu > option must be > chosen to kick off > the hands-free > install. > Alternatively, you can use the > -b option with > 'create-service' or > 'create-client' to > explicitly add the > "install=true" flag > into the menu, > which will cause the > default entry to > do a hands-free install. > > installadm create-service ... > -b install=true ... > installadm create-client ... > -b install=true ... > > > Thanks, > -ethan > > Tyson Ainsworth wrote: >> I am having an issue getting b132 to install with AI. While >> attempting the install my client loads the b132 mini-root but then >> bombs out saying: >> >> Auto-installer disabled. Enable the auto-installer service >> by running the following command: >> svcadm enable svc:/application/auto-installer:default >> >> When trying to enable it the auto-installer services I get: >> >> # svcadm enable auto-installer >> Couldn't find manifest file at </tmp/ai_combined_manifest.xml> >> Feb 5 04:14:12 opensolaris svc.startd[7]: >> application/auto-installer:default failed fatally: transitioned to >> maintenance (see 'svcs -xv' for details) >> >> >> For my setup I the AI server is not the same as the DHCP/PXE server. >> So I copy from the AI server's /tftpboot directory the >> I86PC.OpenSolaris-2 directory to the PXE servers /tftpboot >> directory. Is there something else that needs to be copied over? >> This has worked successfully for me up until now. Any help would >> greatly be appreciated. >> >> Thanks, >> Tyson >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
