Hi > Apparently, this doesn't happen when upgrading an alternate > boot environment with "pkg -R /altroot ..." or when switching > between boot environments with "beadm activate ...". Should it?
What live upgrade does is that during luactivate it creates a boot-archive on /altroot.. So two things need to happen: 1. Update beadm to create a boot-archive on /altroot during beadm activate (don't know if beadm already does this 2. for the pkg -R /altroot usage, one way is to leave /altroot mounted while rebooting. bootadm will update boot-archives on all mounted filesystems during reboot. However the right fix probably is for the "pkg" command to recreate the boot-archive after any -R /altroot updates. Vikram ----- Original Message ---- From: Jürgen Keil <[EMAIL PROTECTED]> To: [email protected] Sent: Wednesday, August 6, 2008 4:47:47 AM Subject: Re: [indiana-discuss] Install opensolaris snv_91 instead of snv_93? Rob wrote: > On Mon, Aug 4, 2008 at 11:25 PM, sanjay nadkarni (Laptop) > <[EMAIL PROTECTED]> wrote: > > Rob wrote: > >>> > >>> Hello! thanks for the reply :) > >>> The inclusion of the new meta package "entire" > >>> definiately makes the process easier, but i'm still > >>> not able to boot into the newly created BE. Here are > >>> my steps: > >>> > >>> # pkg refresh > >>> # pkg install [EMAIL PROTECTED] > >>> # pkg install [EMAIL PROTECTED] > >>> # beadm create opensolaris-1 > >>> # beadm mount opensolaris-1 /mnt/91 > >>> # pkg -R /mnt/91 install pkg:/[EMAIL PROTECTED] > >>> # /mnt/91/boot/solaris/bin/update_grub -R /mnt/91 > >>> # beadm unmount opensolaris-1 > >>> # beadm activate opensolaris-1 > >>> # reboot > >>> > >>> when grub loads, there are three entries in the grub > >>> menu: snv_86, opensolaris-1 (the default), and snv_91 > >>> (2008.11) > >>> > >>> When opensolaris-1 loads, i get this error message: > >>> > >>> > >>> Krtld: bind_primary(): no relocation information > >>> found for module /platform/i86pc/kernel/amd64/unix > >>> Krtld: error during inital load/link phase > >>> > >>> Krtld could not locate nor resolve symbols for: > >>> /platform/i36pc/kernel/amd64/unix > >>> In the boot archive. > >>> > >>> > >>> not sure how to troubleshoot from here? any ideas? > >>> > >> > >> Does anyone have any advice on how to troubleshoot this problem further? > >> I'm not sure why the updated system refuses to boot... > >> > > > > If it's happening this early, it is possible that your root_archive is > > corrupted. If you could boot off the other BE you could try and update the > > root_archive. To do this mount (beadm mount) opensolaris-1 and then run > > /sbin/bootadm update-archive -R <mount point> and see if that helps. > > > > that fixed it! I'm now booting into snv_91 Hmm, so why isn't the boot archive updated automatically? During normal use, quite a few commands (reboot, halt, poweroff, init) make sure that fresh boot archives are built, whenever any of the kernel bits or critical files in /etc or /boot/solaris have changed. Apparently, this doesn't happen when upgrading an alternate boot environment with "pkg -R /altroot ..." or when switching between boot environments with "beadm activate ...". Should it? -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
