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 ^^

@doktornotor: [image: 335081ba60.jpg] +1 My bet is your subnet is /24..  Right?

Does it stuck after Prompt: OK? You can't type anything and no other error message?

Nice one  8)

@doktornotor: Well, if you want RAID with 2.3.x, use can use gmirror. I missed that option entirely… Now the box is deployed so it's too late to fix. I'll just have to rely on the drive until 2.4 comes out  :)

Did another round of updates this morning. D2500 Atom w/ AMD64 build had no issues. Remaining 3 systems were all D525 i386 builds and all had the issue. All were 2.3.3 to 2.3.3 p1 upgrades through gui. Update: Confirmed occured on AMD 64 Intel Atom D525.

FYI, I don't think 2.3.3-p1 was announced on the email announcement list.

Another piece of info, from the gateway log. This is what is in the log for the most recent incident, they are all the same: Mar 13 14:24:03 dpinger GW_WAN 216.177.49.1: Alarm latency 1595us stddev 1087us loss 22% Mar 13 14:29:22 dpinger GW_WAN 216.177.49.1: sendto error: 50 Mar 13 14:29:22 dpinger GW_WAN 216.177.49.1: sendto error: 50 Mar 13 14:29:23 dpinger GW_WAN 216.177.49.1: sendto error: 50 Mar 13 14:29:23 dpinger GW_WAN 216.177.49.1: sendto error: 50 Mar 13 14:30:22 dpinger GW_WAN 216.177.49.1: Clear latency 2014us stddev 2139us loss 6%

I have an ALIX running 2.3.3-p1 and it still chugs along. It's not perfect, but it runs. The hardware was great for its time, but it's past EOL. If it still operates, keep using it. We intend to support 2.3.x for a year or so after 2.4 releases. You're welcome to keep running 2.3.x as long as you want on there. NanoBSD upgrades have always worked fine in our testing, and from our customers that have reported issues, most of them were due to faulty CF and the others were connectivity related or in very rare cases, a configuration issue preventing DNS from working during the upgrade. Even new cards can be faulty, it's the luck of the draw there. We can't fix or code around broken disks. Sandisk is usually reliable and fast, at least the 200X ones I typically use. You have to pay a little more for them but they are worth it: SanDisk SDCFH-004G. But even the best CF is still CF.