The CF on NanoBSD is kept read only except when the system tries to make changes it switches to RW temporarily.

I haven't seen it fail to switch to rw mode unless there was a problem with the filesystem (faulty CF, fs needs a fsck, etc).

You would need to be on either 1.2.3-RELEASE or 2.0 beta images, you shouldn't use 1.2.3-RC <x>images after the -RELEASE is out.

When in doubt, completely reflash the CF or use a different CF, and don't just do a firmware update.</x>

The next point of stoppage.

This applies to both my laptop and the alix.

Trying to mount nfs root.
nfs root: 10.0.0.1 /usr/local/pfsense
(bfe0 or vr0): link changed to state up

Then it just sits.

Help please…..

Does pfSense/FreeBSD automatically trim SSD drives?  If not is there a process to take care of this.  Maybe a script that can be scheduled via CRON?

Seth

At the time the sizes were chosen about 15 months ago they fit every single card we and users could get our hands on, with room to spare. In the past month, SanDisk shrunk their cards (without changing the model number even, lovely) by 5%, leaving the images now too large. 2.0 shrinks them further.

Thank you for the replies.

I was finally able to install it. It now boots normally.

I set the controller to "Compatible Mode" and created a 4 Gb partition for root. I also used a PATA HDD instead of a SATA HDD.

Thank you

Stefano

i shoul like to do the same
maybe this method can work, but i NEVER try it:
if is possible to do this:
dd if=pfSense-1.2.3-RELEASE-4g-nanobsd.img of=/dev/sdc
for "install" the image version

maybe can be possible to do the reverse
1. plug the memory or the hard-drive to another linux computer (or BSD? i don' t know..i come from linux)
2. use the command: dd if=/dev/sdc of=/your home cmputer home/
note: sdc maybe can be different

someone know if this method can work?
i have also found this http://forum.pfsense.org/index.php/topic,9055.0.html

Your title says "no lan card" but what looks to be the pfSense startup clearly shows two LAN cards: em0 and em1.

You need to let the startup continue, select option 1) Assign Interfaces to specify which will be your LAN and WAN interfaces, then option 2) Set interface(s) IP address to set an IP address on the LAN interface. Then restart and you should be able to connect to the pfSense web GUI and configure VLAN interfaces.

I suggest you leave the LAN interface without VLANs because if you add VLANs to the LAN interface then you will lose connectivity to the GUI when you switch LAN from emx to the VLAN interface and if you made a mistake you will probably have to restart the pfSense system and reconfigure from the console.

@phpzilla:

hello  ;D

i hope i can help you with my small english  ;) i am a pfsense user from germany and i know your problem exactly.
the reason for this boot problem happen in BIOS configuration:

1. open "STANDARD CMOS SETUP"
2. go to "IDE PRIMARY MASTER" or the same in SATA version (SATA PRIMARY MASTER ?) and open it with ENTER
3. switch Access Mode from "AUTO" to "LBA"
4. go back until closing BIOS and answer with "Y" to safe your changes
5. let machine restart and try automatically to start pfsense

my background of this problem:

i install pfsense normally and all is going good
then pfsense will restart and i got this failure like you got. like you i try several ways to clean the failure with no good result.
so i try in bios this and that  ::)

at last i try to change access mode (phoenix bios) from auto to lba and restart the machine AND IT WORKS !
so i hope it will helps you also to try my way !

greets,
phpzilla

Yes this was it! You are awesome. Thank you, and thanks everybody for all of the replies. After making that change everything works great now.

@wallabybob:

It appears you have some process that starts from time to time but doesn't terminate correctly, hence the available process "slots" are gradually used up. It would be useful to know which process and then determine why it isn't terminating correctly.

Please peruse the pfSense system logs looking for error reports from processes.

Do you have any packages installed?

How long does the system stay up before this happens?

Since you system seems to be able to stay up for a day (24 hours?) how about rebooting at the end of the day then in the morning ssh to it give the shell command ps ax and look for duplicate processes (some will be valid), repeat hourly and compare with previous output looking for increasing numbers of duplicate processes.  This won't help it the problem is provoked by a particular "unusual" event which provokes a flurry of creation of processes which don't correctly terminate.

You could also scan the forums for topics discussing maxproc to see if anyone else has seen a similar problem.

Well, I did some more research and poking around on the router, and I've discovered the problem and fixed it. The issue was caused by NAT reflection. I have a few servers running here, and quite a few people on my LAN, all accessing local servers via their domain name, and it seems the sheer number of connections being created was causing NAT reflection to spawn off too many processes for the system to handle. I disabled NAT Reflection and am working on getting split-DNS set up now. Thank for the advice though guys. :)

thanks for answere, but setting LBA on my BIOS do not fix my problem (i have try 5 minutes ago)

That should work fine. I run something similar at home using a Draytek 120 modem and an Atheros mini-pci card.
If you've been using IPFire you'll already be aware of most things to look out for. Like the fact that, unless you put in a firewall rule, your wireless network will be completely isolated from your lan.

Steve

You probably need a VLAN capable switch so you can have a "non-VLAN" connection to your internet modem.

pfSense supports some USB ethernet interfaces so that might be an alternative way of getting a WAN port. However for not much more than the price of 100Mbps capable USB NIC you can probably get a small VLAN capable switch (e.g. Mikrotik RB250GS)

You likely burned the file to the disc instead of burning the image to the disc. It's a common mistake. Google "how to burn an iso"…..

After several days I "solved" the problem:

Either pfsense or the WRAP board is very sensible about long cables (My old router - linksys WRT54GL - worked with the same configuration perfectly).

| telephone socket – 1m cable -- Modem -- 20m cable -- WRAP board

does not work properly. In my case the connection came up, but pfsense was not routing any traffic (do not ask me why).

| telephone socket -- 20m cable -- Modem -- 1m cable -- WRAP board works smoothly.

Just in case someone has the same problem...