Nikkon, Not wishing to be hurtful but whenever I ask for help on a forum (quite a lot on pfSense actually) I always report back with my results so others might learn and those who helped me might feel a bit more appreciated. I would hope that you could do the same. I know I would appreciate knowing what you did.

Thanks! I had searched but didn't find that particular post. I also had a different solution. I searched http://www.filewatcher.com for the string: "/ports/i386/packages-8.3-release/Latest/perl.tbz" this found all the mirrors and copies out there. Now, most of these links (like 90%) are dead, however by using a firefox plugin called DownloadThemAll, i told it to start a download of all the sites at once. Then I watched for which sites actually started a download, and i chose the one thar was the fastest and went there. Sure enough that site had a functioning copy if the 8.3 package tree. So i installed that and a Compat6xxx package.

Glad you got it back up and running. pfSense is one amazing piece of effective code  :D

Many thanks…that got me out of package Jail...not sure yet what it was hung on, and so far everything looks fine...will dig some more later when I have time... -ftrain

Thanks a lot!

Yes, just installed the nano update over the vga one. Now I get boot messages but no console. Thanks for the fix.

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