Danek Duvall wrote:
> Hm. Because the "pkg install entire" line is supposed to prevent
> specifically this. There's no indication in the output you give that you
> ended up installing build 111 packages on your build 86 system, but it
> certainly looks like it. Are you sure that BUILD got set to 86, and that
> you did install entire exactly as specified?
Hi, Danek,
I still have it in my .sh_history:
BUILD=`uname -v | sed -e "s/snv_//" -e "s/[a-z]//"`
pfexec pkg refresh
pfexec pkg install entire at 0.5.11-0.${BUILD}
pfexec pkg install SUNWipkg at 0.5.11-0.${BUILD}
pfexec pkg install SUNWinstall-libs
... varous ping, snoop, netstat and ssh commands ...
pfexec pkg install SUNWinstall-libs
There were some network problems somewhere between my machine and
pkg.opensolaris.org, that's why the first SUNWinstall-libs failed,
and the ping commands, etc. Then I ran (only) the last command
again.
Maybe the install entire or SUNWipkg failed too due to network problems
and I didn't notice. Unfortunately, the output had scrolled away by
the time I hit the install-libs problem.
Well, now that I know how to recover, I feel brave; let me try it
again, maybe this will give you some clues...
$ BUILD=`uname -v | sed -e "s/snv_//" -e "s/[a-z]//"`
$ pfexec pkg refresh
$ pfexec pkg install entire at 0.5.11-0.${BUILD}
Creating Plan - pkg: pkg:/entire at 0.5.11,5.11-0.86:20080504T125439Z already
installed
No updates available for this image.
$ pfexec pkg install SUNWipkg at 0.5.11-0.${BUILD}
Creating Plan \ pkg: pkg:/SUNWipkg at 0.5.11,5.11-0.86:20090512T150104Z already
installed
Creating Plan | pkg: pkg:/SUNWpython-cherrypy at
3.1.0,5.11-0.86:20080905T234838Z already installed
pkg: pkg:/SUNWpython-mako at 0.2.2,5.11-0.86:20090512T150118Z already installed
pkg: pkg:/SUNWpython-ply at 3.1,5.11-0.86:20090512T150119Z already installed
pkg: pkg:/SUNWpython-pyopenssl at 0.7,5.11-0.86:20080905T234839Z already
installed
pkg: pkg:/SUNWpython24-simplejson at 0.5.11,5.11-0.86:20090512T150128Z already
installed
No updates available for this image.
$ pfexec pkg install SUNWinstall-libs
DOWNLOAD PKGS FILES XFER (MB)
Completed 20/20 3556/3556 58.44/58.44
PHASE ACTIONS
Install Phase 1333/6412 Action install failed for
'lib/libc.so.1' (pkg:/SUNWcsl):
OSError: [Errno 16] Device busy
The Boot Environment OS-2008.05 failed to be updated. A snapshot was taken
before the failed attempt and is mounted here /tmp/tmp0U6KBC. Use 'beadm
unmount OS-2008.05_static:-:2009-06-04-20:21:42' and then 'beadm activate
OS-2008.05_static:-:2009-06-04-20:21:42' if you wish to boot to this BE.
pkg: An unexpected error happened during installation: [Errno 16] Device busy
Traceback (most recent call last):
File "/usr/bin/pkg", line 2598, in ?
__ret = main_func()
File "/usr/bin/pkg", line 2541, in main_func
return install(mydir, pargs)
File "/usr/bin/pkg", line 767, in install
api_inst.execute_plan()
File "/usr/lib/python2.4/vendor-packages/pkg/client/api.py", line 525, in
execute_plan
self.img.imageplan.execute()
File "/usr/lib/python2.4/vendor-packages/pkg/client/imageplan.py", line 719,
in execute
p.execute_install(src, dest)
File "/usr/lib/python2.4/vendor-packages/pkg/client/pkgplan.py", line 260, in
execute_install
dest.install(self, src)
File "/usr/lib/python2.4/vendor-packages/pkg/actions/file.py", line 197, in
install
portable.rename(temp, final_path)
File "/usr/lib/python2.4/vendor-packages/pkg/portable/os_unix.py", line 197,
in rename
os.rename(src, dst)
OSError: [Errno 16] Device busy
pkg: This is an internal error. Please let the developers know about this
problem by filing a bug at http://defect.opensolaris.org and including the
above traceback and this message. The version of pkg(5) is '26c3e2407c53'.
$ date
Bad system call(coredump)
$ df
Bad system call(coredump)
$ echo $BUILD
86
$
Does that help?
> > # zfs mount rpool
> > # mount -F tmpfs tmpfs /var/tmp
> > # mount -F tmpfs tmpfs /var/log
> > # beadm create RECOVER (name of your choice here)
>
> I suspect you could have run beadm activate here and saved yourself the
> reboot and the invisible grub menu, but perhaps you tried that and it
> failed?
I didn't try it (I didn't anticipate the grub problems) but my
speculation was that it's not the activate itself that fixed the
problem, it's some difference between running beadm under a normal
environment versus the maintenence mode shell with manually mounted
rpool, etc. I'll try it next time.
-=] Ford [=-
