On January 9, 2010 11:27:37 AM -0500 Frank Cusack <fcusack at fcusack.com> wrote: > <ICT Jan 9 07:39:05> current task:bootadm_update_menu > <ICT Jan 9 07:39:05> update GRUB boot menu on device /dev/rdsk/c2t0d0s0 > <ICT Jan 9 07:39:06> bootadm_update_menu output: bootadm: cannot get > (hd?,?,?) for menu. menu not on bootdisk: /dev/rdsk/c2t0d0s0 > > This is an X4275, I booted from a usb stick and am installing to the > onboard CF card (which is a USB adapter). When it boots it goes > into the grub command line, since there is no menu.lst file. > > A simple 'findroot (pool_rpool,0,a)' as found on my other systems isn't > working. > > The system installs and boots fine from solaris 10 or opensolaris 2009.06. > Now to reinstall another OS, find the grub magic and try b130 again. :(
Got it installed using the b130 "normal" (universal) live usb. Much faster that way anyway, as all the bits are on the usb so the little bit of hassle to click through the installer is worth it (and there's no documented way to install less than a full system with AI). I get the same error as above when using the universal usb. On both systems, at the end I get a report that all the ICTs finished correctly, which in the AI case is obviously wrong. It is interesting that for the AI there were 25 Python ICTs and for universal there were 30 Python ICTs. The installed menu.lst does have the line findroot (pool_rpool,0,a) so I'm not sure why I couldn't do this at the interactive grub prompt. For the universal USB, I was able to verify that menu.lst was installed before I rebooted. I wish I had the time to try the AI again to see what's going on before reboot. I just can't let the thing sit for 6 hours while it downloads the bits again for install. -frank