One big / partition *is* a default setup for small storage devices and
there's no reason inherent to that why sysupgrade shouldn't work.
My expectation was that the issue was more likely to do with detecting the
root filesystem but, as Florian points out, this wouldn't explain the
kernel being installed but not the sets.
disklabel output from all disks in the system might give some clues.
--
Sent from a phone, apologies for poor formatting.
On 9 March 2022 21:20:37 Solène Rapenne <sol...@perso.pw> wrote:
Le Wed, 9 Mar 2022 08:50:01 +0100 (CET),
bug.ig...@aleeas.com a écrit :
This is a continuation from this thread:
<https://marc.info/?l=openbsd-bugs&m=164639775618499&w=2>
I tried testing again on the same install and tried my best to create steps
to reproduce & other things I forgot to include before. This
experimentation made me realize that the build number changes with
sysupgrade, but the file sets don't get updated. No error messages are
shown, no emails explaining the incident.
is something wrong happening during the sysupgrade process after you
unlock the disk with the passphrase?
Do you see the script extracting the sets with the progression bar?
I see your setup only use one big / partition, this is not a default
setup and we don't really provide help for such setups because it's
not a supported setup and nobody is testing it.
