Hi folks,
I have an issue...I went from 111b to 134 yesterday and all looked good
until I powered off.
After a cold/hard restart (ie. power off) it will no longer boot to my snv_134
BE. I still have 111b - but I really want some of the features in 134 so I am
desperate to get past this issue.
I edited GRUB to remove graphical boot and it still froze...(just after showing
initial version info. and hostname : nas.
I then added -v to the kernel line and it's shown me it's freezing after
displaying the line...
"vboxnet0 is /pseudo/vbox...@0"
I then booted again with -v -m verbose and got the following additional lines...
[ network/routing-setup:default starting (initial routing=related
configuration) ]
[ system/coreadm:default starting (system=wide core file configuration) ]
I am not sure how to proceed...or should I just delete the new BE's (there are
3 of them see below for why), remove VirtualBox and do the upgrade again and
hope for the best?
Need your expert help here guys.
Some additional notes...
I had issues with vboxnet0 (a network interface added by virtual box)
interfering with Samba, so I removed some files and unplumbed it..ie
rm /etc/hostname.vboxnet0
ifconfig vboxnet0 unplumb
I also had issues with upgrading as I had a zone, and had to delete the zone to
update to 134. As I result I have the following BE's (3&4 are failed upgrades
due to the zone) and opensolaris-5 is the 134 that will not boot.
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
mon-may-03 - - 194.0K static 2010-05-03 19:30
opensolaris - - 10.76M static 2010-02-16 21:36
opensolaris-1 N / 209.12M static 2010-02-24 18:14
opensolaris-2 - - 4.38G static 2010-02-24 21:52
opensolaris-3 - - 35.49M static 2010-05-22 02:36
opensolaris-4 - - 46.97M static 2010-05-22 10:44
opensolaris-5 R - 54.26G static 2010-05-22 11:20
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]
