I presume you have the problem described in http://forum.pfsense.org/index.php/topic,25444.0.html  If so, follow those instructions. When you installed on USB the drive would have been called something like da0 but now that its connected to a SATA controller its called ad6. The startup just needs to be tweaked to look for the root filesystem in the correct place.

There isn't really an easy way to move the configuration from opt1 to WAN if you want to keep the OPT1 rules and make them the new WAN rules (discarding the current WAN rules).

You might have to hand-edit a config backup and replace opt1 with wan in the rule interfaces, but it would be easy to mess something up so be very careful (and keep some clean, unedited backup copies).

It works!
Many thanks, you saved me a lot of time and trouble. :)

@jimp:

Try the fdisk/bsdlabel suggestion here:
http://doc.pfsense.org/index.php/Boot_Troubleshooting

Should also work when booted from a 1.2.2 CD.

If you can wipe/reformat, you might also want to make a small / partition (less than 4GB) and make the rest /usr - obviously that requires a custom install and not a quick/easy install

Jimp, I also tried booting from a 1.2.3 livecd and even the livecd doesn't load with the same error message.  From http://lists.freebsd.org/pipermail/freebsd-stable/2009-December/thread.html#53132 , they seem to be saying its a memory issue with the loader and a possible solution is offered.

Thanks GF ….I seem now to be at the point where Buying the book can only be a good thing....

I have so much to learn and only an old head to do it with  :'(

Managed to get opt's on the lan...next is getting the firewall to allow them.... at times like this I wonder....why do I say computing and stuff is fun???

Soekris Engineering net4801

This compact, low-power, low-cost, advanced communication computer is based on an up to 266 Mhz 586 class processor. It has three 10/100 Mbit ethernet ports, up to 256 Mbyte SDRAM main memory and uses a CompactFlash module for program and data storage. It can be expanded using a MiniPCI type III board and a low-power standard PCI board.

Given those specs, you might be lucky to see in the 20's or so. Less if you are using any kind of VPN, traffic shaping, or other CPU-bound features. That's a pretty underpowered device. You'd get the full speed of that line on something faster like an ALIX 2D3 or a newer Soekris board like a 5501.

@tommyboy180:

If the drives are SATA put the controller into legacy mode.

Depending on the BIOS and controller this is sometimes called IDE mode (or the other mode avaliable that is not AHCI).

There is probably no way to make that card work on pfSense 1.2.3.

pfSense 2.0 is at BETA3 now, it is no longer Alpha, and it's actually fairly stable in many regards (but still needs work in others). Make sure you are using a current snapshot from the last couple days and it should be OK for many things.

There's also nothing stopping you from writing a NanoBSD image to a regular disk of course. So it is still an option, but you won't be able to partition the system to use the whole disk (there's no need to either).

This has turned out to be a problem of BIOS settings.

The LBA option had to be activated in the BIOS options.

Yes this is possible.
Create an allow rule with as source the OPT subnet and as destination the printer IP.

Does your client have the pfSense LAN IP address as the default gateway? (If the pfSense LAN address is assigned by DHCP then its possible it could change so you need t consider how your clients will change their default gateway in sympathy with the pfSense LAN interface IP address. If you use DHCP on your LAN I think things are easier to manage if pfSense is the DHCP server.)

My Old Router is using (192.168.0.1) but I disconnect it in the net system
and..
I also connect the lan cable directly to the 2 PC to try, but no success…

-Is there a color code standard in utp cable on PFsense...

PFsense Guide on PPoE Type Wan... I always get no link-up on WAN interpace..

@jimp:

2.0 is based on what will be FreeBSD 8.1. A major difference from 7.x in many regards.

Ah - that was good news indeed. OK, we'll give it a whirl once it's been released and see how it goes.

Best regards,
Anders C. Madsen

I am using the same server to get started with Pfsense. So far I have not been able to get 1.2.3 loaded, it hangs and the keyboard doesn't function.
I have been able to load the ver 2 June 15 beta but it returns a syntax error when choosing menu items.
If you could let me know if you had similar issues and what changes you made to get it functioning I would appreciate it.
Thanks, Mike ???

Sounds like you are on the right track. I've never used a firebox but I've done the same thing on a Symantec 5420 which is in another thread on here and the wiki. Steps are likely similar. Everything should be detected and you'll see output on the serial console.

Hadn't seen your post

Just one word to thank you.

Guillaume