Just upgraded from 2.2.1 to 2.2.2
-
Tried update failed pfsense now showing one character per minute. Upgrade at this rate will take days. Tried it on a second box same issue.both boxes and. Now have to do a full install. I hope it will work.
Cjb -
Tried update failed pfsense now showing one character per minute. Upgrade at this rate will take days. Tried it on a second box same issue.both boxes and. Now have to do a full install. I hope it will work.
CjbYup, same here. I just left it and were out for dinner. I'll post the output when i get home.
Guess I'll be reinstalling again as well.
-
Anyone with a Watchguard tried it yet ?
Just did a clean install tuesday after my hd crashed, don't want to spend too much time on an upgrade today :) -
Not updated my one remaining Firebox yet but I don't anticipate any issues since it's running Nano. If you're running a full install you will have the serial console enabled so you shouldn't hit the serial port issue.
Steve
-
Hi,
I had the same disastrous experience yesterday. Upgraded from 2.2.1 to 2.2.2. Wondered why my network connection wasn't coming back online. Eventually wandered to the Server Room, hooked up a monitor to the pfsense box and saw it stalling at printing "s l o w l y, v e r y s l o w l y" out a character every minute, i.e., K…D...B etc... Tried a few reboots. No joy. >
Shut down the machine, unhooked power, waited 30 seconds, tried again. No joy...same experience. Completely broke.
In the end I had to completely re-install pfsense (2.2.2) from scratch on the ssd. Fortuntely I had a backup of the config file I made that morning, so didn't loose too much (apart from having to reinstall a few packages).
I think this is a serious bug!
-=david=-
-
the traffic graph is still showing double the bandwidth that is actually used
could nobody fix that minor problem?? -
Tried update failed pfsense now showing one character per minute. Upgrade at this rate will take days. Tried it on a second box same issue.both boxes and. Now have to do a full install. I hope it will work.
CjbYup, same here. I just left it and were out for dinner. I'll post the output when i get home.
Guess I'll be reinstalling again as well.
If you read the 3ds after and before this, you MUST disable via BIOS the COM port to solve the problem.
-
The slow console issue has its own thread (and workarounds posted there) –> https://forum.pfsense.org/index.php?topic=92415.msg512166#msg512166
-
Yeah me too
after upgrade on x64 from 2.2.1 to 2.2.2 after reboot it crashed i saw the log window the console is taking 1minute per word on the console to boot..
tried loading older kernel version also fails..
so basically had to turn on old Backup firewall pc to make machines running on the network….
should have tested this on the backup machine first instead of doing it on the working station sharing the internet to the other access points...
-
And yes
100% tested ok now just switch off the BIOS com serial comport and it will boot
