This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: os914964619 on July 11, 2022, 05:15:51 PM
I am running the latest Opnsense and decided to run zpool upgrade. Here was the result:Quoteroot@router:~ # zpool upgrade zroot
This system supports ZFS pool feature flags.
Enabled the following features on 'zroot':
userobj_accounting
encryption
project_quota
allocation_classes
resilver_defer
bookmark_v2
redaction_bookmarks
redacted_datasets
bookmark_written
log_spacemap
livelist
device_rebuild
zstd_compress
draid
Pool 'zroot' has the bootfs property set, you might need to update
the boot code. See gptzfsboot and loader.efi for details.
Is there anything I need to do, or can I reboot? I am worried that I'm going to brick my opnsense install by not updating "the boot code".
Quote from: rackg on November 28, 2021, 03:06:26 AM
Some more logs strange behavior w.r.t file system space.
root@limestone:/usr/tools # mount
/dev/gpt/rootfs on / (ufs, local, soft-updates)
devfs on /dev (devfs)
/dev/gpt/efiesp on /boot/efi (msdosfs, local)
<below>:/usr/ports on /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/usr/ports (unionfs, local, soft-updates)
<below>:/usr/src on /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/usr/src (unionfs, local, soft-updates)
devfs on /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/dev (devfs)
<below>:/usr/ports on /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/usr/ports (unionfs, local, soft-updates)
<below>:/usr/src on /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/usr/src (unionfs, local, soft-updates)
devfs on /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/dev (devfs)
root@limestone:/usr/tools #
root@limestone:/usr/tools #
root@limestone:/usr/tools #
root@limestone:/usr/tools # df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/gpt/rootfs 76G 48G 22G 69% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/gpt/efiesp 32M 878K 31M 3% /boot/efi
<below>:/usr/ports 153G 125G 22G 85% /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/usr/ports
<below>:/usr/src 153G 125G 22G 85% /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/usr/src
devfs 1.0K 1.0K 0B 100% /usr/obj/usr/tools/config/22.1/LibreSSL:amd64/dev
<below>:/usr/ports 153G 125G 22G 85% /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/usr/ports
<below>:/usr/src 153G 125G 22G 85% /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/usr/src
devfs 1.0K 1.0K 0B 100% /usr/obj/usr/tools/config/22.1/OpenSSL:amd64/dev
root@limestone:/usr/tools #
Quote from: mimugmail on December 05, 2021, 07:04:55 AMI have to verify the same. I just uninstalled the pkg version 1.17. Compiled and installed the following pkg version from ports of git version.
There is already a confirmation with similar problem where downgrade helped
Quote from: franco on December 01, 2021, 02:46:55 PM
My guess is that pkg 1.17 installed in your build system breaks this. You can see the failing command with VERBOSE=yes and I suspect that pkg-repo looks for *.pkg files but we still have *.txz files.
Not a lot of care was taken by the FreeBSD ecosystem to keep the established system running with anything but cutting edge tools that do produce backwards compatible output, but that's obviously not our worry here since we can't get to that state where it produces anything. ;)
Cheers,
Franco
Quote from: mimugmail on December 01, 2021, 02:43:32 PM
I would try a fresh install, disable LibreSSL, dont touch anything else (like additional ports etc.) and start with make dvd. If this works then enlarge, if not, there's room to debug.