Hi,
I just tried out sysupgrade on one of my OpenBSD 6.5 servers in order to
upgrade automatically to 6.6 but unfortunately it failed at the comp66.tgz and
rebooted (upgrade log below).
It looks like I am now running a half-upgraded hybrid OpenBSD 6.5/6.6 system.
It also didn't manage to relink the kernel after reboot (log file below).
So I was wondering if anyone had any recommendations or insights to my
following points:
- reason why it failed?
- what should I do now? retry to upgrade with sysupgrade?
- re-install the whole system?
- maybe sysupgrade needs to be patched to avoid this issue?
Best regards,
Mabi
*** output of upgrade log ***
Terminal type? [vt220] vt220
Available disks are: sd0.
Which disk is the root disk? ('?' for details) [sd0] sd0
Checking root filesystem (fsck -fp /dev/sd0a)... OK.
Mounting root filesystem (mount -o ro /dev/sd0a /mnt)... OK.
Force checking of clean non-root filesystems? [no] no
fsck -p f8bd514855ccf1e5.f... OK.
fsck -p f8bd514855ccf1e5.d... OK.
fsck -p f8bd514855ccf1e5.e... OK.
fsck -p f8bd514855ccf1e5.g... OK.
/dev/sd0a (f8bd514855ccf1e5.a) on /mnt type ffs (rw, local)
/dev/sd0f (f8bd514855ccf1e5.f) on /mnt/home type ffs (rw, local, nodev, nosuid)
/dev/sd0d (f8bd514855ccf1e5.d) on /mnt/tmp type ffs (rw, local, nodev, nosuid)
/dev/sd0e (f8bd514855ccf1e5.e) on /mnt/usr type ffs (rw, local, nodev,
wxallowed)
/dev/sd0g (f8bd514855ccf1e5.g) on /mnt/var type ffs (rw, local, nodev, nosuid)
Let's upgrade the sets!
Location of sets? (cd0 disk http nfs or 'done') [http] disk
Is the disk partition already mounted? [yes] yes
Pathname to the sets? (or 'done') [6.6/amd64] /home/_sysupgrade/
Select sets by entering a set name, a file name pattern or 'all'. De-select
sets by prepending a '-', e.g.: '-game*'. Selected sets are labelled '[X]'.
[X] bsd [X] base66.tgz [X] game66.tgz [X] xfont66.tgz
[X] bsd.mp [X] comp66.tgz [X] xbase66.tgz [X] xserv66.tgz
[X] bsd.rd [X] man66.tgz [X] xshare66.tgz
Set name(s)? (or 'abort' or 'done') [done] done
Directory does not contain SHA256.sig. Continue without verification? [no] yes
Installing bsd 100% |**************************| 18250 KB 00:00
Installing bsd.mp 100% |**************************| 18336 KB 00:00
Installing bsd.rd 100% |**************************| 10058 KB 00:00
Installing base66.tgz 100% |**************************| 236 MB 00:36
Installing comp66.tgz 81% |********************* | 58880 KB 00:02
ETAtar: Unable to remove directory ./usr/include/machine: Directory not empty
Installing comp66.tgz 100% |**************************| 72109 KB 00:14
Installation of comp66.tgz failed. Continue anyway? [no] no
*** output of /usr/share/relink/kernel/GENERIC/relink.log ***
(SHA256) /bsd: FAILED
Failed to verify /bsd's checksum, therefore a randomly linked kernel (KARL)
is not being built. KARL can be re-enabled for next boot by issuing as root:
sha256 -h /var/db/kernel.SHA256 /bsd
