[Fixed] Nano image is actually nano+vga again.
-
i upgraded 6 boxes today using console method and worked fine
-
I had a few hours of down time today due to a non booting upgraDe same as steven. Screwing up the images once was bad enough, seems they didn't learn from their mistakes. Very annoying
-
It was bad enough for me trying to connect my console cable behind the fridge (don't ask ::)) at 2am but at least it was in the same building.
It's worth noting that, as before, this is only an immediate problem on boxes where the CF card slot doesn't support DMA. The Nano+VGA image doesn't have DMA disabled where straight Nano does so the box fails to boot with DMA errors. I thought the Alix has this issue though and I'm almost certain the upgrade images will have been tested on that. :-\ I guess the problem is with whatever script copies the images to the update server.Steve
-
Upon reading additional comments, I was able to get 2 more devices to complete with success. I had to manually input the URL to the correct version on the command line but both completed successfully. The one using a 2G image though says 2.1.5 but shows there is a newer version available, which seems odd.
-
Same here, seemed to stop responding after upgrade. Freezing on console after boot menu counted to zero or an option was chosen.
Restarted the x550 twice then tried safe mode which worked but now console is broken.Will diagnose later as I've had to leave for a few hours.
Pete
-
Just upgraded through console. I found the console worked at 9600 instead of what it was supposed to be at (115200).
Web manual update just locks up.
I installed the latest from the mirrors, not the updates:
http://files.bgn.pfsense.org/mirror/updates/pfSense-2.1.5-RELEASE-1g-i386-nanobsd-upgrade.img.gz(used local mirror.)
It works now but boots up at 9600 then switches to 115200.
Guess from now on, I'll be upgrading through the console and manually pick the update.
-
For anyone who has been hit by this you can recover by connecting to the serial console at 9600 (the bootloader is always 9600) and select the previous boot slice at the menu by hitting '1' or '2'. You will then be returned to your previous pfSense version where you can upgrade manually by downloading the correct image from the mirrors or wait until the correct image is on the updates server.
Steve
-
Ok, the update server now seems to have the correct images on it. The 1G image worked fine for me anyway.
Interestingly it's a different file to the upgrade images on the mirrors, different md5 sum.Steve
-
I try to upgrade (2.14) using the web interface ( autoupdater )but for this one is not working, it stop after it finish the download.
:(
My Alix don't like this update ;) -
Well the fault documented in this thread has been fixed so it's not that.
The Alix can struggle with memory during upgrades. Are you running packages? Lots of interfaces? What CF size? Did it just fail to upgrade or crash out somehow? Anything in the logs, particularly the NanoBSD upgrade log in Diagnostics: NanoBSD:?Steve
