Hi Ceri,
Ceri Davies wrote: > I did this and specified the boot disk as c5t4d0, which is what it > currently is. > > The install fails saying it cant find c5t4d0, and a format shows all > the controller numbers are different in the miniroot, so there is not > c0/c5 etc. How is this resolved? This is a known problem. You could workaround this issue by * using default manifest (without disk criteria specified), * using different criteria currently implemented (vendor, size, ...) * booting AI in order to determine the correct ctd disk name. The issue is that ctd disk names can change across builds or different environments - please see following bug for more details: 5451 No way to permanently target specific disk in AI engine manifest http://defect.opensolaris.org/bz/show_bug.cgi?id=5451 To address this problem, additional disk attributes are considered to be supported in AI manifest - at least: * device id (where id is from: iostat -iEn), requires fix for 6550682 * volume name (8 character volume name set by format) * device path (device path under /devices) * 'boot disk' Thank you, Jan > > Mr. Ceri Davies - Staff Engineer (Software) > Sun Microsystems - Data Management Group > Ceri.Davies at Sun.com <mailto:Ceri.Davies at Sun.com> > W:(303) 272-7810 (x77810) > H:(303) 442-2795 > Typically work from home on Fridays > > > > > On Jun 18, 2009, at 10:40 AM, Sundar Yamunachari wrote: > >> Ceri Davies wrote: >>> How do I specify the boot disk to the ai server and retry the install? >> You can add a target disk in the AI manifest. Check the AI document >> at http://dlc.sun.com/osol/docs/content/dev/AIinstall/customai.html. >> If you are going to use the manifest for one system, you can change >> the default manifest. Otherwise you can add it as a custom manifest. >> >> - Sundar >>> >>> The boot disk is c5t4d0 >>> c0t0d0 and c1tod0 are not in use, so its probably one of them... >>> >>> However guess what... On a thumper you can't boot either of these >>> >>>> Hmm, looks like it did install but the console was redirected to >>>> the VGA. >>>> I logged in and rebooted without looking around. However I >>>> rebooted to the old kernel... >>>> >>>> So... It looks like it chose one of the other 48 disks to install >>>> on and the boot system is still using the old disk! >>>> Of course having lost the console, I have no idea what it did. >>> >>> . How do I specify the boot disk? to the ai server and retry this? >>> >>>>> I deleted the old macro and re-did the other macros, >>>>> and its is somewhat better. I see the OpenSolaris banner and this >>>>> this on the screen: >>>>> " >>>>> Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved. >>>>> >>>>> Use is subject to license terms. >>>>> " >>>>> >>>>> I'm going to the lab to check the console... >>>>> >>>>> >>>>> Mr. Ceri Davies - Staff Engineer (Software) >>>>> Sun Microsystems - Data Management Group >>>>> Ceri.Davies at Sun.com <mailto:Ceri.Davies at Sun.com> >>>>> W:(303) 272-7810 (x77810) >>>>> Typically work from home on Fridays >>>>> >>>>> On Jun 17, 2009, at 6:32 PM, Sundar Yamunachari wrote: >>>>> >>>>>> Ceri, >>>>>> >>>>>> I couldn't find anything wrong with your install server or >>>>>> dhcp server. Can you run a snoop on the install server to capture >>>>>> the client traffic while the client is booting? >>>>>> >>>>>> Thanks, >>>>>> Sundar >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> >> > > > ------------------------------------------------------------------------ > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
