I'm saying that, barring any problems unrelated to the 7551, any upgrade will work on it. In other words: If the upgrade failed, it wasn't because it was run on a 7551. The only specific failure that affects the 7551 is a fresh installation of 2.4.x, which can be worked around as mentioned in the wiki. So if your upgrade failed, post about that instead with more detail because it doesn't have anything to do with the hardware.

OK, Thanks for you insight!!  8)

I came upon that very thread. I left it for over 2 hours without success. BUT, the system is not frozen. I came back after 2 hours, and short-pressed the power button - and the "Syncing vnodes" message came up and the system powered off gracefully. If it is indeed hanging because of pfBlocker (which incidentally, I do have installed), then there should be some log entries somewhere surely? Is there some way to access the "console" mid boot to see what is going on? I'm using the "vga" version of the image so I don't think the info is going to the serial console or anything. Basically after I restored my config file the pfsense became a brick. No ping to the LAN interface at all, no boot, no response from keyboard if I press enter or anything (but numlock works). The only fix was to reinstall (or to manually edit the config.xml I suppose but that doesn't fix the underlying problem).

@luke1018: …. there are errors .... Bad news  ;) Billion exist already - and people report nearly daily new ones. Next time, take some more time to compose your question, and add the error with all it's details.

It's normal that you don't see the card anymore in windows after writing the pfSense install image on it. MS Windows has no clue of the BSD partitioning scheme or the UFS filesystem used.

@Thierry69: Doesn't seems to want to boot on the USB stick … Thx You have to make some changes in BIOS. https://forum.pfsense.org/index.php?topic=43574.0 http://www.triebwerk23.de/joomla/index.php/firewalls/watchguard-xtm-5-xtm-505-515-525-545-pfsense-64-bit

I finaly upgrade to 4.2 with command shell login to the box with ssh (user admin pw : ….) go to command shell type command : "pfSense-upgrade -d" it take a long time and finaly the upgrade is done.

Oh right, id followed all the guides and it'd been running for years ok (freebsd 64bit). Do you have any suggestions on what may need looked at? Will try and mount the vmdk to grab that config as a last resort

So I reinstalled pfSense from 2.4.2-RC snapshot (20171117) and used a different boot drive (some spare WD Red spinning NAS drive). After some time I experienced a first panic, "Fatal trap 1: privileged instruction fault while in kernel mode". I applied options mentioned by @Birke, and rebooted the system. Sysctl complained that all hw.igb.* tunables are read only, but the system ran without a crash for over 30h. Not sure if these options helped of if I had luck. To get a better use of my systems CPU I enabled PowerD (Hidaptive) and AES-NI acceleration for crypto. Some time after that I experienced another crash, similar to previous one + mentioned "Fatal trap 12: page fault while in kernel mode". At this point I have no idea where does the problem come from. I contacted another forum member that owns this motherboard and he told me that his system runs stable without any tunable changes :(

That doesn't happen here when choosing the auto options. It sounds to me like it either went into the manual install or something was wrong with the existing disk layout that auto couldn't handle.

So, apply https://forum.pfsense.org/index.php?topic=138656.msg761867#msg761867  (first line) to have a fast, positive result ;)

@Jed: Appartently something is wrong with the DNS entry for pkg.pfsense.org Nothing is wrong. SRV records do not work that way. https://forum.pfsense.org/index.php?topic=130708.msg719850#msg719850

It was the netmasks wot did it. It wasn't clear - to me - what that netmask represented, so I left it at /32. After all, the interface only has one address, doesn't it? I suppose what it represents is the subnet that interface is connected to as well as the address of the interface itself. Changed it to /24 and all the VLANs suddenly appear. Thanks for the tip. Apologies for the late response, I have been rather unwell. The network(s) just about functioned without the use of VLANs but I do want to set things up properly. Again, many thanks.

@Jailer: PfSense doesnt support DHCP reservations. Assign static IP’s outside the dhcp range for anything you want the IP address to remain the same. Since when??  I have IPv4 addresses mapped to MAC addresses on my network.

I see you have one post.. so you are new. But why is always need to ask people to put every information needed for the problem? can you just spit the specs of the machine/laptop? and the config of what you think is important? What version 2.3.4 you had (vga, serial, nano ….) and what version 2.4.1 you update, from the gui directly? have you try backup config and do a clean install of the 2.4.1 version? and maybe then restore config? What machine (specifically) you have (with CPU and GPU)? If you want help, you should help us with your problem. Should be cultural by now, i think. If you don't have replays don't blame the community. Thanks