> Having some trouble getting an opensolaris install > working on the > following system: > > https://www.acmemicro.com/estore/merchant.ihtml?pid=15 > 69&step=4 > > The motherboard is H8DME-2, a nVidia MCP55 based > board, and we have two > AMD Opteron 2427 (6-core) processors installed with > 48G of memory. The > motherboard is at the latest bios (R 3.5) and details > are: > > http://www.supermicro.com/Aplus/motherboard/Opteron200 > 0/MCP55/h8dme-2.cfm > > Have tried OpenSolaris 2009.10, OpenSolaris-b125 > usb/dvd, as well as > automated install on this system and all have some > issue with > recognizing the harddrives. The AI install says > this: > > > <AI Jun 2 18:40:21> /tmp/ai_combined_manifest.xml is > a valid manifest > <AI Jun 2 18:40:21> Auto reboot disabled > <OM Jun 2 18:46:14> System reports enough physical > memory for > installation, swa > p is optional > <AI Jun 2 18:46:14> Checking any disks for minimum > recommended size of > 12646 MB > <AI Jun 2 18:46:14> Disk c7t0d0 size listed as > 953869 MB > <AI Jun 2 18:46:14> Default disk selected is c7t0d0 > <AI Jun 2 18:46:14> Cannot find the partitions for > disk c7t0d0 on the > target sy > stem > <OM Jun 2 18:46:14> No disk partitions defined prior > to install > <OM Jun 2 18:46:14> No slices defined prior to > install > <AI Jun 2 18:46:14> Disk name selected for > installation is c7t0d0 > <AI Jun 2 18:46:14> no manifest partition > information found > <AI Jun 2 18:46:14> no manifest slice information > found > <OM Jun 3 01:46:15> Timezone setting will be > TZ=US/Pacific > <OM Jun 3 01:46:15> Set timezone > <AI Jun 3 01:46:15> installation will be performed > from > http://pkg.opensolaris. > org/release (opensolaris.org) > <AI Jun 3 01:46:15> installation will be performed > from > http://pkg.opensolaris.org/release (opensolaris.org) > <AI Jun 3 01:46:15> list of packages to be installed > is: > <AI Jun 3 01:46:15> entire > <AI Jun 3 01:46:15> SUNWcsd > <AI Jun 3 01:46:15> SUNWcs > <AI Jun 3 01:46:15> babel_install > <AI Jun 3 01:46:15> list of packages to be removed > is: > <AI Jun 3 01:46:15> babel_install > <AI Jun 3 01:46:15> slim_install > <OM Jun 3 01:46:15> Disk was changed > <OM Jun 3 01:46:15> Disk contains valid Solaris > partition > <OM Jun 3 01:46:15> whole_disk = 1 > <OM Jun 3 01:46:15> diskname set = c7t0d0 > <OM Jun 3 01:46:15> Set fdisk attrs > <TIDM_E Jun 3 01:47:32> fdisk: fdisk -n -B failed. > Couldn't create > Solaris2 partition on whole disk c7t0d0<TIMM_E Jun 3 > 01:47:32> Creating > Solaris2 partition on whole disk <c7t0d0> failed > <OM Jun 3 01:47:32> Could not create fdisk target > <OM Jun 3 01:47:32> TI process failed > <OM Jun 3 01:47:32> Target instantiation failed > exit_val=-1 > <AI Jun 3 01:47:35> om_perform_install failed with > error 208 > <AI Jun 3 01:47:35> Auto install failed > > Other versions/install methods all report problems > accessing the disks. > > Anyone have ideas of what the problem could be, or > where we can start > digging deeper to get the system going? > > > -- > paul > _______________________________________________ > storage-discuss mailing list > storage-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/storage-d > iscuss
Hi Paul, Cross-posting with the install-discuss. Have you tried running the Sun Device Detection Tool? http://www.sun.com/bigadmin/hcl/hcts/device_detect.jsp regards chuck -- This message posted from opensolaris.org
