As additional info,  I've spotted

/usr/local/etc/rd.d/microcode_update:  exec_format_error

Oops!

https://forum.pfsense.org/index.php?action=search

Which bios version do you have? There are known problems with latest bios (4.6.x mainline branch) when accessing hard disks:

v4.6.x BIOSes need to have MSI disabled, due to signal races causing disk write commands timeouts.

Read more at pc engines github page.
Maybe your issue is related to this bug?

Well, I am in Sweden, so that might be a reason. There are more fiber here than blonde girls…

This solved it!

https://forum.pfsense.org/index.php?topic=105398.0

@nattygreg:

the package manager is broken in 2.4.2 , 2.4.2_1 and 2.4.3

Irrelevant to know, he's using 2.3.4 on an ALIX board which cannot run 64-bit software at all.

Just posting because it might help others:
Friend of mine had failed update as well; upgrade from gui but following on console.
Seems file system was read-only? (Could this be something left over from nanobsd days?)

Attached the screenshot I got from him… (no credits here)

update243.JPG
update243.JPG_thumb

@LanceD:

Just forced the update again like described here https://www.netgate.com/docs/pfsense/sg-4860/reinstall-pfsense.html

Everything workes fine.  :)

Did the same.  At least the machine works again now.

This was not so nice.

Monitoring logs are lost apparently. However, the config could be salvaged as described above. I still have no idea, why the update failed.

There's a post with a redmine ticket here.
For what it's worth, I've hit this bug too.

Today is the day I reply to myself.

My current workarround:  disabling the umass driver with a device hint

/boot/device.hints
add the line  hint.umass.0.disabled="1"

That setting takes all unsolicited traffic coming into its WAN and forwards it to a specific IP address on the inside. That would be pfSense's WAN address.

@stephenw10:

You can test it against a single client by adding a firewall rule to pass traffic from just that one IP at the top of the LAN list and setting it's gateway to the BT WAN directly.

Steve

Thanks that worked!

I can not access anymore the webinterface

What does "can't access" mean?  You get an error message?  It times out?  Your login fails?  The page only half-renders?  What have you tried to fix it?  Did you clear your browser cache?  Have you tried a different browser?  Did you go to console and select option 11 or 16?

Hi !

I have solutionned my problem.

Thing is that my old install was on an unknown VM system, so the Integrations options in advanced features for proxy server was :
redirect_program /usr/pbi/squidguard-amd64/bin/squidGuard -c /usr/pbi/squidguard-amd64/etc/squidGuard/squidGuard.conf

Not only redirect_program was deprecated, i change for
url_rewrite_program /usr/local/etc/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf

cause that's what i found on Internet. But it doesn't work.
And when I'm trying to launch Squid without squidguard integration there was no problem.
So, i keep integration option blank, uninstall SquidGuard, then reinstall squidguard. And installation did the job and find the right way :

url_rewrite_program /usr/local/bin/squidGuard -c /usr/local/etc/squidGuard/squidGuard.conf

The most straight forward approach would be to backup your current config, install fresh from USB stick and reapply your config afterwards.
Don't forget to backup your config first. ;)

Thank You!
I will give that a try.

The operating system enumerates the ports. It has to do with the PCI bus they are on, etc. Every motherboard is different. You need to look at the MAC addresses and be sure you're talking to the correct port.

Yup.