On 10/19/24 16:57, Peter Fraser wrote:
I ran sysupgrade and was supprised to still be on the same version of OpenBad.

The /var/log/messages shows:

Oct 19 11:00:01 gateway syslogd[88983]: restart

Oct 19 14:15:12 gateway sysupgrade: installed new /bsd.upgrade. Old kernel version: 
OpenBSD 7.5 (GENERIC.MP) #82: Wed Mar 20 15:48:40 MDT 2024 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP 
<mailto:dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP>Oct
 19 11:00:01 gateway syslogd[88983]: restart

Running sysupgrade show that it is loading the correct files, the partial 
output follows, not all it because the reboot stops me from copying it

sysupgrade -r -k

Fetching from https://ftp.OpenBSD.org/pub/OpenBSD/7.6/amd64/ 
<https://ftp.OpenBSD.org/pub/OpenBSD/7.6/amd64/>

SHA256.sig   100% 
|******************************************************************************************************************|
  2324       00:00

Signature Verified

INSTALL.amd64 100% 
|*****************************************************************************************************************|
 44889       00:00

base76.tgz    18% |********************                                         
                                                     | 79744 KB    24:32 ETA

all the OpenBsd version 7.6 files are under /home/_sysupgrade

Any hints as what is wrong and how to fix it?


The broad, general (i.e., I'm working from unreliable memory) sysupgrade
process is...
On old kernel/userland:
  * Download new install tgz files and kernels
  * copy bsd.rd to /bsd.upgrade
  * reboot
Boot loader sees bsd.upgrade, boots it:
  * upgrade performed
  * reboot
  * record upgrade process for e-mailing to root.
boot new kernel/userland:
  * sysmerge

It appears your system isn't running the bsd.upgrade successfully,
but check for e-mail to root.  I suspect there isn't any.

First step would be to attach a monitor or serial console and see what
is happening when it tries to boot bsd.upgrade.

I've seen this on some odd hw that bsd.rd will crash without a monitor
attached (the full kernel works just fine).  On this particular hw with
no display, bsd.rd panics, and the system reboots (rather
brilliantly, I might point out) on the old kernel and at least your
system didn't get into a boot, crash, reboot, crash, reboot loop.  On
my system, plug a monitor in, and it sysupgrades just fine.  While this
could, in theory, be fixed at the OS level, I'm told Linux refuses to
boot at all on this HW without a monitor attached.  OpenBSD full kernel
at least works headless.

I can't say your issue is monitor related, but we need to know what is
happening when it tries to boot bsd.rd and what the error situation is.
In my case, I found there are cheap HDMI cheater plugs for basically
exactly this purpose (looks like some high-end GPUs don't like to run
without a monitor).  The other free fix is to just do a manual, remote
upgrade (as detailed in the upgrade web page).

Nick.

Reply via email to