Upgrading to 1.2.1 issues…
-
I am attempting to upgrade via the web interface from 1.2 release (based on 6.3 FreeBSD) to 1.2.1 RC1 snapshot, and after 5 hours, the web config page still displays the update message and says it will reboot automatically when finished. I'm guessing this should have happened long ago, and was wondering what I should do? Should I reboot manually and hope for the best?
-
Yes.
-
All right, so I rebooted and then attempted to begin the firmware upgrade process again - this time to the newest 1.2.1 snapshot (a day newer than the one I had tried the day before) and now 6+ hours later it is doing the same thing. How can I get this to successfully upgrade?
-
If your using a classic 'PC' setup, why not downloading the latest ISO, brun it to a CD, and boot from it.
It will find the config on your hardisk and the boot takes a couple of secondes more.If the new 1.2.1 pleases you, write it to your hard disk.
I think the update mechanisme is broken in your case.
-
Is it possible that the command line would work better? I'm kinda resisting the thought of reinstalling because it will be somewhat of a pain to get a monitor, and kb and mouse to the server. Not to mention I would have to reinstall the CD drive and graphics card.
-
Is it possible that the command line would work better? I'm kinda resisting the thought of reinstalling because it will be somewhat of a pain to get a monitor, and kb and mouse to the server. Not to mention I would have to reinstall the CD drive and graphics card.
Euuuh, better go back to 1.2 stable right away. When trying out 1.2.1 your still in RC country.
Leave in the CD (why taking it out ?) but note that I'm not hooking any screen to my PC any more for month now.
Upgrading and re-installing works good now through a SSH session - as long as a valid config.xml can be found on boot on HD or floppy.Anyway, you don't have the choice, go back to stable 1.2 or take the latest 1.2.1 - and do it the old fashionned way. Clear is that the update isn't working for for you, so I would consider your actual installation as ‘damaged’?
Always save the config.xml, and if possible, have it on a floppy (if your pfsense machine has this drive).
With that you won't need any vga card any more for sure. -
So if I boot off the CD and it will look for the config.xml on the installation existing on the HD?
-
Yep
That' how I try new builds without taking out the exitant (stable) one.
If you detect strange things, remove the CD, reboot, and all is well again. -
Is just an MSDOS FAT formatted floppy fine? Because I tried that multiples times and the box did not read the config.xml (correct naming right?) because several minutes later when the box should have finished booting it wasn't even pingable much less giving out dhcp leases or having the web interface accessible. I'm wondering if I just need to cart a monitor into that room…
-
I went ahead and moved a monitor to the room the server is in and reinstalled…
-
The 6.3-based 1.2 has upgrade issues apparently, the official 1.2 release does not.