Hi Sean, unfortunately, it is not possible to rely on drive c#t#d# device name, since it might change across builds. It is known issue and we will need to find out the set of attributes which might be used for reliable identification of target disk for AI installation - please see also bug 5451 for details.
Thank you, Jan Sean McGrath wrote: > We've found that on any box (x86 for now) we network install opensolaris > on (osol 2008.11) its boot disk is named different to that from s10updates > and Nevada. > > For example, a Ultra-20 goes from c0t0d0 to c4t0d0 and a x4500 (thumper) > from c3t0d0 to c6t0d0. > - makes life difficult in our lab for automation since its now unknown > what the boot disk will be named as. > > Anyone seen this ?
