Is there anything actually connected to that SATA channel?

If not you can probably disable it in the BIOS.

Otherwise I'd try this system tunable:
https://man.freebsd.org/cgi/man.cgi?query=ahci#SYSCTL

Steve

Yup check that the drive(s) are shown in the boot log. Or when it fails like that drop to the command line and check: ls -ls /dev

Yup almost certainly because of old BE snapshots taking up space. You needs more that 1.2G to upgrade into. Remove old BE snaps.

@reaper689

need to put a memstick version on the USB flash drive drive, not the iso.

https://atxfiles.netgate.com/mirror/downloads/

@stephenw10 I will have to wait until the end of the semester to test again it malformed the data on the boot environment after also. So, I had to use another one I have multiples of them in case a test failed glad I made some, I am so thankful for boot environments, it failed I was up in 3 mins after I got a term session going again.

2.7.2 is only available CE version from there. There are no public 2.8 dev snaps yet.

Hi All,

I just thought I'd respond because I had this "Failed to select the ZFS volume type" issue on install of whitelabel hardware, but was able to resolve it by retrying install with the "Netgate Installer - AMD64 Memstick USB" installer instead of the ISO installer.

Hope this helps someone else!

Ah interesting. Good result!

@stephenw10 Got it, thanks.
If the GUI sets the branch, and I assume updates some configuration files.
Are there a set of files that we can modify via the console, or symbolic links, that can manually set the branch version, so we can then issue pfSense-upgrade -U -d -y

@stephenw10 IIRC the message about the missing /etc/hostid was the last message before the hang (I neglected to make a screenshot).

Just make sure you have a backup of the config and you can always recover.

@rac1503
Sorry for late reply, but thanks to the last iOS update I see emails only just after rebooting the phone. (One may think that email is an anachronistic way of communication compared to modern messengers but it is annoying if it does not work.) However, fine, that you have solved your problem!
Regards, Michael

@stephenw10 I see wireguard getting uninstalled in the logs following a reboot after config restore.

Once reinstalled and rebooted it does remain installed.

There isn't yet a newer public installer version but it should be available soon.

The checksum difference is not a cause for concern IMO. It is curious though.

Does it show the 24.11 branch in the dropdown selection? You have to select it in order to upgrade.

@stephenw10 - I totally agree, but that is what originally pulled me into the thread. I wouldn't bother changing the thread title.

I also think that my wear rate is actually slower so I expect the 1.5 year estimate to be more like 3 years.

Phizix

@Bly said in Syntax error upgrading from 24.03 to 24.11:

Warning: syntax error on file /boot/loader.conf.lua
if _ENV["smbios.system.maker"] == "Netgate" then
^

Yes that's normal on a 3100. The 32bit loader doesn't support that lua code which is shared by all platforms. It shouldn't cause any issue beyond that cosmetic warning though.

Steve

@roadrunner662 Open WRT is different from pfSense. Open WRT is dedicated access point software with limited firewall capabilities, and pfSense that is dedicated firewall software with limited AP capabilities. The Open WRT is very streamlined for AP use and software is smaller. Pfsense is a hypothetical tank and takes up more room. I run Open WRT on my AP and pfsense is on its own box. I don’t think you should run it on a layer 3 switch.

Yup I would reinstall clean to be sure at this point.

@SteveITS

I contacted support and they said I could only downgrade to 24.03 via the installer.

I went back to 24.03 and it fixed my DHCP and SQUID problems. Turns out my VLAN issue was due to a new feature added in 24.03 and I've attached the excerpt for anyone else experiencing the same issues with VLAN giving firewall problems

I couldn't connect to my VLANs with the following appearing in my logs

VLAN123 Default deny rule IPv4 (1000000103)

I could ping devices but that's all.

"Beginning with pfSense Plus software version 24.03 and pfSense CE software version 2.8.0, the default configuration is explicitly set to an Interface-bound policy to enhance security. It appears that in your previous version, the default was configured as a Floating state type. You can read more details about this change here: https://www.netgate.com/blog/state-policy-default-change"

Changing the Firewall State Policy to Floating States (System>Advanced>Firewall & NAT - Advanced Options) solved the VLAN problems for me.