To 2.5.1 or not ? that is the question :)
-
Forgot to backup on 2.5.0 and I'm stuck on 2.5.1 with this problem...
I hope on a workaround until they release a fix. -
@dredex If it is that important you could download 2.5.0 from
https://atxfiles.pfsense.org/mirror/downloads/or
https://nyifiles.pfsense.org/mirror/downloads/ Before installing I would
check the hashes https://nyifiles.pfsense.org/mirror/downloads/ or find
some University site that has them of course all on you own risk. -
@qinn Thanks but I don't have a backup config from 2.5.0
-
You can use the current config from 2.5.1 never had trouble using a config file among versions.
-
So I some time ago installed 2.4.5.
This was upgraded to 2.5 and then to 2.5.1.
I have a firmware of 2.4.5 that I downloaded from my web GUI when I installed it.
If I use this 2.4.5 firmware on my 2.5.1 current box, will I still be able to use 2.5.1? -
@bismarck said in To 2.5.1 or not ? that is the question :):
Root mount waiting for: CAM
That message shows in dmesg on 2.5.0 as well so it's not new in 2.5.1.
@waqar-uk said in To 2.5.1 or not ? that is the question :):
I have a firmware of 2.4.5 that I downloaded from my web GUI when I installed it.
If I use this 2.4.5 firmware on my 2.5.1 current box, will I still be able to use 2.5.1?By "downloaded from my web GUI" do you mean you downloaded the 2.4.5 .iso file from Netgate? Or saved a configuration backup (.xml file)? You can always install whatever version software you want, and restore a configuration backup. You will be able to upgrade again in the future.
Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
Upvote 👍 helpful posts! -
@steveits New at least for me, was that the root partition was gone and this error message was looping on the screen for ever.
-
As I was affected by the IPV6 gateway bug that also affected the floating IPV6 rules as you couldn't specify the gateway, I had updated to the RC about a week ago. I was too nervous about using a RC build to do so earlier but finally figured, it was probably less buggy than 2.50. So now I see the 2.51... I DO have a 2.45 installer and a 2.50, along with configuration backups and will probably go back to 2.45 if 2.51 is a dud... So I just went 'what the heck' and clicked update... Watched the update process in the GUI, and the reboot went off without any issues. Logged back in, and remembered to be patient and let it reinstall packages/restart services. Waited and watched on the Dashboard. I'm running Snort, PFBlocker, Service Watchdog and OpenVPN Client Export. Everything came back up in less than 2 minutes. Checked the logs, looks ok so far. My setup is lan and two vlans, one wan.
-
So I did get to nuke my 2.5.1 install tonight. I was also experiencing stability issues with it so I just stopped troubleshooting. Got fed up with 2.5.1.
Anyway, I did a clean install of 2.5, restored my 2.5 config and waited for all the packages to install. I am using pfBlockerNG, Suricata (only on a DMZ interface), OpenVPN client export and Service Watchdog (because Unbound is randomly crashing on 2.5). After that I went to check if port forwarding is working on my OpenVPN interface...and BINGO! Port forward on OpenVPN interfaces is working fine again!
I recommend to stay away from 2.5.1. I know I am using the CE edition and maybe I complain too much but if Netgate's own hardware would be more stable and everything working fine, I would gladly spend the money and buy it since this troubleshooting is costing me a lot of time. But seeing how unstable pfSense 2.5 and 2.5.1 is on Netgate's own hardware got me seriously considering other options. For now I need to take a break from this headache and will let it run 2.5 since this is the version which ran fine for days without issues. 2.4.5 p1 ran amazingly fine as well but going back to that older version now means to deal with packages which are "old" as well. Too much of a hassle this :(
-
Went from 2.5.0 single disk ZFS to 2.5.1 this AM.
No problems that I am aware of.However, my LAN Traffic Graph is STILL blank, that happened when going to 2.50, sigh...
-
@vjizzle said in To 2.5.1 or not ? that is the question :):
@bismarck Same here. I can see the same CAM messages but system boots fine.
I see these also.
I did not know this was happening, so I may have had these messages in 2.5.0 also?
Dunno... -
@buggz CAM is also in 2.5.0
-
@steveits said in To 2.5.1 or not ? that is the question :):
@bismarck said in To 2.5.1 or not ? that is the question :):
Root mount waiting for: CAM
That message shows in dmesg on 2.5.0 as well so it's not new in 2.5.1.
@waqar-uk said in To 2.5.1 or not ? that is the question :):
I have a firmware of 2.4.5 that I downloaded from my web GUI when I installed it.
If I use this 2.4.5 firmware on my 2.5.1 current box, will I still be able to use 2.5.1?By "downloaded from my web GUI" do you mean you downloaded the 2.4.5 .iso file from Netgate? Or saved a configuration backup (.xml file)? You can always install whatever version software you want, and restore a configuration backup. You will be able to upgrade again in the future.
OK, thanks.
I just want to know if my untouched firmware ver 2.4.5 can be used to the latest package 2.5.1?
-
@cool_corona said in To 2.5.1 or not ? that is the question :):
@buggz CAM is also in 2.5.0
Hi, that CAM message is just an scrip that is trying to start your WebCam on your computer/devices.
So be aware that going to try to take a picture of you, make sure you have your clothes on. My suggestion is that you should disconnect your webcam
-
@ciscox HAHAHAHA Yeah.... I better. That would scare the shit out of almost anybody if they were aware of whats going on here
HAHAHA
-
An interesting question (for me at least) is 2.4.5-RELEASE-p1 still secure or are there reasons we 'have' to upgrade?
CERT-US has listed at least 8 vulnerabilities with FreeBSD 11.* which could be related to a pfSense-repo upgrade: 2.4.5_10 -> 2.4.5_12
Anyone any comments? -
@itpp21 Yes I would like to know this as well. 2.4.5 p1 was running smooth and I had months of uptime there without any hiccups. I like my firewall to be boring.
-
Hi all
I'm generally used to pfSense updates running smoothly so was rather surprised when the dedicated router PC failed to reboot after applying the 2.5.1 update. I plugged a monitor in and could see the load stalled with "Can't find /boot/entropy". A Google search revealed this to be a common problem relating to legacy v UEFI disc formatting. I guess this was perhaps a problem waiting to happen but I'm puzzled as to why this update triggered the requirement to be UEFI compliant. If it were known that this was a 'feature' of the update some advance warning would have been appreciated....
I run pfSense on a dedicated cheap Mini-ITX PC. The American Megatrends BIOS doesn't have the option to force legacy boot format. I put a spare hard drive in the machine and downloaded 2.5.1 onto a memory stick. On booting the memory stick I got the same "Can't find /boot/entropy" issue. I then discovered the BIOS has an interactive boot option menu and selecting the UEFI option for the memory stick allowed it to load correctly. I then did an install onto the gash disc making sure I specified UEFI and went on to use the config.xml saved from the time of the 2.5.0 release. I regret NOT taking a config backup before attempting the 2.5.1 upgrade. I won't make that mistake again. Luckily such changes as I've made since 2.5.0 are not devastating to do again. The ability to restore the config from backup is awesome.
The fresh install of 2.5.1 now boots without manual interaction using UEFI / gpt.
I don't pretend to understand all that's gone on and feel I have just blundered through to a solution. I would love to be able to convert the original disc with the non-booting 2.5.1 on it to UEFI (and mbr to gpt) but I haven't found a simple recipe for achieving that. I don't assume plugging the disc into a Windows 10 machine and using mbr2gpt.exe will produce something FreeBSD will work with although it might be worth a try.
Had I started out with a UEFI compatible disc I suspect none of my problems would have happened... Has to be written off to a 'learning experience' :).
Any got any comments??
Mike
-
@ciscox said in To 2.5.1 or not ? that is the question :):
Maybe it's time to report it. Make an bug-rapport. Can someone please add it on the bugtracker.
Has been done and apparently a fix is close https://redmine.pfsense.org/issues/11805
Also I find TLA distract from readability so in case anyone cares CAM manual page and a thread on common causes of errors
-
@miken58b That makes totally sense in my case. My pfSense hardware is BIOS/MBR, but the update converted it somehow to UEFI/GPT, thus leaving me with a unbootable system and just a fresh install fixed it.
Looks like the pfSense CE version needs a bit more attention...
