Upgrade to 2.3.4 bricked my SG-4860\. Options?
-
Hi,
Last night I decided to upgrade my SG-4860 from 2.3.3.1 to 2.3.4.
The update seemingly went fine and went until a screen popped up indicating the update was done and the device about to reboot.
From then on however, my device has no longer been accessible.So I hooked up the console, and the device boots up for a few seconds but then remains indefinitely at a "Boot: F1" line.
I checked the forum, and some other seemed to have experienced the same thing.
I also checked the terminal baud settings and other than on 115000 I just get gibberish.
So I am trying to figure out what my options are now:
1/ Do I really need to re-flash/re-install my device?
Is there anything else I can try other than re-installing from an image?2/ My support expired and apparently if I want to download the firmware image for my device I need to pay $400 as it qualifies as a support request.
While I am happy to support pfSense, I have to say that this has me somewhat upset!
Paying $900 for an appliance that bricks my device with the built-in update command and then wants to charge $400 for a download is…sad really!
I'm totally OK with paid support tickets when using a support person's time & effort, but I should at least have free access to the original image file of my device, so that I can try to make my device usable again.3/I'm told I can also install the community edition (pfSense-CE-memstick-ADI-2.3.4-RELEASE-amd64.img.gz) but then I will be loosing some functionalities as well as the fine-tuning for my specific device.
Can someone tell me what exactly I will be loosing if I go that route?If anyone has any pointers, these would be greatly appreciated.
Thank you in advance for your time. -
you got the backup u did before upgrading?
u could try the community version and then restore from backup.
this might be the issue?
https://www.netgate.com/blog/clock-signal-component-issue.html -
Last night I decided to upgrade my SG-4860 from 2.3.3.1 to 2.3.4.
So I hooked up the console, and the device boots up for a few seconds but then remains indefinitely at a "Boot: F1" line.
Honestly, I'd just call them Monday. There have been a few similar posts in the official hardware forum and they've really been extremely helpful to people who have had problems with updates of both BIOS and pfSense itself. You might want to check a few of those posts too, maybe there is something there.
Rick