Changing to 1.2.3 RC3 1G nanobsd causes corruption of CF
-
Hello
I have an Alix 2d3 board with latest bios 0.99h.
I have it fully working without any problems using Pfsense 1.2.2 embedded image.
Yesterday i tried to move at Pfsense 1.2.3 RC3 1G nanobsd.
I did the following steps:1. Moved out 1gb CF from Alix and wrote pfSense-1.2.3-1g-20091006-0229-nanobsd.img on it using physdiskwrite.The process completed successfully.
2. Put the CF again back to Alix and connected a Null cable on its serial port.
3. Powered on Alix and run putty to connect to serial using 9600,8,n,1
4. Boot up process went fine showing me the usual options of Pfsense (although it didn't ask me to reconfigure interfaces,it did it automatically).
5.Changed LAN ip using serial to match my network.
6. Accessed web if and restored the .xml config from 1.2.2
7 At this point using the console i get many messages regarding file system corruption.I reboot alix and after showing the first screen then stops and asks me to locate the kernel file.
I repeated the procedure many times and each time i get the same message.
Now i have moved back to 1.2.2 working without any problems.My question is:
Do i have to change the CF to faster one with better read/write speeds to be able to use nanobsd?
Any suggestions about model i should buy?thank you
-
My guess would be that something in your restored config is causing the issue. I have moved several configs from 1.2 and 1.2.x to 1.2.3rc3nano and haven't come across this. Anything unusual in the setup?
-
I've used many CF cards and restored configs (2GB, 4GB, 1GB, etc…) and have not had any issues.
It could be an indication that your CF is wearing out, but there shouldn't be any problems restoring a 1.2.2 config to any 1.2.3 box.
If you can reproduce this error, try to capture the exact error messages you received. Also, if you try again, use a newer snapshot.
-
Hi again
On 1.2.2 i've configured ipsec vpn,traffic shapping,nat,captive portal.
I'll try with a newer build and i will report back..thank you
