2.4.0 Release
-
Upgraded from 2.3.4 to 2.4.0
I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"
No internet connection anymore.
I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media) -
Hi,
I upgraded from web interface. And system ins not openning now!
I attached screen.
When I write
ufs:/dev/ada01a
on this screen than system started and open normally. But when I restart the system same black screen comes up?!What is wrong?…
Regards,
Mucip:)
-
Hi,
I upgraded from web interface. And system ins not openning now!
I attached screen.
When I write
ufs:/dev/ada01a
on this screen than system started and open normally. But when I restart the system same black screen comes up?!What is wrong?…
Regards,
Mucip:)Follow the instructions in the link in my post above (blog article has pretty much a step-by-step). You basically just need to alter your fstab to match your new drive names from the console once PFSense has booted up for both root and swap.
-
I've been running off of development snapshots, and I'm currently on 2.4.1.a.2017*
How can I switch to the 2.4 release? Switching to stable shows I have the latest, presumably because 2.4.1 is higher than 2.4.0.
You'll have to reinstall, there is no proper way to force a downgrade. It's easy to reinstall though, and your config can still be used because the format hasn't changed on 2.4.1 yet.
-
Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu
Sounds like maybe you're hitting what people are seeing in this thread: https://forum.pfsense.org/index.php?topic=137103.msg754234#msg754234 - Try the suggestions there, if they apply.
-
I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"
I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media)
https://redmine.pfsense.org/issues/7936
Also, the number of people using both bridge mode and traffic shaping at the same time is … low. :-)
-
I got several errors at bootup: "There were error(s) loading the rules: pfctl: bridge1: driver does not support altq - The line in question reads [0]: @ 2017-10-13 12:53:16"
I suggest you think twice before upgrading if you have Pfsense in Bridge mode. Just installed back to 2.3.4 (luckily have old installation media)
https://redmine.pfsense.org/issues/7936
Also, the number of people using both bridge mode and traffic shaping at the same time is … low. :-)
Thanks for the link. Any chance traffic shaping is introduced in bridge mode in future releases? Is there any place where to download previous releases? Could not find them from download pages. I guess I have to stick with previous releases for the time being.
-
Upgraded last night and like a few others it said on the web interface that the upgrade had failed. However after rebooting the box it came back up with the newly installed system. Only thing I've noticed so far is that the system is using way more memory than what it was before. It's hovering around 90% vs the <40% that I recall from before.
LoboTiger
-
Follow the instructions in the link in my post above (blog article has pretty much a step-by-step). You basically just need to alter your fstab to match your new drive names from the console once PFSense has booted up for both root and swap.
No need to mess with fstab manually: https://forum.pfsense.org/index.php?topic=137929.msg754282#msg754282
-
Hi,
I upgraded from web interface. And system ins not openning now!
I attached screen.
When I write
ufs:/dev/ada01a
on this screen than system started and open normally. But when I restart the system same black screen comes up?!What is wrong?…
Regards,
Mucip:)Same thing happened to me. Upgraded remotely and the pfSense went offline and never came back. When I got home to address the issue, had the same mounting problem.
At first I was able to boot by using the kernel.old, but the system was very unstable with many segmentation faults. Then after reading here online, I was able to mount the only harddrive I have in the system ada0sa1, and change the /etc/fstab.
-
Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu
I'm experiencing this behavior on my APU2C4 as well.
-
Upgrade successful but I'm monitoring an issues where webaccess SSH even serial stops responding after a period of time yet internet is still going SSH or serial will allow login but never displays the splash screen/welcome screen that usually gives you a menu
I'm experiencing this behavior on my APU2C4 as well.
Check to see if you're hitting this: https://forum.pfsense.org/index.php?topic=137103.msg754234#msg754234
-
@terminalhit:
Hi,
I upgraded from web interface. And system ins not openning now!
I attached screen.
When I write
ufs:/dev/ada01a
on this screen than system started and open normally. But when I restart the system same black screen comes up?!What is wrong?…
Regards,
Mucip:)Same thing happened to me. Upgraded remotely and the pfSense went offline and never came back. When I got home to address the issue, had the same mounting problem.
At first I was able to boot by using the kernel.old, but the system was very unstable with many segmentation faults. Then after reading here online, I was able to mount the only harddrive I have in the system ada0sa1, and change the /etc/fstab.I got the same result. I have updated it remotely through the webui: first attempt failed, the second was successfull but the router went offline. When I reached it, I found the same thing.
I had to input the
mountroot> ufs:/dev/ada0s1a
in order to boot itWell done pfSense team!
-
OK, this thread is officially getting unwieldy :-)
Locking this thread for now. Please find an existing thread for a single issue topic or start separate threads for distinct issues but only after searching to see if you can find an existing related thread. We're seeing the same info in 2-3 threads and new threads for duplicate topics and so on.
Using the "All Unread" view is especially helpful for locating new/recent threads: https://forum.pfsense.org/index.php?action=unread;all;
