Did the upgrade and everything went without a hitch. I actually tested it in vmware first, loaded my config to make an identical setup.  Worked flawlessly there, so I did the upgrade on my home production box. Only thing I had to do was hit SHIFT+F5 in chrome to make the pfsense logo back to the normal size in the upper right corner. All packages updated as well.

That's unrelated to this issue, please start a new thread.

With regards to the download speed. It appears that the new version of firefox slows the download. Using other browsers like chrome and opera does not seem to limit the download so the speed issue can't be on PFSense. The upgrade as seen from the GUI went well, the problem occurred after reboot. The interfaces are not detected and I was just prompted with setting the interfaces dialogs. Anyway, as I was able to easily recover by installing from scratch and restore from backup xml file, everything is back to normal here.

@jimp: If you want to stay on 2.3.x, you must go to System > Update, Update Settings tab and select the security/errata branch, then you can make changes to packages. Otherwise you'll have to update to 2.4 first, which will pick up any updates automatically along the way.

pfsense 2.4.0-RELEASE (amd64) does support UASP. #camcontrol devlist <st1000nm 0011="" pt0d="">at scbus0 target 0 lun 0 (pass0,da0) #camcontrol inquiry da0 pass0: <st1000nm 0011="" pt0d="">Fixed Direct Access SPC-4 SCSI device pass0: Serial Number 000000123BA3 pass0: 400.000MB/s transfers #usbconfig ugen0.1: <0x8086 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: <vendor 0x05e3="" usb2.0="" hub="">at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen0.3: <vendor 0x04d9="" usb="" keyboard="">at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) ugen0.4: <vli manufacture="" string="" vli="" product="">at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (2mA)</vli></vendor></vendor></st1000nm></st1000nm> This is with this USB to SATA device and this HDD. My next mission is to figure out how to test the actual speed it achieves. Edit: build in speed test: #diskinfo -tv /dev/da0p2 /dev/da0p2 512        # sectorsize 996431888384 # mediasize in bytes (928G) 1946156032  # mediasize in sectors 0          # stripesize 544768      # stripeoffset 121142      # Cylinders according to firmware. 255        # Heads according to firmware. 63          # Sectors according to firmware. 000000123BA3 # Disk ident. Seek times: Full stroke:   250 iter in  5.089351 sec =  20.357 msec Half stroke:   250 iter in  3.598658 sec =  14.395 msec Quarter stroke:   500 iter in  5.795468 sec =  11.591 msec Short forward:   400 iter in  1.517583 sec =    3.794 msec Short backward:   400 iter in  2.655790 sec =    6.639 msec Seq outer: 2048 iter in  1.572585 sec =    0.768 msec Seq inner: 2048 iter in  1.577754 sec =    0.770 msec Transfer rates: outside:      102400 kbytes in  0.831469 sec =  123156 kbytes/sec middle:        102400 kbytes in  0.863127 sec =  118638 kbytes/sec inside:        102400 kbytes in  1.456835 sec =    70289 kbytes/sec

Deleted the file, went to the gui saved it, the file showed up, same error. : id uid=2000(xxxx) gid=65534(nobody) groups=65534(nobody),1999(admins)

Thanks very much @Gertjan. I managed to save the file to USB, and to my delight the new installer also offered to pick this up and automatically restored my new 2.4 install.

@kpa: If it's using UEFI you will notice from the console immediately because the console is in graphics mode as opposed to the old VGA text mode that the non-UEFI installation uses. The other thing you can check is to run this from the command prompt (over SSH or from the Diagnostics->Command Prompt menu): $ gpart show =>      40  62533216  ada0  GPT  (30G)         40    409600    1  efi  (200M)     409640      1024    2  freebsd-boot  (512K)     410664      984        - free -  (492K)     411648  4194304    3  freebsd-swap  (2.0G)   4605952  57925632    4  freebsd-zfs  (28G)   62531584      1672        - free -  (836K) The first partition is of type "efi" which gives away that this is an UEFI install, if it's missing you're on the older style of installation. Also, you can tell from the BIOS set up program of your system right away if it's UEFI, it will tell it to you as just about the first thing, very hard to miss. Yeah, I just checked. It's still using MBR so probably BIOS (not UEFI).

This turned out to be freebsd 11.0 issue with kvm. Switching my cpu to be emulated as opteron g3 was a workaround. Here are the bug details incase anyone else runs into the same issue. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213333

Thank you, guys! sds,

I have changed it to "SMTP-Einstellungen testen". Should be correct in the next pfSense release.

@iso70x: @kevindd992002: @iso70x: I have just had to restore a 2.3.4 config onto a fresh 2.4 system (upgrade to 2.4 via GUI failed, long story, file system got corrupted somehow). Doing a fresh install of 2.4, then restoring the 2.3.4 config backup worked perfectly. All packages were installed automatically and everything seems fine. Entire system back up and running very quickly. Restore was done via gui diagnostics menu after the system was up and running with default config btw. For ref, this was done on a PCEngine APU1D4 via a serial cable. I see. Did you reinstall it in UEFI mode? No, standard bios I’m afraid. The APU uses the open source coreboot firmware which I believe is comparable to legacy bios. I see. So we're not UEFI-compatible, bummer :(

With that formatting, just run the pkg info pfSense-base package. You can get close with the contents of /etc/version and /etc/version.buildtime

In other words: You did something unsupported, and to the surprise of nobody, it broke. Don't do that.