OPNsense Forum

English Forums => 25.7, 25.10 Legacy Series => Topic started by: zackboll on April 22, 2026, 03:10:44 AM

Title: Opnsense file corruption
Post by: zackboll on April 22, 2026, 03:10:44 AM
Hi,

I believe I have a failing SSD so I am currently in the process of buying a new one.

A number of my opnsense packages were corrupted, but I was able to resolve most issues by reinstalling the package.  I am currently stuck on the package (cc) c compiler.  I keep getting pager fault errors, and I cannot figure out how to reinstall the package that provides it.

root@OPNsense:~ # pkg which /usr/bin/cc
/usr/bin/cc was not found in the database

Output from dmesg for example of error:
[87] vm_fault: pager read error, pid 14115 (cc)
[87] pid 14115 (cc), jid 0, uid 0: exited on signal 10 (no core dump - bad address)
[116] vm_fault: pager read error, pid 29661 (cc)
[116] pid 29661 (cc), jid 0, uid 0: exited on signal 10 (no core dump - bad address)
[176] vm_fault: pager read error, pid 75465 (cc)
[176] pid 75465 (cc), jid 0, uid 0: exited on signal 10 (no core dump - bad address)

I was getting many more vm_fault before I reinstalled all packages (with pkg upgrade -f).  Any idea how I can reinstall /usr/bin/cc?

When I try to use executable:
root@OPNsense:~ # cc --version
Bus error

Worse case scenario, I can start from a fresh install (on new SSD) and try to restore from backup configuration.  I am currently running on the latest version 25.x series, the thought crossed my mind about trying to do in-place upgrade to 26.x to see if that fixes my corrupted filesystem.  Since my firewall is currently partly operational, and I have internet, I figure it may be better to wait until my new SSD arrives. 

Any ideas how to resolve the vm_fault errors stemming from the corrupted cc binary would be appreciated.

Thanks,
Zack
Title: Re: Opnsense file corruption
Post by: franco on April 22, 2026, 07:42:53 AM
/usr/bin/cc is part of the "base" "package". You can reinstall it from the firmware GUI packages tab or

# opnsense-update -fb
(reboot)


Cheers,
Franco
Title: Re: Opnsense file corruption
Post by: zackboll on April 22, 2026, 08:01:28 AM
Thank you, that worked!
Title: Re: Opnsense file corruption
Post by: nero355 on April 22, 2026, 03:36:25 PM
Quote from: zackboll on Today at 03:10:44 AMI believe I have a failing SSD
if you think that then you should check the S.M.A.R.T. data with either smartctl or nvmecontrol first and then look further :)

See :
- https://man.freebsd.org/cgi/man.cgi?query=smartctl
- https://man.freebsd.org/cgi/man.cgi?query=nvmecontrol