Hey Auguste, if you're having problems with snv128, the best thing about
OpenSolaris is that it takes a ZFS snapshot of the old system state before you
upgraded and you can still rewind back to the old snapshot and boot in to the
old version of OpenSolaris (2009.06) using the "beadm" command. Here is a link
to the documentation that explains how the "beadm" command works and how you
can boot in to different "boot environments" that represent different ZFS
snapshots of the system:
http://dlc.sun.com/osol/docs/content/dev/getstart/bootenv.html#indexterm-164
The fact that you can rewind to old pre-update snapshots of the system and boot
up into them and undo all the damage after you have accidentally destroyed
everything was the main reason that I switched from Linux to OpenSolaris.
To let us know what's wrong with your system, when the Grub menu shows up
during boot, hit the "e" key to edit the grub parameters that you are going to
boot up into (you should be able to choose whether or not to boot into the old
OpenSolaris or the new OpenSolaris).
When you are editing grub, delete the following lines:
splashimage /boot/solaris.xpm
foreground d25f00
background 115d93
These lines in GRUB create a very retarded "happy face boot feature" (similar
to Microsoft Windows) that hides and obscures the important debugging
information that you need to see while the computer is booting up. We want to
get a verbose, FreeBSD style boot that sends lots of kernel related logging
messages to the screen and we are going to do this by editing GRUB.
Ok, so I'm sure that you remember from using Linux that the name of the Linux
kernel in GRUB is "vmlinuz", well, the name of the OpenSolaris kernel is
"UNIX", so you want to look for a line in GRUB that says something about
"$kernel /platform.../unix". Once you find this, change the kernel line in GRUB
from this:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS,console=graphics
to this:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS -v
notice that I got rid of the lame "console=graphics" happy face boot B.S. and
added a "-v" for "verbose output" so now we can see what the UNIX kernel is
actually doing.
Watch it boot up and let us know what the last 5 or 6 messages are that are
logged to the screen before it freezes. If you're having problems entering
input into your terminal using a keyboard, you can connect to OpenSolaris using
a serial console cable / rollover cable (like how you connect to a CISCO switch
to configure it). You can use hyperterminal or Putty in Microsoft Windows or
the "tip" command in Solaris or the minicom or kermit commands in Linux to
connect to your OpenSolaris box if it does, in fact, have a DB-9 serial port
(RS232) to connect to.
Here is a blog entry from Dennis Clarke of blastwave fame that explains how to
get an OpenSolaris box to redirect all console output out to the serial port:
http://www.blastwave.org/dclarke/blog/?q=node/110
booting to the serial port and remoting in to it from another computer should
also make it easy to copy and paste the exact error messages that you're
getting in this thread.
You can also find more information about how to do a serial console boot here:
http://opensolaris.org/jive/thread.jspa?messageID=389081
basically you need to boot in to the OpenSolaris live CD environment and import
your rpool zfs pool and edit the /rpool/boot/grub/menu.lst so that it looks
something like this (note the lines such as "spashimage" and "background" that
are commented out and the "-v" parameter passed to the UNIX kernel to make it
boot in verbose mode):
:~$ cat /rpool/boot/grub/menu.lst
#splashimage /boot/grub/splash.xpm.gz
#background 215ECA
timeout 30
default 0
serial --unit=0 --speed=9600 --word=8 --stop=1 --parity=no
terminal serial
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
#
# f^%k bootadm, I'll vi edit whatever I want to
# - the sysadmin
#
title OpenSolaris
findroot (pool_rpool,0,a)
bootfs rpool/ROOT/opensolaris
kernel$ /platform/i86pc/kernel/$ISADIR/unix -v -B $ZFS-BOOTFS -B console=ttya
module$ /platform/i86pc/$ISADIR/boot_archive
#---------------------END BOOTADM--------------------
Try it and see if you can get the serial console thing working. It's a really
useful thing to have, especially if you accidentally destroyed the network
configuration on your server and can't SSH in and you need to get a console on
it ASAP even though you're a thousand miles away from the data center. Well, if
you have another server that's in the same cabinet that you can SSH in to and
you have a serial console cable going from one server to another server then
you can use the serial console to log in and fix the broken network settings
and bring your downed server back online.
--
This message posted from opensolaris.org
