Messages

Maybe just use ZFS ?

Took a chance and backed up my config, fresh installed using ZFS and restored. Running fine thank you for heading me in the direction easier than I thought.

I had similar issues with installing 25.7 (data corruption) installing the OS_CPU_MICROCODE_INTEL Plugin resolved the issue, previously was Not installed when I experienced the errors. Hooked up an monitor and noticed cluster errors during boot from upgrade (boot loop) reverted back to previous version installed the microcode plugin and then upgraded it has been running for an week now and several reboots no issues.

[not]

Here are the details:

Code Select Expand

Reloading firmware configuration
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from cpu-microcode-rc-1.0_2:

--
This port includes an RC script, which is one of two methods to update
the CPU microcode on a FreeBSD system.

1. Early loading.
   This method does not use the RC script included here.
   This is the preferred method, because it ensures that any CPU features
   added or removed by a microcode update are visible to the kernel by
   applying the update before the kernel performs CPU feature detection.

   To enable updates using early loading, add the following lines to
   /boot/loader.conf:

   cpu_microcode_load="YES"

   and the appropriate one of these lines:

   cpu_microcode_name="/boot/firmware/intel-ucode.bin"
   cpu_microcode_name="/boot/firmware/amd-ucode.bin"

   The microcode update will be loaded when the system is rebooted.

   AMD systems running FreeBSD prior to 2024-02-22 snapshot
   34467bd76 only support late loading.


2. Late loading.
   This method, which does use the RC script included here, is enabled by
   adding the following line to /etc/rc.conf:

   microcode_update_enable="YES"

   The microcode update is then applied upon reboot or when the microcode
   update service is run via:

   # service microcode_update start

   If the CPU requires a microcode update, a console message such as the
   following will appear:

   Updating CPU Microcode...
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl0 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl2 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl4 from rev 0x17 to rev 0x22... done.
   /usr/local/share/cpucontrol/m32306c3_00000022.fw: updating cpu /dev/cpuctl6 from rev 0x17 to rev 0x22... done.
   Done.

It is safe to enable both methods.
=====
Message from x86info-1.31.s03_1:

--
===>   NOTICE:

This port is deprecated; you may wish to reconsider installing it:

Abandoned upstream, fails to identify anything remotely new according to upstream issue reports.

It is scheduled to be removed on or after 2025-06-30.
=====
Message from cpu-microcode-amd-20241121:

--
Refer to the cpu-microcode-rc installation notes to enable AMD microcode
updates.
Checking integrity... done (0 conflicting)
Nothing to do.
***DONE***

And as you can see, the notice pertains only to the x86info package, which installs alongside the microcode update in order to be able to actually query which microcode is loaded, not to the microcode package itself.

Appreciate the clarification (still learning) I have loaded the Intel V1.1 of the plug in and still received the message about depreciation but not all the detail that you provided (appears to be an older and x86?)so going forward the microcode as long as it is v1.1 and not x86 will receive updates without special intervention?

Thank you all that replied

Mark

I also fail to see where that is said. The info about os-microcode-intel and/or os-cpu-microcode-amd does not state anything to that extent.

And there are no security risks as long as you can accomplish to update the microcode via BIOS updates. But: Many systems out there may not be elegible for that, either because they are out of warranty (being old repurposed boxes) or their manufacturers do no support that in the first place (many chinese boxes fall into that category).

IDK why some systems with that plugin failed on reboot after the update, FWIW, I did not have that problem on any of may 7 machines.

During the install of the plug in 'Console Window' when it downloads, extracts and installs there is a message that states about depreciation. Sorry did not think about notating the details.

When you install the microcode plugin, does it tell you that the code updates are not reliable or not fruitful (or something like that), and that you might want to rethink installing it?

It did indeed state that the microcode would no longer be supported nor updated. Decided to try it out anyway since I have had issues updating/clean install v25.7 since it was released.

Finally realized that I did Not have os_cpu_microcode_intel installed on v25.1.12 so I installed and checked for updates, installed v25.7 and it came up clean. Have rebooted three times to make sure and no issues.

Similar situation, hooked up an Monitor and it appeared that the SSD was bad, stating when 25.7 was installed that it needed to recover clusters etc. then eventually would not boot. Uninstalled 25.7 and reinstalled 25.1.12 and no issues 2 days and counting. May try removing the Intel Microcode later and trying to install 25.7 again, spent an entire day troubleshooting. I am running the Glovary Mini PC with N100 Alder Lake CPU