Ok, clear now. Thanks a lot for your prompt answer !

I have found some problems upgrading from RC3 to 2.0 RELEASE too. NRPEv2 configuration is lost (this happened upgrading from rc1 to rc3 too) Squidguard in transparent mode stops working, now i only see on access logs  TCP_DENIED/400 2260 GET NONE:// - NONE/- text/html and a invalid petition error on browser. Seems something isnt working properly on http traffic redirection. Thanks and best regards.

Is the same one CF card ,It can bootup in the IBM X306m ,But can't boot in the X305

Of course, there is plenty of documentation and even FAQ articles.

Had the same issue on a install on a Dell Optiplex 745 with a Pro/1000 MT Dual PCIe card.  Never installed pfSense on a 745 before and was getting stuck at 38% with memstick and CD.  Read up that this was an issue with Dell R210s. http://forum.pfsense.org/index.php?topic=31907.0 Disabled multicore, and the onboard NIC, enabled virtualization and the install went through smoothly.  I figured it was just a Dell issue and surprised you also saw this on your Fujitsu.

OK, so I figured this one out a while back and haven't made it back on the forums 'till now. This was caused by the fact that pfSense tried to assign the interfaces itself after I made so many changes, and ended up putting Opt2 - Opt5 (renamed as VLAN10, VLAN20, VLAN30, and VLAN40) all on em1. This was resolved by me dropping down the interface assignment from em1 and putting it on LAGG0. Easy fix. Very nice. Everything is working now, plus I have my AP on a VLAN20 port on the switch now instead of its own interface, which was kind of the point of giving this a try. Works well.

ok found a fix. for some unknown reason pfsense was trying to boot from a non existant partition, the installer somehow got the wrong name. I forced it to the correct by: Trying to mount root from ufs:/dev/ad2s1a Manual root filesystem specification:   <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:da0s1a   ?                  List valid disk boot devices   <empty line="">Abort manual input mountroot> ? List of GEOM managed disk devices:   ufsid/4e7a0c1bbf9d728f ad0s1c ad0s1b ad0s1a ad0s1 ad0 Manual root filesystem specification:   <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:da0s1a   ?                  List valid disk boot devices   <empty line="">Abort manual input mountroot> ufs:/dev/ad0s1a Trying to mount root from ufs:/dev/ad0s1a ___ / f / p _/ Sense _/      __/ Welcome to pfSense 1.2.3-RELEASE… Mounting filesystems... done. Creating symlinks......done. Launching the init system... done. Initializing.................. done. Starting device manager (devd)...done. Loading configuration......done. Network interface mismatch -- Running interface assignment option. Valid interfaces are: fxp0    ff:ff:ff:ff:ff:ff fxp1    ff:ff:ff:ff:ff:ff fxp2    ff:ff:ff:ff:ff:ff Do you want to set up VLANs first? If you are not going to use VLANs, So if anyone else has this error its nothing you are doing it is a pfsense bug! All thats left is to correct fstab and its ok.</empty></fstype></device></device></fstype></empty></fstype></device></device></fstype>

wallabybob and ptt, Thanks to you both for helping find the problem. I dropped the dot, restored the config and upgraded to 2.0 without a problem. It's been an interesting month  - pfSense 2.0 and ESXi 5.0.  Sincere thanks and congratulations to the devs for the former. Cheers, biggsy

Updating from default install to default install. almost the same as clean install for me. my sucessfull upgrades(1.2.3 and 2.0RC) are: remove packages download full update to pfSense disk upgrade via console As you do not have local console I've changed this to ssh. give a try, it will work.

@zombie: The sha256sum is correct. However the firmware upgrade page says the file must be a 'tgz'. if sha256sum is ok, rename the file.

I have been recycling my config file since BETA 5 with no issues.  I would do fresh VM builds every so often in between updates. From my experience, it has been solid for restores from build to build. I have a basic config with nothing fancy on the routing and networking side.  Just some nat's, aliases, rules and some settings, but way too much to redo from build to build. So for peace of mind and if you want to start fresh, do a complete new build and then make a backup.

Yes, I found that out the [really not so] hard way. But WOO-HOO! the serial connection is up. Unfortunately, I cannot with any degree of surety, point to the change that made it possible. My suspicion is that either my PC's serial port (which I added on and plugged into the appropriate port on the motherboad), or the null modem cable, was faulty. For when I went out and picked up a USB to Serial adapter, and new null modem cable… it worked, both with Minicom, and GTKTerm. I have what looks to be one last hurdle to overcome, but since it's a different issue, I'll start a new thread.

I am also running behind an Untangle server. Thanks you very much!! Case closed  :)

OK - on permanently it is then!

It always had it, just not the automatic way. :-)

i used a SD to IDE adaptor for a bit, just a cheap one from ebay, crapped out after about 6 months though.

Didnt have to…. tail /var/log/system.log show me the progress... I just had a lot of pkgs :) All done. Thanks.