Gertjan, you helped me on another thread. Much appreciate. Give your Windows 7 each a "fixed IP" (no DHCP). Now that is an interesting idea. Give each of my computers and end devices a static IP. That would eliminate the need for NAT on the Windows computers and surrender it to pfSense where I think NAT, etc. belongs. Is that what you are saying? Some background on my "present" (definitely will change) setup: WAN through pfSense Network Appliance out single LAN NIC to Cisco SG300 10 port Managed Switch out to each computer and end device. Have 2 more NIC's in the pfSense box (not yet being used).

You could try adding the myk driver but the msk driver is newer and far more likely to work IMHO. Since the msk driver is built into the kernel I have no idea which driver would end up attaching to the card. The PCI Express error is likely not causing any problems as you've found. I have spent some time trying to stop that happening and did succeed eventually but it made no difference at all. Support for MSI in the current msk(4) driver can be buggy. You should add: hw.msk.msi_disable=1 to the file /boot/loader.conf.local.  Create that file if it doesn't exist yet. The symptoms you describe seem far more likely to be a problem with the express card hardware to me. I would guess it's being put into some power saving mode from which it's not recovering correctly. There may be options in either the BIOS or the express-card driver to restrict standby power modes. Steve

If your problem is that the drive is no longer at the logical location it installed to, because you installed on a different machine for example, then enter the new correct location at the mountroot> prompt. Then once the box has booted edit the fstab. Steve

Yes it's still possible for it to be the BIO. Depending on how the BIOS handles booting from USB devices it may not like the multiple slices that exist on NanoBSD

Yes, +1 for Notepad ++, fantastic tool if you're running Windows. The hexedit pluggin is also great  :) Steve

Chralie, Your advice about using single user mode to enable TRIM worked perfectly.  I also disabled advanced poer management in BIOS and now the CAM status error has also disappeared.  Thanks for the assistance, I am all good now.

I also ran into this today. This thread may be helpful to anyone else who gets bitten by the problem: https://forum.pfsense.org/index.php?topic=46725.0 I had already reinstalled by the time I found the thread, though.

pkg list: Cron LightSquid bandwidthd darkstat iperf namp ntop phpsysinfo rate snort squid I'd prefer to NOT re-install Snort… for a variety of reasons, and the only other package that I "need" would be Squid. The others can all be installed fresh. I have no need for old data. Thanks for the confirmation on the XML info.... I may try what you suggested and just nuke it all, and then try a selective restore with just Squid. I'll post back any success or disaster.... -S

Fixed, thanks!

found a really good guide http://www.gooze.eu/howto/pfsense-installation-on-alix-apu-board-howto/starting-firewall-in-console-mode-on-the-apu-boar

I know this is an old thread, but I MUST get control of these fans on Proliant DL360 G3 server (and similar) The fans start off low, and once ANY amount of extra cooling is needed, it goes to 100% and hangs there until rebooted. So many have come so close to getting HPASM running, can we now take a stab at it again? If no, then here is the ONLY solution to this… Load VMware ESXi on these boxes and run the firewall as a single VM on them. Then you can load the VMware ESXi drivers that are supported by HP and since ESXi is FREE and WEB BASED, you should be good to go. The idea is actually a good one now that i think of it, because I would never have to rebuild my PFsense box again! I could just move the VM to any other HW i choose moving forward.

Hello This is sadly still true for 2.1.4. 2.1.4-RELEASE (amd64) built on Fri Jun 20 12:59:50 EDT 2014 FreeBSD 8.3-RELEASE-p16

@pvoigt: @spid: Hi, I have the same board, and also a Kingston 30gb SSD currently running 2.1.3 (Kingston SSDNow mS200 SMS200S3 30GB) Holding off on 2.1.4 until someone confirms 2.1.4 still works with serial console as some have reported problems with the update. I can confirm the serial console is still working with pfSense 2.1.4. I have tested this with an ALIX.2D13. You can find some more details here: https://forum.pfsense.org/index.php?topic=78713.msg429345#msg429345. Regards, Peter Thank you for your feedback, but i'm not running the nanobsd image but the full 64bit memstick installer with serial and after upgrading just now from the auto upgrade web page it all seems fine  8)

When can we expect a 2.1.4 vga release? At the moment, on https://updates.pfsense.org/_updaters/amd64/ I'm seeing again old release dates (02-May-2014) even though version-nanobsd-vga-4g contains the "2.1.4-RELEASE" version string: latest-nanobsd-vga-4g.img.gz                      02-May-2014 21:24            94184435 latest-nanobsd-vga-4g.img.gz.md5                  02-May-2014 21:24                  99 latest-nanobsd-vga-4g.img.gz.sha256                02-May-2014 21:24                134 version-nanobsd-vga-4g                            02-May-2014 21:24                  14 On my pfSense dashboard I still see the message "You are on the latest version." Will we ever be able to upgrade from 2.1.3 to 2.1.4?

Same sentiment from me. It's always better to ask questions than to struggle on alone for fear of saying the wrong thing.  ;) Since you have 4 NICs you can have a 1 WAN and 3 LAN setup (without using VLANs). 3 internal interfaces, 3 separate subnets with whatever firewall rules you choose to put in to filter traffic between them. You might choose to put any servers on one subnet, wireless clients on another and everything else on the last for example. If you want more segregation, firewall rules between each machine for example, you can add further interfaces using VLANs and your switch. Steve