Nandini,
If you're upgrading from such an older release, is it possible that
you're hitting one of the following issues listed in the release notes:
6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346
After updating to build 130 or beyond, the system may panic
with messages of the form
/kernel/misc/amd64/pci_autoconfig:
undefined symbol 'pcie_get_rc_dip'
WARNING: mod_load: cannot load module 'pci_autoconfig'
panic[cpu0]/thread=fffffffffbc2e3a0:
failed to load misc/pci_autoconfig
Work-around: Boot the original boot environment (BE) instead
and correct the boot archive as follows
<reboot into the earlier BE>
user at host$ pfexec beadm mount <name of new BE> /mnt
user at host$ pfexec bootadm update-archive -F -R /mnt
user at host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
12380 image-update loses /dev/ptmx from /etc/minor_perm
http://defect.opensolaris.org/bz/show_bug.cgi?id=12380
When using image-update or the Package Manager to update to
build 125 or greater, remote access to the system via ssh(1) or
rlogin(1) may become unavailable. Alternatively, using
terminal programs such as gnome-terminal(1) or xterm(1) may
result in characters not being echoed or commands unable to be
typed.
Work-around: Boot the original boot environment (BE) instead
and correct the /etc/minor_perm file contained within as
follows
<reboot into the earlier BE>
user at host$ pfexec beadm mount <name of new BE> /mnt
user at host$ pfexec sh -c \
"grep ^clone: /etc/minor_perm >> /mnt/etc/minor_perm"
user at host$ pfexec touch /mnt/reconfigure
user at host$ pfexec bootadm update-archive -R /mnt
user at host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
Taken from:
http://mail.opensolaris.org/pipermail/opensolaris-announce/2010-March/001421.html
On 03/24/10 02:21 PM, Nandini Mocherla wrote:
Hi Clay,
I have seen the grub menu and until it displayed "Use is subject to
license terms." And then no output is redirected to SP/console. If I
boot back to old BE, I could see the output onto SP again. Here is the
output from the SP/console. Thanks,
SunOS Release 5.11 Version snv_134 64-bit
Copyright 1983-2010 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
*******could not see after this****************************
-- Nandini
[email protected] wrote:
Hi Nandini,
I have not seen this type of failure before. However, to confirm, you
do see the GRUB menu at boot and then what is the last piece of
information displayed on the SP before it goes blank? The IPS team may
also have insight into this, since they provide the upgrade mechanism.
Thank you,
Clay
On Tue, 23 Mar 2010, Nandini Mocherla wrote:
Hi,
I have upgraded one of our systems running OpenSolaris 2009.06 to dev
build 134. The
upgrade went fine and the system is up and running b134. I have not
seen any significant
errors during the upgrade except for the 'pcieb' driver. The only
problem I am seeing
after the upgrade is, I can't see the output from /SP/console.
The issue was there in every build for the initial install and I am
following the
workaround by changing the grub/menu.lst file. But haven't seen this
after upgrade as
the new BE also uses same menu.lst file. Is it a bug in b134 and is
there any work
around for this issue?
--
-- Nandini
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
