Menu

Show posts

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 Menu

Messages - superduke1010

#1
Thanks Patrick....microcode was installed.  Looking for and more like a total H/W failure of some kind.  I need to buy a total new mini PC to confirm....but I have new RAM and new SSD on the old box and all kinds of glitchy issues....brutal!

Lucky I have an old warhorse box as my cold backup but now I need to really think about double redundancy...lol
#2
Certainly pointing to a fried Topton box at this point.  Now I have to figure out which mini pc I want to chance now!
#3
Oh dear....a TON of missing files under the health audit....wtf

Not sure why it would still be a hardware issue necessarily with the RAM and storage both brand spanking new....did a clean install (although I did revert to UFS instead of ZFS because I only had one drive) but I don't think a config refresh after an install impacts that does it?  Thanks for the quick reply.

Edit: SMART test of new drive passes
#4
Hardware issue.  Memtest on RAM came back fine but changed it out, but didn't have SMART plugin installed to check SSDs but changed them out too.  Bare metal install and config restore and system came back to life without issue.

Having kernel updating issues now, post on another thread.
#5
Hello all....turns out my RAM or SSDs were fried on my Topton (other post with widgets etc).  Changed them out and did a bare metal install.  All is well except when I try and update to 25.1.1 I get the following.  Have never seen that before.  Any help would be appreciated.  thanks

***GOT REQUEST TO UPDATE***
Currently running OPNsense 25.1.1 (amd64) at Wed Feb 26 17:54:10 EST 2025
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (122 candidates): .......... done
Processing candidates (122 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
Checking integrity... done (0 conflicting)
Nothing to do.
Checking all packages: .......... done
The following package files will be deleted:
/var/cache/pkg/x86info-1.31.s03_1~dbb2eda5d2.pkg
/var/cache/pkg/cpu-microcode-rc-1.0_2.pkg
/var/cache/pkg/x86info-1.31.s03_1.pkg
/var/cache/pkg/pciids-20250127~859b46d158.pkg
/var/cache/pkg/pciids-20250127.pkg
/var/cache/pkg/cpu-microcode-rc-1.0_2~99322c5e25.pkg
/var/cache/pkg/libpci-3.13.0~4c1389cfd9.pkg
/var/cache/pkg/libpci-3.13.0.pkg
/var/cache/pkg/cpu-microcode-intel-20241112~4ebeeff8ee.pkg
/var/cache/pkg/os-cpu-microcode-intel-1.1~50eaaabc00.pkg
/var/cache/pkg/cpu-microcode-intel-20241112.pkg
/var/cache/pkg/os-smart-2.3~8fb32cb7e8.pkg
/var/cache/pkg/os-cpu-microcode-intel-1.1.pkg
/var/cache/pkg/smartmontools-7.4_2.pkg
/var/cache/pkg/os-smart-2.3.pkg
/var/cache/pkg/smartmontools-7.4_2~dd8d8423a5.pkg
/var/cache/pkg/libmilter-8.18.1~3b08d89f05.pkg
/var/cache/pkg/arc-5.21q_1~27f5400a01.pkg
/var/cache/pkg/libmilter-8.18.1.pkg
/var/cache/pkg/libmspack-0.11alpha~65d1465e96.pkg
/var/cache/pkg/libmspack-0.11alpha.pkg
/var/cache/pkg/clamav-1.4.2,1~89501ebb28.pkg
/var/cache/pkg/clamav-1.4.2,1.pkg
/var/cache/pkg/arj-3.10.22_12~da096115f5.pkg
/var/cache/pkg/arj-3.10.22_12.pkg
/var/cache/pkg/c-icap-0.6.3,2~4ddb96f4ea.pkg
/var/cache/pkg/arc-5.21q_1.pkg
/var/cache/pkg/os-dmidecode-1.1_1.pkg
/var/cache/pkg/c-icap-0.6.3,2.pkg
/var/cache/pkg/c-icap-modules-0.5.7_1~57e398558d.pkg
/var/cache/pkg/pcre-8.45_4~8118507b40.pkg
/var/cache/pkg/c-icap-modules-0.5.7_1.pkg
/var/cache/pkg/pcre-8.45_4.pkg
/var/cache/pkg/unzoo-4.4_2~76e1636474.pkg
/var/cache/pkg/unzoo-4.4_2.pkg
/var/cache/pkg/os-c-icap-1.7_5~fe04b74fef.pkg
/var/cache/pkg/os-c-icap-1.7_5.pkg
/var/cache/pkg/os-dmidecode-1.1_1~57df82e025.pkg
/var/cache/pkg/dmidecode-3.6~eddd565497.pkg
/var/cache/pkg/dmidecode-3.6.pkg
/var/cache/pkg/os-clamav-1.8_2~13715ea7c0.pkg
/var/cache/pkg/os-clamav-1.8_2.pkg
/var/cache/pkg/os-theme-vicuna-1.48~85d321fa13.pkg
/var/cache/pkg/os-theme-vicuna-1.48.pkg
The cleanup will free 27 MiB
Deleting files: .......... done
All done
Nothing to do.
Starting web GUI...done.
Fetching base-25.1.1-amd64.txz: ........... done
Fetching kernel-25.1.1-amd64.txz: ...... done
!!!!!!!!!!!! ATTENTION !!!!!!!!!!!!!!!
! A critical upgrade is in progress. !
! Please do not turn off the system. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Installing kernel-25.1.1-amd64.txz.../usr/local/sbin/opnsense-update: tar: not found
 failed, tar error 0
***DONE***
#6
Quote from: bartjsmit on February 25, 2025, 07:32:16 AMRun a memory test https://www.memtest86.com/

Thanks...good idea.  Ran the test, went through the first round and no issues of note.  Might be a SSD issue as well as I've looked at the forum and it seems as if some SSDs in ZFS fail due to overuse.  Certainly did seem like a memory issue so I was hopeful.  Ended up buying a new SSD and stick of ram anyhow.
#7
Repost from Reddit....

As above, OPNSense 25 has been rock solid for me (as have all versions really).  Don't think this has to do with the software but wanted to ask.
Today network was choppy and logged into the firewall to see widgets failing to load one by one until all fail and the links in the Webgui were very slow to respond. 
Tried rebooting, same result.  Tried reverting to older snapshot, same result. 
Hardware is Topton N100.
Removed box from network and plugged in my old cold spare (on 13.7 if you can believe it) and everything is fine.  Plugged locally into the Topton and all seems well and solid when logging into to GUI, widgets load and do not fail.  Power off, put it back into the system and same behaviour.  Logs looked clear (from what I could tell) and did a top when plugged in locally to see if any stray processes were screwing sheet up.  I do get a crowdsec error on boot up mind you, so my next trick was to try and killall just in case.
Thinking it's hardware related, but odd that locally it seems stable but when plugged into the network it goes to hell.  Thought a port issue so might try redefining interfaces to another pair.
Any thoughts would help immensely.  Thanks.