There isn't a cleanup guide. It shouldn't be necessary.

Though apparently that case wasn't handled by the upgrade code.

You could install the cron package and remove the old job that way.

I opened a ticket for the upgrade bug:
http://redmine.pfsense.org/issues/1905

@Rural:

(…)
That was the problem. Fixed that.
(...)

Nice to hear. :)

@LostInIgnorance:

Some of the old code that worked with IE may have remained in the firewall or in your browser history, but on a fresh install, that all would be deleted.

Thank You that helps clear this up.

I'm seeing the same problem with the final release under VirtualBox. It doesn't happen with the x86 version, so trying that may help you too.

Later, when I have time, I'll try to troubleshoot the problem.

Thanks Havoc

THANKS,

I think I can sort it now!

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.