On Tue, Mar 17, 2009 at 03:51:25PM -0700, Neal Pollack wrote: > >Step 3, you'll be presented with the disks to be selected as in > >previous releases. So, for example, to select the boot disks on the > >Thumper, > >select both of them: > > > >[x] c5t0d0 > >[x] c4t0d0 > > Why have the controller numbers/mappings changed between Solaris 10 > and Solaris Nevada? I just installed Solaris Nevada 110 to see what > it would do. Thank you, and I now understand that to find the disk > name, like above c5t0d0 for physical slot 0 on X4500, I can use > "cfgadm | grep sata3/0"
> I also now understand that in the installer screens, I can select 2 > disks and they > will become a mirrored root zpool. > > What I do not understand, is that on Solaris Nevada 110, the x4500 > Thumper physical > disk slots 0 and 1 are labeled as controller 3 and not controller 5. > For example; > > # cfgadm | grep sata3/0 > sata3/0::dsk/c3t0d0 disk connected configured ok > # cfgadm | grep sata3/4 > sata3/4::dsk/c3t4d0 disk connected configured ok > # uname -a > SunOS zcube-1 5.11 snv_110 i86pc i386 i86pc The numberings are not pre-set, and probably have nothing to do with Solaris 10 vs Nevada (or ZFS). Controller numberings are sequential as they are discovered by the OS. So different probe order, post-boot hardware installations, or when drivers get installed can case the number assigned to be different on different machines. > Of course, that means I shold stay away from all the X4500 and ZFS docs if > I run Solaris Nevada on an X4500? Why would that be? It doesn't claim that there will be a particular mapping for a particular X4500. > Any ideas why the mapping is not matching s10 or the docs? As far as I read, the docs are giving you an example. They're not declaring that yours will be the same. -- Darren _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
