Discussion:
[OpenIndiana-discuss] Unable to boot from BE created today
russell
2018-11-02 18:47:48 UTC
Permalink
Hi,

Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.

Is anyone else experiencing the same problem?


Regards

Russell
Till Wegmüller
2018-11-02 19:38:14 UTC
Permalink
Hi Russel

Did /var/adm/messages Say anything about the rebooting? Like a Panic?

Greetings
Till
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
openindiana-discuss mailing list
https://openindiana.org/mailman/listinfo/openindiana-discuss
Geoff Nordli
2018-11-02 20:36:59 UTC
Permalink
Post by Till Wegmüller
Hi Russel
Did /var/adm/messages Say anything about the rebooting? Like a Panic?
Greetings
Till
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
Hi Russell.

I had some problems the other day going from legacy OI -> Hipster.  I
ended up having to go to just Hipster-2015.

At the very end of the upgrade I was getting an error like:

pkg /sbin/bootadm update-archive -R /tmp/xxxxx failed with a return code
of 1

Do you see something like that?

Geoff
Till Wegmüller
2018-11-02 20:59:47 UTC
Permalink
Ah yeah that is a quite old one :)

You need to use the bootadm from the new BE.

Greetings
Till
Post by Geoff Nordli
Post by Till Wegmüller
Hi Russel
Did /var/adm/messages Say anything about the rebooting? Like a Panic?
Greetings
Till
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
Hi Russell.
I had some problems the other day going from legacy OI -> Hipster.  I
ended up having to go to just Hipster-2015.
pkg /sbin/bootadm update-archive -R /tmp/xxxxx failed with a return code
of 1
Do you see something like that?
Geoff
_______________________________________________
openindiana-discuss mailing list
https://openindiana.org/mailman/listinfo/openindiana-discuss
Geoff Nordli
2018-11-03 02:51:06 UTC
Permalink
Post by Till Wegmüller
Ah yeah that is a quite old one :)
You need to use the bootadm from the new BE.
Greetings
Till
Post by Geoff Nordli
Post by Till Wegmüller
Hi Russel
Did /var/adm/messages Say anything about the rebooting? Like a Panic?
Greetings
Till
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
Hi Russell.
I had some problems the other day going from legacy OI -> Hipster.  I
ended up having to go to just Hipster-2015.
pkg /sbin/bootadm update-archive -R /tmp/xxxxx failed with a return code
of 1
Do you see something like that?
Geoff
Thanks for the info Till, sorry for hi-jacking the thread.  I thought it
may have been related.

I will give that a try.

Geoff
Michal Nowak
2018-11-02 22:57:56 UTC
Permalink
Post by Geoff Nordli
Post by Till Wegmüller
Hi Russel
Did /var/adm/messages Say anything about the rebooting? Like a Panic?
Greetings
Till
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
Hi Russell.
I had some problems the other day going from legacy OI -> Hipster.  I
ended up having to go to just Hipster-2015.
pkg /sbin/bootadm update-archive -R /tmp/xxxxx failed with a return code
of 1
Do you see something like that?
Geoff
Russel,

this is what we do in our tests for OI releases before 20170503:
https://github.com/OpenIndiana/os-autoinst-distri-openindiana/blob/master/tests/update/pkg_update_to_latest_packages.pm#L46.

Here
https://openqa.oi.mnowak.cz/tests/4172#step/pkg_update_to_latest_packages/9
you can see how it plays out in the MATE environment.

Michal
russell
2018-11-03 10:56:53 UTC
Permalink
Hi,

Just to be clear, I am currently running a BE created on 2018-08-11
@11:01, I have performed a number of updates and created new BE since
then but have deleted them when I can not use them with VirtualBox.

This morning I attempted to boot from the BE environment created
2018-11-02 @ 14:57, I got the splash screen with the horizontal line but
then as before my computer rebooted unexpectedly. When the reboot to
place it automatically booted into the 2018-08-11 BE. I mounted the
broken BE with

# beadm mount oihipster201811-01 /tmp/broken

Then proceeded to look at /tmp/broken/var/adm/messages, the file
contained no reference date of Nov 03, syslog also contained no
reference to Nov 03. Checking the time stamps on the files, nothing
appeared to be dated Nov 03. It was though the BE had never been booted.

Regards

Russell
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
Till Wegmüller
2018-11-03 12:43:59 UTC
Permalink
Hi

I just updated today and It worked flawlessly.

I am curious why you are getting a splash screen with a Horizontal Line
though.

Are you using Grub still? AFAIk Loader does not put any Splash screen
lines on the Boot command line by default

Greetings
Till
Post by russell
Hi,
Just to be clear, I am currently running a BE created on 2018-08-11
@11:01, I have performed a number of updates and created new BE since
then but have deleted them when I can not use them with VirtualBox.
This morning I attempted to boot from the BE environment created
then as before my computer rebooted unexpectedly. When the reboot to
place it automatically booted into the 2018-08-11 BE. I mounted the
broken BE with
# beadm mount oihipster201811-01 /tmp/broken
Then proceeded to look at /tmp/broken/var/adm/messages, the file
contained no reference date of Nov 03, syslog also contained no
reference to Nov 03. Checking the time stamps on the files, nothing
appeared to be dated Nov 03. It was though the BE had never been booted.
Regards
Russell
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
_______________________________________________
openindiana-discuss mailing list
https://openindiana.org/mailman/listinfo/openindiana-discuss
russell
2018-11-05 18:54:04 UTC
Permalink
Hi,

My OpenIndiana desktop rpool is still using Grub during boot, my rpool
is an mirrored pair of disks which have been replaced a few times but is
still the same partitioning from when I was using OpenSolaris.

Regards

Russell
Post by russell
Hi,
Just to be clear, I am currently running a BE created on 2018-08-11
@11:01, I have performed a number of updates and created new BE since
then but have deleted them when I can not use them with VirtualBox.
This morning I attempted to boot from the BE environment created
but then as before my computer rebooted unexpectedly. When the reboot
to place it automatically booted into the 2018-08-11 BE. I mounted the
broken BE with
# beadm mount oihipster201811-01 /tmp/broken
Then proceeded to look at /tmp/broken/var/adm/messages, the file
contained no reference date of Nov 03, syslog also contained no
reference to Nov 03. Checking the time stamps on the files, nothing
appeared to be dated Nov 03. It was though the BE had never been booted.
Regards
Russell
Post by russell
Hi,
Today I performed a pkg refresh and update to create a new BE, I did
however make my previous BE the active one before attempting to boot
from the new BE. Booting occurs normal, I select the new BE created
today, the boot process starts and then my computer reboots within 8
seconds.
Is anyone else experiencing the same problem?
Regards
Russell
Loading...