Can't Upgrade to 1.2.1 snapshot from Console
-
Havin the same issue here, thankful for any help. Tried both webgui and console for update but nothing works.
-
uname -a
FreeBSD fw.hiddendomain.com.br 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #0: Wed Apr 9 23:22:02 EDT 2008 sullrich@freebsd6-esx.geekgod.com:/usr/obj.pfSense/usr/src/sys/pfSense.6 i386
That's not 1.2-release. Guessing it must be the 6.3-based 1.2, which should be the same other than the base OS, so that shouldn't be a problem.
Havin the same issue here, thankful for any help. Tried both webgui and console for update but nothing works.
Does the console upgrade give you the exact same message as dhipo reported? Are you running the 6.3 based 1.2 as well?
-
Indeed 6.3 based 1.2, downloaded from sullrich testing images : http://cvs.pfsense.org/~sullrich/testing_images/6/FreeBSD_RELENG_6_3/pfSense_RELENG_1_2/pfSense-Full-Update-1.2-RELEASE-20080410-2139.tgz
uname -a gives : FreeBSD pfsense.local 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #0: Wed Apr 9 23:49:10 EDT 2008
sullrich@freebsd6-esx.geekgod.com:/usr/obj.pfSense/usr/src/sys/ pfSense_SMP.6 i386I get the exact message as dhipo reports if upgrading through console. If I try to upgrade from webgui i get the "firmware upgrade in progress window" forever and have to restart to get access to webgui again.
Any suggestions on how to resolve?
I tried putting the 1.2.1 firmware and md5 file in the tmp folder as the console upgrade system refers to, doing this i get a message that the upgrade has begun however this message keeps repeating itself
and the speaker beeps every 5-10 seconds and I have to reboot.Broadcast Message from root@pfsense.local
(/dev/ttyp0) at 5:01 GMT+1…Beginning pfSense upgrade.
Broadcast Message from root@pfsense.local
(/dev/ttyp0) at 5:01 GMT+1...Beginning pfSense upgrade.
Broadcast Message from root@pfsense.local
(/dev/ttyp0) at 5:01 GMT+1...Beginning pfSense upgrade.
Broadcast Message from root@pfsense.local
(/dev/ttyp0) at 5:01 GMT+1...Beginning pfSense upgrade.
Broadcast Message from root@pfsense.local
(/dev/ttyp0) at 5:01 GMT+1...Beginning pfSense upgrade.
-
I tried to load one of the early 1.2.1 snapshots over 1.2r based on 6.3 via the gui originally.
I ended up loading an .iso and starting fresh…
I couldn't use my backup from the release version either. I had to cut and paste...
:) ;)
-
Doesn't seem to matter what firmware I try to upgrade to, I still get the same error. Tried upgrading to even older versions but without any sucess.
-
Any ideas on how to resolve this? If it can't be fixed, is there an easy way of keeping settings and files if I go for a new install?
-
I simply put the two config files side by side in an editor and did some copy and pasting…
-
I simply put the two config files side by side in an editor and did some copy and pasting…
OK, thanks! I'll give it a go as soon as I have some spare time.
-
You can restore a 1.2 config on 1.2.1 or any newer version without changing anything.
-
@cmb:
You can restore a 1.2 config on 1.2.1 or any newer version without changing anything.
Sure worked ! I'm running 1.2.1 now and everything is working perfectly!
-
Hello!
I have the same problem… Pfsense 1.2 Freebsd 6.3
When i try to upgrade via gui it just stops there doing nothing and i have to reboot.If i try to upgrade via console i get a message that
/tmp/latest.tgz is missing and it brings me back to shell options.
Is there any way to fix this without reinstalling the whole thing??thank you
-
When you have the 1.2 FreeBSD 6 based release You first need to downgrade to 1.2 RELEASE. That restores the firmware upgrade to proper condition.
From there you can then update to 1.2.1 without issues.
Manually replacing the firmware files in /etc also works.
-
hello again!
Can you please tell me how to downgrade? I tried to downgrade using pfSense-Full-Update-1.2-RELEASE.tgz from the gui but still does not do anything… Is there any tutorial for this?
thank you
-
You will need to manually replace the /etc/rc.firmware script with a decent copy from 1.2.
Then you can use normal upgrades again.Alternatively just save the config and reinstall
