still can`t upgrade...
-
@JonathanLee there is no way to connect a video card or serial port.
ssh session only.
upgrade_log.latest.txt -
Do you see an alert showing it booted into the old BE because the boot confirmation failed in the upgraded BE?
What hardware are you using? It could be something that isn't supported in FreeBSD 15. Yet. Or maybe something that is supported in FreeBSD 15 that causes a problem now it;s a recognized device.
-
@stephenw10 No, there are no alerts, everything works fine. Hardware is detected everything without errors. It has been working since the release of 22.10 (or what it was, I don’t remember), successfully updated to 23.04, then to 23.09.1. Stopped updating since the release of 24.03
My hardware:
Bare metal system on
Intel(R) Xeon(R) CPU E5-2666 v3 @ 2.90GHz
Current: 1200 MHz, Max: 2901 MHz
20 CPUs : 1 package(s) x 10 core(s) x 2 hardware threads
AES-NI CPU Crypto: Yes (active)
IPsec-MB Crypto: Yes (active)
QAT Crypto: No128GB RAM
-
Do you see the new BE listed in System > Boot Environments?
Is it marked bad?
Also: 128GB RAM
-
@stephenw10 yes, i do. this new BE 24.11 absolutely normal. it can be made bootable, but the system reboots into the old BE before loading the web interface.
Could it be because I'm using a PPPOE connection and it only comes up after the system is fully loaded and can't check the license or something like that?
I think so because there is similar hardware, but it is connected via fiber optic from the provider and works great.Intel(R) Xeon(R) E-2314 CPU @ 2.80GHz
4 CPUs : 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
IPsec-MB Crypto: Yes (active)
QAT Crypto: No -
No it will always boot if it can. It's failing to boot and falling back. I'm surprised it's not marking the new BE as bad though. If it fails the boot confirmation check and falls back it should. Which implies it's not getting that far. Maybe you have some obscure drive controller in that or some other unusual hardware device that is preventing it in FreeBSD 15. Hmm, very hard to say without a console output.
What does the boot log show in 23.09.1? The contents of /var/log/dmesg.boot
We might be able to spot a likely troublemaker there. Though without access to a console it might be hard to do anything about it....
-
-
Hmm, nothing especially exotic. The cellular modem might do something odd if it's handled differently in a newer u3g.
I would disable the Realtek Audio device but that requires BIOS access.
Hmm, you could probably mount the new BE and get any boot logs from it...
-
@stephenw10 Well, finally! I physically removed the Huawei modem and deleted the interface in the interfaces tab. And only after this it successfully loaded into BE 24.11
It remains unclear why the modem could influence the download?
If possible, please tell us more about the reasons.Thank you so much for your assistance in solving this mega problem.
-
Possibly it is detected or initialised slightly differently in FreeBSD 15 and if that happens it might not create the ue0 interface. And that would cause pfSense to drop to the interfaces assign prompt due to an assigned missing NIC, eventually rebooting when the confirmation check timer expires.
It would likely have worked if you had just unassigned the NIC. If you still need it you could reconnect it and see how it comes up in 24.11.
Anyway glad you were able to get past it!
