pfSense 2.5.2 install...Can't find /boot/entropy
-
Hi,
I have been using pfSense for quite sometime.
I am attempting to create a backup pfsense box setup the same way the primary firewall is setup.
The primary pfsense box is a Zotac Zbox Nano CI-321 that was probably installed with pfsense 2.3 using legacy boot mode. It is running updated if_re.ko drivers and supports a 1Gbps AT&T fiber internet connection. Tests I've done show that it can hit 980Mbps IN/OUT. The CI-321 is very stable. (realtek NICs)The backup box I have is a Zotac CI-323. I am unable to install 2.5.2 in legacy bios mode.
Many different settings were tried. It dies at Can't find /boot/entropy.
I had an old USB stick of pfsense 2.25 as well as 2.3.2. Both of these versions boot up in legacy BIOS mode without issue and so does FREEDOS. It's only appears to be an issue with 2.5.2. I installed 2.3.2 and then attempted to upgrade to 2.4.X via the GUI, and this fails.I am able to install in UEFI mode and get the system up and running using the if_re.ko nic driver as well. Once configured, this box is not capable of more than 830Mbps.
I've tried many settings and spent alot of time trying to get it to to match the primary firewall.The reason for wanting to legacy bios boot is to try and get the same performance out of the newer, more powerful Zotac CI-323 by mimicing my CI-321 setup (legacy bios). I am unable to find a 2.4 pfsense version to try to load via legacy bios and then upgrade, but am hopeful someone may be able to shed some light on my issue.
Any help is appreciated.
Rich
-
"legacy" means : still supported, but it will vanish.
@technorich said in pfSense 2.5.2 install...Can't find /boot/entropy:
very stable. (realtek NICs)
Keep those candles lit.
There is a thread on this forum that proposes better realtek drivers.
IMHO : don't focus on 980Mbps versus 830Mbps if you have to trade in security == using old software. Go for better hardware (NICs).
-
So...after scouring the web....
I found this:
https://www.reddit.com/r/PFSENSE/comments/9l5fqo/422_upgrade_boots_up_yet_monitor_stuck_at_booting/I proceeded to test, and yes, pfSense 2.5.2 does boot in legacy mode on the Zotax CI-323 to install, you are just unable to see it booting as the console output stops after you see the message can't find file '/boot/entropy'.
The solution was shown in the above link to be:
- hit [esc] during initial pfsense boot.
- At the prompt, type "set kern.vty=sc"
- hit return
- At the prompt, type "boot"
I was able to see the boot and prompts to install once this was completed.
There is likely an issue with a kernel driver, but this solves the problem for now.
Once I installed with the updated realtek driver, I my /boot/loader.conf.local config is as follows:
kern.vty=sc
if_re_load="YES"
if_re_name="/boot/modules/if_re.ko"The system is now booting in legacy mode and I have the updated CI-323 driver 1.96_04 installed as a module.
The system is stable.
For what it's worth, I have used a pfsense Zotac CI-321 for more than 2 years with a recompiled kernel and loaded the updated realtek drivers in the kernel. This box achieves 1Gbps throughput routinely and hasn't been rebooted for months. I run it on AT&T Fiber for basic firewall with NAT.
I will be recompiling the FreeBSD kernel to include the updated realtek drivers for the CI-323 as well with hopes of duplicating the performance I get on the CI-321.
It's a shame we have to do this.
I do agree with you. The Intel NICs are mostly painfree with respect to pfsense functionality.
Realtek needs some love to get working properly.