Hi Michael, my guess is that you have installed from IPS repo which doesn't contain Sparc bits (likely from 'release' IPS repo instead of 'dev' one) - in order to verify, could you please attach full /tmp/install_log and /tmp/ai_combined_manifest.xml files ?
Thank you, Jan Michael Barrett wrote: > I just got my console message: > > Automated Installation failed > Please refer to /tmp/install_log file for details > > opensolaris svc.startd[7]: application/auto-installer:default failed > fatally: transitioned to maintenance (see 'svcs -xv' for details) > > In looking at the install_log I see the failures are all related to > each other and the bootblk: > > > 0.) devfsadm fails to find the device namespace: > > current task:get_rootdev_list > current task:setup_dev_namespace > devfsadm command output: devfsadm: could not find major number for > driver ipnet > mber for driver ipnet devfsadm command output: devfsadm: could not > find major nu--More--(65%) > > 1.) then the bootloader failed: > > ict_installboot Command /usr/bin/env -i PATH=/usr/bin > /usr/sbin/installboot -F zfs /a/platform/sun4v/lib/fs/zfs/bootblk > /dev/rdsk/c7t0d0s0 failed with 256 > installboot failed > ICT - Failed to install the bootloader > > > 2.) the updating the archive fails > > shell cmd (bootadm update-archive -R /a 2>&1) returned status 256 > Updating boot archive fails. exit status=256 command=bootadm > update-archive -R /a 2>&1 > Failure. Returning: ICT_UPDATE_ARCHIVE_FAILED > > > 3.) Lastly the copy of the bootlst fails > > current task:copy_sparc_bootlst > Unexpected error when copying the sparc bootlst file /rpool/boot/menu.lst > Traceback (most recent call last): > File "./ict.py", line 1677, in copy_sparc_bootlst > shutil.copyfile(bootlst_src, bootlst_dst) > File "/usr/lib/python2.4/shutil.py", line 47, in copyfile > fsrc = open(src, 'rb') > IOError: [Errno 2] No such file or directory: '/a/platform/sun4v/bootlst' > > Failure. Returning: ICT_COPY_SPARC_BOOTLST_FAILED > > > But it continues to get the rpool ready and no I have nothing in /a? > But I'm still booted off the ramdisk. > > Mike > > > > Sean McGrath wrote: >> Michael Barrett stated: >>> ahhhh...nice. I see >>> >>> <skipped-to-keep-it-sort> >>> Download: SUNWural ... Done >>> Download: SUNWxdg-user-dirs-gtk ... Done >>> Download: SUNWlang-fr ... Done >>> Download: SUNWthunderbirdl10n-extra ... Done >>> Install Phase ... Done >>> Reading Existing Index ... Done >>> >>> Looking at the services I see: >>> >>> # svcs -a | grep install >>> legacy_run 7:59:06 lrc:/etc/rc2_d/S72autoinstall >>> offline* 7:59:03 svc:/application/auto-installer:default >>> >>> Seems to be done or trying to transistion the service to off? What >>> happens next? >> >> its 'offline' since the start method is still running, i.e. its >> installing :) >> (I think) >> >> When its finished you'll get a message on the console saying its ready >> to reboot. It'll then wait for you to reboot it. >> >> ptree and you'll see the pkg process running too. >> >> Sean. >> . >>> Thanks, >>> Mike >>> >>> >>> Sean McGrath wrote: >>>> Login as root with passwd == opensolaris >>>> >>>> then try this: >>>> tail -f /var/svc/log/application-auto-installer:default.log >>>> >>>> you should then see packages etc being installed. >>>> >>>> This lack of verbosity is fixed in later versions of AI. >>>> >>>> Sean. >>>> . >>>> Michael Barrett stated: >>>> < I'm trying to install build 111 on a T5240. Note this box seems >>>> to have 14 drives with bad labels on them. I don't know if that is >>>> related, but is does make reading the console difficult...with all >>>> the scrolling "bad label" errors. >>>> < < AI install gets pretty far (I think). It boots off the >>>> miniroot, downloads it's starter pkgs and files from >>>> pkg.opensolaris.org, etc. Then it gets around to this part: >>>> < < Service discovery over multicast DNS failed >>>> < Service located at <ai-server>:46501 will be used >>>> < Service discovery finished successfully >>>> < Process of obtaining configuration manifest initiated >>>> < Configuration manifest obtained >>>> < Automated Installation started >>>> < The progress of the Automated Installation can be followed by >>>> viewing the logfile at /tmp/install_log >>>> < < Then nothing seems to happen. I wait around 2 minutes and then >>>> hit return and I get a login prompt. When I login, it's still >>>> booted of the miniroot with /a mounted. >>>> < < No real errors in the install_log in /tmp: >>>> < < Bottom part of the install_log: >>>> < < <AI Apr 9 14:59:45> list of packages to be installed is: >>>> < <AI Apr 9 14:59:45> SUNWcsd >>>> < <AI Apr 9 14:59:45> SUNWcs >>>> < <AI Apr 9 14:59:45> babel_install >>>> < <AI Apr 9 14:59:45> entire >>>> < <AI Apr 9 14:59:45> list of packages to be removed is: >>>> < <AI Apr 9 14:59:45> babel_install >>>> < <AI Apr 9 14:59:45> slim_install >>>> < <OM Apr 9 14:59:46> Set zfs root pool device >>>> < <OM Apr 9 14:59:46> creating zpool >>>> < <OM Apr 9 14:59:47> /usr/sbin/zfs get -Hp -o value available rpool >>>> < <OM Apr 9 14:59:47> Creating swap and dump on ZFS volumes >>>> < <OM Apr 9 14:59:58> TI process completed successfully >>>> < <OM Apr 9 14:59:58> Transfer process initiated >>>> < <OM Apr 9 14:59:58> IPS transfer mechanism selected >>>> < <OM Apr 9 14:59:58> IPS transfer phase initiated >>>> < <OM Apr 9 15:00:45> IPS initialization phase 1 succeeded >>>> < < I've never seen an AI install before, so I'm not sure what is >>>> suppose to happen next? >>>> < < Thanks >>>> < -- < This message posted from opensolaris.org >>>> < _______________________________________________ >>>> < caiman-discuss mailing list >>>> < caiman-discuss at opensolaris.org >>>> < http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>> >> > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
