Issue installing latest pfSense Plus (24.03 release)

[olivierlambert]

Can you try to add a bit more RAM in case? Like 4GiB/4GiB to see if it's better

[Affonso]

@olivierlambert I changed the memory settings like this

I'm going to proceed with the upgrade and post the outcome

[olivierlambert]

Perfect, keep us posted!

[Affonso]

The same error

[olivierlambert]

Is there a way we can test that ISO? It's hard to reproduce if we don't have any way to test it here or in the community

[Affonso]

@olivierlambert let me talk to Netgate support and work some way out

[nikade]

Googling the error "supervisor read data page not present" gives a lot of hints towards bad memory, are you using ECC or non ECC?

[Affonso]

@nikade

The Dell R620 (Intel):

# dmidecode -t memory | grep -i "ecc"
	Error Correction Type: Multi-bit ECC

The lab AMD Razor

# dmidecode -t memory | grep -i "ecc"
# 

One server has ECC memory, the other doesn't. I believe it would be a very odd case of having "bad memory" on two completely different instances, and the fault being exactly the same on the different machines ... but as I said, this is not my area of expertise.

[Andrew]

@Affonso I had a problem upgrading OPNsense to 24.7 which uses FreeBSD 14 using XCP 8.2.1

OPNsense had a kernel crash related to Xen using some FreeBSD kernel options. OPNsense was able to update their kernel to resolve the crash issue.

It was a OPNsense/FreeBSD issue, not a XCP issue. It has been resolved.

Here's the OPNsense github issue. I don't know if it's related.

[Affonso]

Thank you @Andrew I will mention this to pfSense. lets hope

[Affonso]

So just to give a quick update on how this went:

Since pfSense 24.03 is based on FreeBSD 15 I proceeded with a FreeBSD 15 installation on XCP-ng to see if the issue stemmed from there. FreeBSD15 installed and booted correctly.
From there I ended up testing the development snapshot 24.08.
Also installed correctly and booted.

So whatever issue was there between pfSense 24.03 and XCP-ng that was preventing it from booting, was only present on version 24.03.

[Andrew]

@Affonso Looks like it might have been Bug 15684 in 24.03 that was resolved for 24.11 (release notes).