Hmm, well that's interesting. Sounds like a BIOS quirk. Persistence FTW. Steve

Hi Jim We have posted nearly the same time our reply. Thank you for the hint, that is what i was looking for. However, my personal believe is, of course this is a solution but probably not the smartest and sexiest. Maybe there is a explicit 'post upgrade script'-possibility for the future. Cheers Tom

There is an issue with 2.3.4 that prevents it seeing the updates. That was when we went to two branches and it can get confusing and start looking at 2.4.X where no 32bit updates exist. Try running the following command at the CLI or via Diag > Command Prompt: pkg-static clean -ya; pkg-static install -yf pkg pfSense-repo pfSense-upgrade That should force it to use the correct update package and see 2.3.5_2. Steve

Hi @Derelict, Looks like these patches did it. I manually commented out the line in /tmp/rules.debug and then applied the patches, rebooted and voila, internet came back online. I will monitor it closely to see it it has any adverse. Thanks for all your help MM

@stephenw10 said in Installing 2.4.3 in mini pc using flash disk into the flash disk in UEFI mode: For reference if you have enough RAM to use it you can choose the guided ZFS install from the menu and then select the GPT(UEFI) or GPT(BIOS+UEFI) partition scheme to get a bootable drive directly. Steve Hi @stephenw10, how much minimal RAM to use ZFS? I only install 2GB RAM in the only slot on this mini PC. Right now I only use space "7% of 14GiB - ufs" Why the option of UEFI and BIOS+UEFI only exist in ZFS install? Isn't it a little overkill to use ZFS for a router that meant to be small and fast?

When you write the image to a USB stick it uses 1 write cycle for each bit within the image size. Unless your drive is already 99% dead it should make practically no difference. I have seen some odd behaviour with those Sandisk devices that appear as two drives by default though. I avoid them where possible. Steve

What kpa said ^. If you're using SWAP at all that's almost always a sign something is misconfigured or you're trying to do too much with the RAM you have. With 8GB I would not expect to see any issues with anything unless you run Squid and Snort and don't limit their use. Steve

@aswin_hadinata said in [[ASK] Install pfsense on Harddisk SSDintended to buy ordinary SATA HDD but got doubt. please advice Pfsense is the perfect application for a solid state drive. Heck I spent usd$15 for a 16gig and it's not even 30% full after install. What's there to think about.

Hmm, interesting. Thanks for the update. Steve

@KOM: Perhaps a clue, but I noticed last week that I could no longer log into my vSphere web ui in Firefox.  It still worked in Chrome, but FF told me that there was a problem with the cert auth and no exception could be created. Doesn't work on Linux or Windows with Chrome and Firefox on both platforms.

Yeah, was kind of late yesterday, but I want to post the solution. As Steve points out, if you install using automated ZFS(last option) you can configure swap size, which drive and which partition scheme. When selecting GPT(UEFI) an UEFI-only box(or in my case, MBR using CF and a required UEFI using a sata ssd) will boot.

Thanks. Those files existed, though several were 0 bytes. The update wiped all my settings for various packages also: pfBlockerNG, Snort, Squid. I decided to do a clean install of V2.4.2 to my router, then did an upgrade to 2.4.3.1 via the GUI without issue. Now, I'm updating my config and various packages. So far, so good

A lot more info needed.  ;) What version did you upgrade from? What hardware are you running on? Do you see any errors/collisions reported in Status > Interfaces? Steve

How long did you wait after the upgrade rebooted? What hardware are you running on? On some older hardware or slow boot media the webgui can start significantly before the upgrade has completed. If you login at that point it may report the old version still. If you are connected to the console you will see the boot has not completed, the boot menu has not been shown yet. What error is shown on the CLI when you try to upgrade again? Steve

OK, I got it to update from 2.3.4 to 2.3.5, but now it doesn't show any more updates after that. I've tried switching to all the other branches, & they all say it's up-to-date. Could this have to do with the FreeBSD 11 issue? Or is there another way I could get it to update to 2.4.3?  

Same thing happened to me.  It failed on the first attempt.  After it rebooted I tried again.  It went through the updates, rebooted and then it's all ok.  Odd. Darkk

On comparison, there are differences in the XML sections.  The old version (8.0) has sysctl, pptpd, dnsmasq, bridge, and l7shaper that the new version (17.3) doesn't.  The new version (17.3) has dhcpdv6, unbound, notifications, mailreports, and dyndnses that the old version (8.0) doesn't.  I know some have to do with package differences but I wonder if some of the core changes scrambles the config on an import.  I'm reinstalling and manually moving the relevant portions of the XML over.  I'll see how that goes.

I managed to 'resolve' the issue, by restoring the configuration, do a fresh install and restore the old config. This are the steps I have followed: 1. Download pfSense-CE-memstick-serial-2.4.3-RELEASE-amd64.img.gz 2. Unzip and write to USB stick e.g. with a tool like rufus 3. Boot APU board with USB stick 4. Get a prompt using the rescue shell 5. Plugin an addition USB stick (fat32 preformated) – needed as the installer image lets you mount /dev/da1 only read-only 6. Mount partitions (mount /dev/ada0s1a /mnt && mount -t msdosfs /dev/da2s1 /tmp/usbstick) 7. Copy configuration (cp -Rv /mnt/cf/conf /tmp/usbstick) 9. Do a fresh install and assign interfaces 10. Restore configuration via webinterface 11. Check serial settings...