Most likely a hardware fault. Either it can't read the installation media (CD/USB memstick) or it can't write to the SSD/HDD.

Taken to PM to not steal OP's thread.

maybe its this problem: https://forum.pfsense.org/index.php?topic=116223.0

Hmm what exactly are you trying to do? Did you run into a problem? Rigging LCDproc is documented here, half way on the page: https://forum.pfsense.org/index.php?topic=44034.555 Good luck

So, The method you described did not work unfortunately. I tried it a few different ways and i was unsuccessful. I was able to do what I wanted to do by fiddling the outbound rules, by changing to manual outbound NAT rule generation. I matched all the autocreated rules so WAN1/LAN1 and WAN2/LAN2 were paired and there was no cross between the two. Not sure if this is the proper way to do it, but it's working. Thank you! Now to get L2TP working…

Does 2.4 support running off of USB?  Or if not, are you aware of a guide for optimizing USB boot for pfsense? Thanks! EDIT:  Did a full install to USB and it seems to be working.  I put tmp and var in memory, and set it to write only every 6 hours to disk.  Hopefully this will save my USB jump drive. Of note, and this is weird, if if set pfsense to use serial console, it crashes with BTX HALT again.  I had to completely re-install pfsense after I tried that and no amount of various USB jumpdrives with serial memstick written to it will boot.  Any ideas?

Or indeed here: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#X-Core Some of that information is a little outdated now but still mostly relevant. I should point out that all of those boxes are getting old now. The two X700s I have have both stopped booting reliably likely due to bad caps. Steve

Don't think your crash has anything to do with your DNS problem on "ISP3 is connected to the OPT4 interface." I had issues with unable to update or get package before. My problem is was DNS has not route or could not find a route to netgate.com, I'm sure this is your problem as well.

Those are update images not full installation images. You only have one slice, not a full NanoBSD setup. Take the opportunity to instead use the 64-bit serial memstick to put a full install on there, forget NanoBSD.

Also, do NOT burn the GZ.

That wasn't the full crash dump, it didn't have any of the information from inside the textdump archive.

Bootcamp used to support BIOS/MBR only operating systems but as far as I know Apple took that away because of the messy hybrid MBR/GPT partition table system and they now require that the OS installed with bootcamp supports GPT/EFI installations.

Yeah. Now that i've installed it, no problems at all. Thanks guys.

What sort of system are you on? NanoBSD? Full install? What architecture? Are /var and /tmp in a RAM disk?

ZFS supports TRIM natively so it'll do that automatically. There is a knob to disable it if your disk blows up with it on: https://www.freebsd.org/doc/faq/all-about-zfs.html#idp59422952

Yes.