Replacing hard drive with CF card
-
See http://doc.pfsense.org/index.php/Installing_pfSense for how to flash the image.
-
@jan:
my question is kinda newbie, i just need to clarify this thing which has been bugging me for some time so here it goes, i'm planning to purchase a CF card to replace the hard drive install of pfsense so my question is when i install pfsense on the new CF card which image do i need, the live cd install which i used in my hard drive? or the embedded image? and would a 512 MB CF Card do the job? does a CF card install need a swap space?
TIA
I am doing the same exact thing of using a 512MB CF Card with IDE-CF card reader. i have gotten all kinds of error messages during the install. Is there any tricks that can make this less painful?
-
Use the embedded image. If you use a full install your card will wear out sooner or later. If you still have problems try setting your bios to lba for the cf-drive and set it to the lowest available PIO mode. Disable UDMA and so on. Most cf-cards/readers don't support it.
-
Just little curious
If I install full version of pfsense on a CF card, how long those it take until my card get wear out ?
-
Depends on you card and what additional packages you install. We never have measures write cycles of a full install. We just tried to lower those for embedded installations by mounting the volume readonly and using memory for frequently written logs and such.
-
Mine is not dead yet. So even if you need to replace it on a yearly basis that's not really a financial back breaker.
-
databeestje,
Have you used the full version of pfsense on a CF card for one year without getting any problem ?
If so, that cool.
In Sweden, you can buy a SANDISK COMPACTFLASH 512MB for 21$
So, it's very cheap and I don't mind to use it only for one year.I thought that If you use pfsense non embedded with CF card, you would destroy the card in one month or two.
-
I'm using my cfcards extensively for testing, some with full install and even if not they are sometimes rewritten several times a day. I have nevver had any issues with one of them and I'm torturing them for more than 2 years now like this. You probably should always have a backed up config.xml handy and in a production environment this is a no go but it looks like cfcards nowadays can handle quite a lot of write cycles.
-
I'm also thinking of using CF card as a replacement for my usual hard disk installations of pfsense.
Is it more reliable than hard disk installs? What hardware do i need to connect a CF card as a bootable medium for my firewall?
I encounter frequent software crashes of my pfsense firewalls, even all hardware are new.
Thank you very much. -
Use an IDE-CF-adaptor like the ones pc-engines sell: http://pcengines.ch/cflash.htm
The cfcard will then be seen by the bios like a hdd. It's of course not hotplugable. -
Thanks, Hoba.
My problem is that there is no locally available CF to IDE adapter here in the Philippines. :o
Is it possible to use a USB drive (via the USB port) as a replacement for the hard drive, and would it be reliable enough?
Thanks again. -
Not sure, mainly depends on your boards bios and so on. USB support is not the greatest in freebsd currently. Haven't tried that yet.
-
Firstly, pfsense ROCKS!
Would you recommend that i replace my hard-disk-installed pfsense with the one of an embedded version install using a compact flash card as the hard disk (via CF to IDE adapter)?
I'm using pfsense firewalls (all hd installs) on all of my 5 internet cafe's here in the Philippines.
What i observed is that hd installs are very prone to software corruption due to power outtage, incorrect shutdown, or sometimes even a normal power cycle corrupts the pfsense software. We usually turns off the firewall at night.
All hardware that i am using is relatively new and without any defects since i considers pfsense as a critical part of my cafe operation.
I don't use any packages, only basic config of traffic shaping and load balancer. Traffic is only max of 2 mbps download and 1 mbps upload.
Would my systems be more corruption-free using CF since it would be loaded as read only?
Is there a way to make my hd installs load as read only after configuring everything so as to avoid the corruption?
Thanks in advance, still a newbie here. -
Also you can setup pfsense with "Disk-on-module". Not very fast, but stable, and writecycles are not a problem.
Greetings
heiko -
cheeky,
Is there a way to make my hd installs load as read
only after configuring everything so as to avoid the corruption?I think so, I have test what you ask with 1.0.1-SNAPSHOT-03-08-2007
in a couple of days without any problem.Maybe Hoba can also confirm this, he is the expert here.
this is what I did :
SSH to your router and choose option 8 and write following command :
echo embedded > /etc/platform
/etc/rc.conf_mount_ro
exitnow, choose option 5 for rebooting your router.
after this your router will act exactly like a embeded version. -
Any procedure on how to do that disk-on-module? Or the command suggested by nima.m is enough already to make my pfsense corruption-free?
Thanks again. -
The Disk-on-module is to place directly to the IDE-Port. Then you run the installation from the LiveCD. That´s it. A DOM with 4 GB costs for example 60 €/ 80 $.
-
You can also try a CF microdrive which has physical moving parts and a platter so they should last longer than your traditional CF card. A 4gb microdrive runs about $50 probably and fits in the same CF type II slot. Of course older CF readers have issues reading these drives from my experience but if its something recent, you should be fine.
-
You might mention that the Seagate 4G and 8G microdrives (the ones which cost $50 or less) DON'T WORK in CF-to-IDE adapters under FreeBSD 6.x. Not sure how this slipped your mind since you are the one who discovered it and submitted the bug report to FreeBSD! (Thank you for doing that, by the way.)
-
How do you install? I Followed the fullinstall on wrap guide using wmware but all I get is
ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad0: FAILURE - READ_DMA timed out LBA=0 ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=1 ad0: FAILURE - READ_DMA timed out LBA=1 ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad0: FAILURE - READ_DMA timed out LBA=0 ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 ad0: FAILURE - READ_DMA timed out LBA=0 Trying to mount root from ufs:/dev/da0s1a Manual root filesystem specification: <fstype>:<device> Mount <device> using filesystem <fstype> eg. ufs:da0s1a ? List valid disk boot devices <empty line=""> Abort manual input mountroot></empty></fstype></device></device></fstype>
I'm not realy sure what I did wrong. The hardware I use is a routerboard 200 from www.routerboard.com