@Finger79 said in Error using the Netgate installer on a new install on an HP t740 thin client PC [Solved - Intel WLAN]: FreeBSD doesn't like HP eMMC storage is outdated Make sure that you check the eMMC health regularly (pfSense: Troubleshooting Disk Lifetime: eMMC). ZFS does write a lot more and there are a few threads here about Netgate devices with eMMC that failed quite early. UFS is better in that regard. How-to for reducing disk writes pfSense: Troubleshooting Disk Writes.

@NOCling said in Separate file system (and pool) to isolate the logs, to not compromise the operating system !: If you want to analyse Firewall Logs in a large environment, you need a external Syslog server. You will not drop hundrets of GB Logs on a Firewall a start parssing thorugh there. I more than agree with You strategically! We using external syllogism node, of course, Thank You! But I am asking particulary about how to isolate the logs on the pfSense node. Let me drop 5 cents about logs aggregation and analysis: You will run a Graylog or other elastic seaech driven stuff to look into. Search just the 1 line in a 40GB dayly log is no fun. Of course, if You using Elasticsearch - even 10Gb / day would need a lot of resources on a separate node. I recommend You using “ClickHouse + Vector.dev + Redash” instead than stack “Elastic Search + FluentD + Kibana” (or Elasticsearch + anything”): at initial point this give You superior (7-10x) better data compression, write optimization and on 1/3-1/4 less hardware resources. Operations like COUNT, SUM, and AVG over billions of rows execute 10-100x faster in ClickHouse compared to Elasticsearch…. And of course, better horizontal scaling with good consistency.

Hmm, so it can't pull stats data from Unbound at that time. It must be very highly loaded. I would try turning up the logging. It will probably create a very large ammount of logs. You could also check the states or run a packet capture to try and see what the traffic spike is. Also check the number of states shown in the monitoring graphs. Does that also spike at the time?

@Gertjan thank you for the advice, yes, 24.11 it is available, seems that it was a hardware issue.

Could be exhausting the RAM perhaps? Anything in the system log after doing that?

I assume you don't have any recent snapshots in Proxmox?

@Hoserman7632 I finally got it to work. My Error, I named the Config file on the USB incorrectly.

@pongli I very much agree as I have stranded there myself with the pfSense+ installer (also online). Very good suggestions, and as much as I would like those options to be available in the installer, I would actually also/rather prefer an offline installer was also made available. PS: @Netgate - while you are at it. PLEASE make DHCPv6 RAW options available in pfSense as well. Right now that is preventing IPv6 setups with some of these ISPs because they require DHCP options in DHCPv6 that you cannot configure in pfSense.

@NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: But after rebooting from setup into the freshly installed instance of PFsense on the NVMe, the IP will be unreachable a While the console output, still attached and active, that a reboot was in progress, the USB drive from which you installed pfSense, was removed, right ? What 'IP' is unreachable ? You mean the LAN interface ? @NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: and will display a setup webpage on other hosts on the network, during the setup. A setup page ? What does it show ? @NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: No matter if i put both the WAN and LAN interface on DHCP, or set a static IP address. Valid for 'everybody' : WAN == dhcpc or DHCP - the DHCP client process will request a lease-WAN-IP for you from somewhere 'upstream'. LAN : set it to static IP address like 1992.168.1.1 /24 or 255.255.255.0 and set up a DHCP - server, this time - a pool from 192.168.1.10 to 192.168.1.200 Done. For experts : dozens of (far) less common setups are possible. Although : dhcp client on LAN ? Never saw that one before. dhcp server in WAN ? same thing. @NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: Now the Protectli V1610 does have a USB-C console port, as well as a HDMI port, and both show the console output for PFsense. But the console cannot be interacted with, and seems to be logging only. When you install pfSense, what version ? their might be a choice to make : Serial console ? or Video+keyboard console ? It's possible that at first the BIOS uses the serial console - and then later on, while booting, pfSense uses the video mode. Or the other way around. @NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: igc4: link state changed to UP igc0: link state changed to UP igc0: link state changed to DOWN What's connected to igc0 ? If it's the LAN - connect this port to a switch, and connect all your LAN devices (PC's AP's printers etc etc etc to this switch). You really want to be sure the LAN 'never' goes down. Same thing for the WAN btw, connect it to an upstream 'other (ISP ?) router or modem etc. @NetworkTechie said in Installing on Protectli V1610: No network after first boot, and read only console.: Or will pfSense CE not run at all on this hardware? edit : Oh, wait, didn't saw the other replies. Sorry if I lost the subject. I never saw a "Protectli " device IRL but they are quiet known. Check their web site again : I'll bet they say that their devices support 'pfSense' (whatever version).

Hmm, I use Proxmox and have some VMs running UEFI. I haven't seen a problem. What issue do you see trying to run the installer?

Yes, I have serial port. Next time I will check report during boot without monitor attached. I am interested to what's going on.

You can set a static DHCP lease but not set static ARP. Normally pfSense would just ARP for the IP and update the MAC in the table but if you mark it static things like this can happen.

Found the solution to disable wireless card from pfsense before installation. https://forum.netgate.com/post/1214869

@stephenw10 said in Update to 2.8.0 always still starts 2.7.2: Do you have an upgrade or boot log from the failing boot? Unfortunately not. I took a different approach yesterday evening: Installed a fresh 2.7.2. (due to the lack of a 2.8.0 ISO), upgraded this without issues and then restored the saved config. Worked without issues. Thanks for coming back to me.

Is it always at the same place in the install? Have you tried using UFS? That usually requires less memory in my experience.

Yeah it definitely could be more obvious. Maybe even a required step in the installer because the installer itself boots to both consoles.