The .img file is a disk image that is written to the USB memstick using dd, win32disk imager, rufus, etc. The filesystem format is UFS which few other operating systems can read, aside from FreeBSD. The fact that you can't see any files on there does not mean there is a problem. Try to boot from the USB memstick. If the hardware supports booting from USB and FreeBSD will run on that hardware, then it should work. There was at least one other person who managed to get it to work on similar hardware, but that might be a different model: https://forum.pfsense.org/index.php?topic=116910.0

That went into the right direction. I had defined the LDAP server by FQDN. But during testing, there was also a problem with DNS lookups, so the server was not found. Instead defining it by IP address solved the problem. There had been some more challenges to take (WAN connections didn't come up right away…), but the process of exchanging hardware finally worked. What a relief!

Thanks for this guide it really helped. I did run into a snag though on 2.3.3: If you follow the posted guide pkg install icu will install icu-58.2,1. This will then throw an error when you try to run murmurd. Unable to load library icui18n "Cannot load library icui18n: (Shared object "icui18n" not found, required by "murmurd")" To resolve this I issued: pkg remove icu Then added the icu package 55 as per rest of guide: pkg add http://pkg.freebsd.org/FreeBSD:10:i386/release_3/All/icu-55.1.txz I also had to re-add all the QT dependancies as listed above because the removal of icu also removed QT. Of course if you add icu-55 first there is no need to remove anything and the guide is still good. Hope this saves someone some time. I love Mumble and wish it could be a native package  :P ***For the observant; I added this to an i386 architecture. So be careful when copy-pasting!

Follow on from the above. By adjusting the "start date" on the rrd_summary package I've found that the large data "error" occurs all on one day - the day I was assembling the pc with the new LAN card.  Starting the present month after that date shows sensible figures. Most probably I've caused some file or data corruption, perhaps with the backup file which at one point I restored.  My assumption now is that the display will self correct at the month end - and the "problem" is self inflicted.  Oops. J

YES! That was it. Thanks so much!

Install an older version that will boot on that box (e.g. 2.1.x) and then upgrade.

For what it's worth, the upgrade to 2.3.3 on my 2440 also broke as the OP described.  Install seemed to go fine through the web admin, but the box never came back up.  Tried power cycling a couple times and eventually after hitting the reset button the internet came back on my computers, however I could not access the web admin and was getting the 403 Forbidden.  I was able to login via SSH and run: pkg update -f pkg upgrade -f That seems to have me back up and running.  That was pretty scary for a while there!  Thanks for the helpful thread.

So I completed the update this morning using the same steps as in the main update thread: Restart via GUI Verified in GUI pfSense stuck on FreeBSD 10.3-RELEASE-p16 Logged into SSH, used 13) Update from console After reboot, GUI shows FreeBSD 10.3-RELEASE-p17 and all systems are go.

Excellent news! Thanks.

I am able to login with the password now on console but problem is after Reset to factory defaults Boot is strucked at Starting webConfigurator…done. Configuring CRON... WebUI still not working Parse error: syntax error, unexpected end of file, expecting ']' in /usr/local/www/index.php on line 623 SSH not working Enter an option: Mar 17 18:59:51 php-fpm[289]: /sshd: The command '/usr/sbin/sshd' returned exit code '1', the output was 'Undefined symbol "compat13" referenced from COPY relocation in /usr/sbin/sshd' Mar 17 18:59:51 php-fpm[289]: /sshd: New alert found: SSHD failed to start. default version : pfSense 2.3.1-RELEASE-p1 ??

@doktornotor: NanoBSD is dead. You really should do a proper full install with the SSD. Agreed, support is being phased out for nanoBSD. You'll save yourself a lot of ass pain by just doing a regular install to a cheap SSD with the current Release version. Alternatively, you can still use your USB drive (I have a USB install) using the 2.4.0 BETA install with ZFS. Either of the above two options are straight forward, supported installs that will continue to be supported into the future, that will almost certainly work for you out of the box. I doubt there is any legitimate reason that you HAVE to use nanoBSD, and if there is you'll have to work out a solution sooner or later as it's days are numbered.

thank you , the 2.3.3_1 realy solved the problem ,  so thank you ^^