I was looking at creating a home firewall running pfSense (as I could not get IPCop to boot properly on my hardware). Doing a little research, however, I have some concerns with installing it onto an SSD.

I would like to use an SSD as the drive for this home firewall machine for the reduced noise level and less mechanical/moving parts (it's also a fanless build, so essentially there are none!). With normal firewall logging enabled there will be too many writes to the SSD and it will reduce the life of the drive significantly, which is not something I wish to do.

I looked through some various other forums and read somewhere that the pfSense NanoBSD install is perfect for CF or SSD installs as it essentially removes disk writes (with the exception of needed writes) and has everything run from RAM.

Has anyone used pfSense NanoBSD on an SSD, and would it be a viable option? Would this build still reduce the life factor of my SSD greatly?

Also, if this is a viable option, is there a way I can get the .gz file to write to a USB drive and boot/install it from that to the SSD (I have no disk drive on this machine).

Finally, if this installation does work, is there a way to get logging to store to a separate drive if I wanted to (such as a USB attached 320GB WD MyPassport drive)?

  • 3
    considering that many users use SSDs for their OS, with thousands of browser cache writes daily, I think pfSense would not overwhelm an SSD. Use ext2 to eliminate journaling. Personally I use a CF for my pfSense
    – bsd
    Commented Apr 19, 2012 at 9:45
  • @bdowning Thank you for the input. I was just concerned as numerous places I was reading that people had their SSD's crash within 2 -3 months with a pfSense install writing to it. For a CF to work with my build I would need a SATA adapter as well. Do you have a recommended CF for this? Also, do you know a good tutorial/introduction to ext2 (or ext4) and how to utilize that? Thank you for the feedback!
    – SirCobalt
    Commented Apr 19, 2012 at 15:25
  • 1
    My pfSense box is an Alix2D2. I'm using a 1GB Lexar "professional", stolen from my Nikon, nano-bsd-1gb install image. CF is 5 YO, so far no troubles but this is for home use, very low volume.
    – bsd
    Commented Apr 19, 2012 at 20:03
  • @bdowning Thanks for the information! That's a neat mini-board. The one I am using does not have built in CF support. So when you installed your for your home FW you used the 'nanoBSD' install? Do you know a link to a good source for setting up an ext2 file system? Everything I have found gives details on ext history, but nothing on really setting it up.
    – SirCobalt
    Commented Apr 20, 2012 at 17:26
  • re:ext2, I wasn't really thinking about this, just an off the cuff comment, with my head stuck in the linux cloud, forgetting that pfsense is based on bsd. I don't know enough about bsd file system types to make an intelligent suggestion.
    – bsd
    Commented Apr 20, 2012 at 19:59

2 Answers 2


Distros like nanoBSD, bowlfish and others use memory file systems for things like /etc, var, /tmp and others so they do not write to the flash storage. Obviousy /tmp an be safely lost without preventing reboot to a working system, and for the others the OS variant manages writing what's in the MFS mounts to the persistent storage. Bowlfish does this through storing /var & /etc as actual partitions and then copying to the MFS at boot-up, shutdown and regular intervals. FreeNAS (which uses NanoBSD) has a a /data partition on which it stores some sqlite databases from which it rebuilds /etc at boot and to which it saves any changes you make via the web UI.

However, CF and SD cards have come a long, long way in the last 10 years and while the write limit still exists, it is so high these days that it's no longer much of a factor, which is why SSD hard drives are now both popular and common.

Honestly, these days I'd worry more about the heads in your hard drisk drive crashing on the platters and it dying that way than the write limit making a flash drive eventually unusable.


We have been using pfSense on SSD for past 4 years. We have not had any problems whatsoever. We are not using the pfSense NanoBSD.

The modern SSD's are fairly well designed to handle the wear and tear induced by logging. Probably the SSD will outlast the computer it has been installed in. The trick is buy a 128-250GB SSD though pfSense does not need that kind of space and allow plenty of reserved space.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .