Pfsense startup problem
-
I have made quite a few attempts to get pfsense starting from a usb-flash. My latest try is 2.1 BETA
A: Running pfSense-LiveCD-2.1-BETA1-i386-20121226-2125 and Installing to flash memory
B: pfSense-memstick-2.1-BETA1-i386-20121226-2125 and using unetbootin to transfer the image to the USB-flash
In both cases the diskless computer boots from the USB-flash and in both cases it runs until "mountroot>". Available devices are acd0 and fd0 but I cannot get the system to accept any of them.
I can get the system to work from the Live CDPlease help
-
Have you read and acted on http://doc.pfsense.org/index.php/Boot_Troubleshooting
-
Have you reproduced your issue on a separate box to ensure it is not something in your hardware?
-
Have you read and acted on http://doc.pfsense.org/index.php/Boot_Troubleshooting
I have but it didn't help
-
Have you reproduced your issue on a separate box to ensure it is not something in your hardware?
No! The box itself is working when running from Live CD. The startup-problem only appears when i boot from USB-flash
-
Have you reproduced your issue on a separate box to ensure it is not something in your hardware?
No! The box itself is working when running from Live CD. The startup-problem only appears when i boot from USB-flash
My mistake :-(
I missed overlooked the option of pressing 3 in the menu. When I do, pfSense boots perfectly from the USB./AnWi
-
Hi
I am not sure why the topic changed, any suggestion on my issue? -
any suggestion on my issue?
How about providing the additional information requested before AnWi hijacked the thread.
-
any suggestion on my issue?
How about providing the additional information requested before AnWi hijacked the thread.
Hi:
As I mentioned earlier, the issue happens about 1-2 times every 5 startups. Everything looks normal on the pfsense box, got WAN IP correctly. Computers under the pfsense LAN does not get IP addresses.
Is there any logs I should be collecting? I would do that the next time I encounter. As this happens kind of random, it may take a bit of time.
-
Well it could be a number of things causing this you have to gather as much info as possible when it doesn't come up correctly to narrow it down. For example it could be:
1. The NIC is not attaching to the driver correctly. Seems unlikely since you said earlier you could see it had a 192.168.1.1 address. If you provide the output of ifconfig that will confirm that.2. The firewall is blocking traffic. That should never happen if you are running a DHCP server but sometimes things get weird. You would see that in the firewall log however.
3. The DHCP has stopped. If the DHCP server crashed out you should see something in the system log.
4. Something else on your LAN is running a DHCP server that is grabbing requests. This happens quite often.
Steve