giovanni: thanks for the tip about the disks, the text-based install wouldn't boot because of the inodes problem, i didn't realize i could solve that by unplugging some drives. looks to be progressing fine now.
james: i never got 134 to install... the text-based install would boot into maintenance. standard livecd would boot but gui install would fail silently. thanks guys. milosz On Thu, Oct 14, 2010 at 9:23 PM, James C. McPherson <j...@opensolaris.org> wrote: > On 15/10/10 05:54 AM, Giovanni Tirloni wrote: >> >> On Thu, Oct 14, 2010 at 4:05 PM, milosz <mew...@gmail.com >> <mailto:mew...@gmail.com>> wrote: >> >> hi all, >> >> anyone have a workaround for installing 2009.06 to disks attached to >> an mpt_sas controller? the 134 install from genunix crashes every >> time for me. >> >> best thing i can think of is installing to a usb stick, doing an >> image-update and installing mpt_sas, and then zfs attach/detach >> trickery. >> >> >> You can try to rebuild the 2009.06 microroot on the USB image to add the >> mpt_sas driver. There are some articles with instructions on how to do >> that. >> >> With b134 and 24 disks, I have had it break on the install because it >> exhausted the number of inodes for all the disks/partitions on the >> ramdisk. The workaround was to install with fewer disks attached. > > > Giovanni: Sorry, that suggestion is WRONG. > > mpt_sas(7d) is a SCSAv3 hba driver. The changes to enable > SCSAv3 went into build 118, along with mpt_sas(7d). > > You cannot use 2009.06 with an mpt_sas(7d) hba. > You must upgrade to a build following 118. > > Milosz: I am interested in seeing your panic stack from a > build 134 installation. > > > > James C. McPherson > -- > Oracle > http://www.jmcp.homeunix.com/blog > _______________________________________________ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss