For the archives here, the current (updated) memstick image in my directory on files.pfsense.org should be working better now.

http://doc.pfsense.org/index.php/Upgrade_Guide#Changing_architecture_.2832_bit_to_64_bit_or_vice_versa.29_during_upgrade

It was a great learning experience, I have a solid understanding of troubleshooting pfSense installs and I know a bit more about partitioning for BSD!  I got it working last night routing one wireless connection into another, which was one of the tasks I wanted to try with this machine so I'm happy  :)

Jimp, Yeah, up for 19 days now on 2.0-Release with no issues.  So reverting back to 2.0 (with no config changes at all) fixed whatever my issue was.  I suspect it might just be that combination of hardware since I have 5 other boxen running 2.0.1 with no problems. If you'd like to investigate just tell me what you need.  I can reload that box with 2.0.1 whenever. Thanks.

I have the exact same problem. Removing /usr/local/pkg/squidguard* followed by a reboot get things back to normal. Thanks for the tip!

Checked in a fix for this one today, too https://github.com/bsdperimeter/pfsense/commit/b357f0a66de848ce7b840538e5499b1d2c989833

Ok, thanks! Those must have been from quite an old version of pfSense. Sure. I'm using pfSense for the last 5 years. I did many upgrades !!! I didn't edit manually any alias. Regards, Josep Pujadas

This did the trick http://forum.pfsense.org/index.php/topic,32017.15.html

The memstick image is the same as the livecd – it's an installer and test platform, it's not meant to be run indefinitely. It does not store the config on the drive.

I would not run on the Dev kernel in production. Aside from being slower due to increased debugging, it is also more likely to panic if it gets into a situation it doesn't like for any touchy little reason.

Thanks both.

Check this: http://www.pfsense.org/index.php?option=com_content&task=view&id=43&Itemid=44

What would I have done without you  :) it worked…. much appreciated.. still dont know why using the web manual update hangs.. have a good day

@nexusN: @cmb: It means what it says, it can't write to /var/tmp because there is no space available on the device. That's either because there is no space (something overrunning the disk? would have to be a package) or at times a dying disk will produce that output. Check "df -h" at the console when it's happening. Sadly I don't have another harddisk to test it out; They are too expensive now such that I must use an old one. While I do think it works quite well as I have been using it to store and download new data frequently. Maybe I should check it anyway. Thanks for your advice. Thanks for the check advice! I am sorry for my irresponsible claim on the software, on WD harddisk check the harddisk is found to have bad sector, and it cannot even pass a quick test. Now I have switched to a 2.5" harddisk and hopefully I won't see the same error on the page.

Thats exactly what solved the problem! (Creating a small boot-partition) Thanks a lot for this excellent help!!!

having the same problem

Diag>Backup/restore, Config history tab

So, you are saying to edit the xml file, and correct the few differences in hardware before importing the "restore" into the new box. That makes sense. Thanks.

That means it's not compatible with FreeBSD 8.1 amd64 probably because of a driver bug of some sort. You may want to try a stock FreeBSD 9.0 release amd64 version and if you still have problems, report them upstream to FreeBSD. That's outside of our control.

Wow, message to self: never try becoming a sysadmin. I've setup pfsense for remote logging (easy), i've installed and configured Syslog Watcher on Windows (also easy), then it took me 3 days to figure out Windows Firewall was blocking the UDP packets on port 514. Anyway, it's remote logging now. We'll see what happens :) Thanks for the hint.