Little confused - is 24.11 not available for SG-1100? Says at latest revision 24.03 RELEASE
-
@SteveITS Encountered this error: Checking integrity...Bus error (core dumped)
Device rebooted; can I go ahead and try the update again or will that cause an issue? Update page is still displayed in the web browser, I have not reloaded it.
-
The most common cause there is memory exhaustion. Try rebooting before upgrade to free RAM. If it still fails you may need to disable any packages you might have installed.
-
@stephenw10 I keep getting this error, even after several reboots:
Is there some 'flag' someplace that needs to be cleared so that it doesn't think it's in the middle of an update already?
-
Nope that's just the update check. On the 1100 it can take longer than expected. Just refresh the page in a minute or so.
-
@stephenw10 Failed again:
The only package I have installed is pfBlockerNG-devel (whcih states it's deprecated). I don't see any way to disable it (other than removing it).
Should I delete it ad then reinstall the latest version, or do the update inside the package manager?
-
Deleted pfBlockerNG and tried again. Failed again. Bus error.
I noted this error in the top of the GUI (message indicator):
pkg: "Upgrading packages in cloned boot environment default" returned error code 138 @ 2025-05-22 10:56:47 -
Ah, it could be out of space. It should give a more helpful error though.
But check System > Boot Environments and remove any older snapshots you're not using.
-
@stephenw10 There's only one boot environment (the current one).
Here's the vitals (right after a reboot, CPU usage tends to diminish after a bit):
-
I'd expect that to be OK.
You could check Diag > System Activity to see what is using RAM.
-
@stephenw10 if the update "BUS error - core dumps" is that indicating it's running out of memory?
When I removed pfBlocker earlier, using the package manager, it asked for confirmation and then says it removed it. However I later realized it was still there and still active. Do I need to reboot the device after removing a package, in order to free up the memory it was using?
-
Hmm, no you should not need to reboot.
Do you have a more complete log showing that error in context?
-
@stephenw10 Where in the system can I pull the upgrade log, I didn't see anything. I guess I can try again and try to capture it.
It fails at random places during the process, so I don't think it's related to one single library that it's downloading. Also the farthest it gets is the integrity check. If it makes it that far, that's about as far as it gets.
-
You should be able to copy/paste it from the GUI.
But you could also run the upgrade using option 13 from the console menu. Then you get the full output and easily copy it out.
-
@stephenw10 I'll run it from the console once I get back home and post it.
-
@NGUSER6947 Well here's the console output:
-
@stephenw10 I suspect, that since the Dashboard doesn't recognize that 24.03 isn't the newest release, that from the console it just tries to update 24.03 and of course it's already on the latest. Possible?
-
Yes it looks like it's still set to the 24.03 branch. You should be able to set it to use the 24.11 branch in the gui then run the upgrade from the console.
Also one of the main advantages of using the serial console (or ssh) for this is that you can easily copy and paste the actual text output rather than use screenshots. That is much easier to read through for diagnosis.
-
@stephenw10 I set it to 24.11 in the web gui, then launched the update from the console.
It first did a 24.03 update to Patch 1 (but faulted in the middle then continued), then I repeated and it started (downloaded the 24.11 libraries) but then faulted. It kept going but at reboot shows it's still at 24.03.
Attached is the log from the console, for the 2nd round.putty.zip
-
Hmm so it did appear to upgrade to 24.03 patch 1?
You might have a filesystem issue that cannot be fixed by the normal processes that run at boot. It's also possible you have an issue with the eMMC drive.
Try checking the eMMC status: https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html#emmc
If that looks OK then I'd try backing up the config and re-installing 24.11 clean: https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html
-
@stephenw10 Tried checking the eMMC status (and it displayed a lot if information), but it appears my unit doesn't support the EOL information. No output when I tried that last command (the one with egrep) and scanning the output manually shows nothing regarding EOL.
