Using bootable linux on USB, did wiping all the partitions on DOM, crate one new FAT32  partition, but result is the same error. Accessing logs, there is line at the end of logs: Executing '/sbin/bsdlabel -B -r -w ada0s1 auto' bsdlabel: /dev/ada0s1 read: Invalid argument Did not try with Ultimate Boot CD, but effect should be the same.

The same issue. Some one resolve it? pfSense-CE-2.3.3-RELEASE-4g-i386-nanobsd

No there is no home router that would run pfsense.. Your talking like something you go the local computer store and pick up.. Like linksys, belkin, dlink, etc..

Oh nice, i tought that isn´t included. Then i gonna try this. THank you.

Missing that function means that a file may be missing or corrupted on the disk and if one is, more probably are. It's possible the disk has a problem, or it may be a problem with the filesystem. Download the serial memstick installer and reinstall 2.3.3 to the mSATA disk. If you still have trouble after that, consider replacing the mSATA.

Any updates?

Hi Heliop, it is a virtual machine like yours made with the newest ova… but that there is no swap suprises me. I'm going to test it out what happens, i have squid, guard, snort and blocker. Think that will be enough  ;)

@gnhb: You're likely logged in as a non-admin user and the user wasn't given privileges to view any page in the GUI. If you're logged in as admin, then the permissions are screwed up. On second thought, I wasn't really admin as I believed I was…created user and didn't add to admin group. It was easier to do a factory reset than fix permission.

Really, i have the same question. I have WatchGuard e750x and want install pfsence on it. But i have a troubles with serial connection. (Maybe my cable is broken or serial port -i don't know ) So, after i flashed pfSense-CE-2.3.3-RELEASE-4g-i386-nanobsd.img to my CF card - can i put in in device - stated it and connect to PFsence with SSH ?

I would still revert to the built-in resolver/forwarder just to be safe. The update/upgrade isn't terribly smart about handling situations where the system's DNS resolution depends on a package like BIND that is being updated as part of the update/upgrade.

Wow. Sorry, man. it looks like I hit modify there instead of reply. Ugh. Glad you got it sorted out though.

No direct cause has yet been found as far as I know. Obviously we would like to resolve it as soon as possible. https://redmine.pfsense.org/issues/4310 Steve

Thank you!  That got me past the hump I was bumping into.

Forcing a cache refresh in the browser (ctrl+F5, shift reload) is a good idea when you see this sort of thing as well. The browser probably cached the old logo if it changed in-place.

Not to mention the fact that a device with NVMe drive could always be repurposed for a more intensive task without replacing hardware. I don't see any issues with it. I have the same drive and I also get the same error. I just choose "Skip" and it continues with the installation properly.