Re: After sysupgrade -s yesterday /bsd fails to boot
Lloyd <[email protected]> Sat, 16 May 2026 07:34:04 +0000
| Newsgroups | gmane.os.openbsd.bugs |
|---|---|
| Message-ID | <2jtnXTjos16dXn7UgVOFNP_zoA7qzS4DigVu17WmVlAfYjMVlqkBvU2wR-fmf6n7R6KOfGpCkcmIjaRKZME0HQm0elbzde4gqV9CjERQYQA=@proton.me> |
# mv /bsd /bsd.bad # cp /bsd.booted /bsd Then try again. Maybe you got a bad snapshot. How is /usr doing on space? There was an issue a minute ago where a full /usr could cause a corrupt /bsd to be generated and installed due to the linker ignoring ENOSPC and returning 0 but I think it got fixed....? Regards Lloyd [email protected] wrote: > >Synopsis: > fails to boot /bsd after sysupgrade -s > >Category: > kernel > >Environment: > System : OpenBSD 7.9 > Details : OpenBSD 7.9-current (GENERIC) #413: Fri May 15 03:19:07 UTC 2026 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > Yesterday 14th May I ran doas sysupgrade -s as I do daily only this time it would not boot /bsd ending with error 255 unknown > I can boot /bsd.booted and /bsd.sp ok > Also the log file /usr/share/relink/kernel/GENERIC/relink.log > > make: don't know how to make newbsd > Stop in /usr/share/relink/kernel/GENERIC > > >How-To-Repeat: > Repeat as above > >Fix: >