It seems to be my day for pkg problems.

I'm trying to image-update my SPARC system from build #123 to #124.
I get the following:

ri...@sunk:~$ pkg authority
PUBLISHER                             TYPE     STATUS   URI
opensolaris.org (preferred) origin online http://ipkg.sfbay/dev/

ri...@sunk:~$ pfexec pkg image-update
DOWNLOAD                                  PKGS       FILES    XFER (MB)
Completed                              1518/1518 53088/53088 1115.4/1115.4

Segmentation Fault (core dumped)

ri...@sunk:~$ pkg version
77e92d348aaf

ri...@sunk:~$ pfexec file core
core:           ELF 32-bit MSB core file SPARC Version 1, from 'beadm'

I also tried a simple:

ri...@sunk:~$ pfexec beadm create bug-6186
Segmentation Fault (core dumped)

From the release notes, this appears to be:

11221 beadm create core dumps on OpenSolaris 122 SPARC
http://defect.opensolaris.org/bz/show_bug.cgi?id=11221

   When using builds 122 or 123, an attempt to create a new boot
   environment (BE) via beadm(1M) or indirectly through "pkg
   image-update" may result in a "segmentation fault".

   Work-around: Boot into an earlier boot environment and then
   manually create the desired BE from there.  For example, to
   image-update from build 122 or 123 the following set of
   commands can be used

       <reboot into the earlier BE>
       u...@host$ pfexec beadm create -e <name of build 122 BE> \
           <name of new BE>
       u...@host$ pfexec beadm mount <name of new BE> /mnt
       u...@host$ pfexec pkg -R /mnt image-update
       u...@host$ pfexec beadm unmount <name of new BE>
       u...@host$ pfexec beadm activate <name of new BE>

   At this point, the new BE can be booted into.

The problem is I don't have any earlier boot environments I can boot into:

ri...@sunk:~$ beadm list
BE Active Mountpoint Space Policy Created -- ------ ---------- ----- ------ ------- bug-6186 - /tmp/.be.F9aiMf 86.0K static 2009-10-05 07:31
opensolaris   NR     /               15.95G static 2009-09-16 09:44
opensolaris-1 -      /tmp/.be.MoaWrg 87.0K  static 2009-10-06 07:44


Anything I can do with my existing machine to fix/workaround this or
do I have to reinstall everything again?

Thanks.


_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to