Update to 2.4.3 Bricked SG-4860 [FIXED]
-
My SG-1000 bricked after an upgrade from 2.4.2_1 to 2.4.3 as well. It all seemed to go ok during the upgrade process from the web console then it never came back after a reboot and the serial console just shows repeating "Q"s on the putty terminal. Guess i'll be reloading the base image again….
-
My SG-1000 bricked after an upgrade from 2.4.2_1 to 2.4.3 as well. It all seemed to go ok during the upgrade process from the web console then it never came back after a reboot and the serial console just shows repeating "Q"s on the putty terminal. Guess i'll be reloading the base image again….
Can you try option 2 from here? https://www.netgate.com/docs/pfsense/sg-1000/faq.html#how-do-i-restore-the-firewall-os-firmware
Please let me know how it goes!
-
There were like 97 packages or something to update if I recall.. on the 4860.. I know it was more than 74… So it was updating the packages and it just froze?
You bring up an interesting point here… the email from Netgate strongly suggested removing packages before upgrading my 4860. So I uninstalled Snort and pfBlcokerNG (making sure I had access back to the beta site first).
I have made a point of doing upgrades from a local console for many versions now and while watching the console the system seemed to hang after item 4 of 90something for quite some time. I just left it and watched. Got tired of watching and started to dread a hang. Without doing a screen update past item 4 for over 10 minutes, it rebooted and came up and all has been well. Update success.
Is there a glitch in the screen writes and people are halting what looks like a hang?
My best advice at this time is just be patient.Rick
-
Watching the console while upgrading shows you all of the things that are happening after the reboot.
It can take considerable time especially with lots of packages, slow internet, etc.
I am fairly certain that a great many people say the upgrade didn't work, but they were just impatient and unplugged it while it was still working on it, which is bad.
-
Watching the console while upgrading shows you all of the things that are happening after the reboot.
It can take considerable time especially with lots of packages, slow internet, etc.
I am fairly certain that a great many people say the upgrade didn't work, but they were just impatient and unplugged it while it was still working on it, which is bad.
Yeah, kinda like the Windows updates when it appears to be "stuck" when in fact still updating in the background. I tell people when doing updates please be patient. It gets frustrating to see "79% complete" and stay that way for awhile. Alot of times I just do something else like getting coffee and hope it will be done when I get back with a fresh cup.
-
I am fairly certain that a great many people say the upgrade didn't work, but they were just impatient and unplugged it while it was still working on it, which is bad.
Agreed, PEBKAC syndrome just never seems to go away.
-
You guys seem to be pointing a finger of blame, here. But, a "user issue" isn't what I reported. PfSense listed the 74 items it needed to update (perhaps I used the wrong word with "packages"). It went through and showed its progress on updating each item (I watched it). When it was done updating (all the little animations were done for each item), it said it had successfully updated (at least I'm pretty sure it said that) and then said it was going to reboot. It never came back. It's not like I walked across the house and yanked the plug out of the wall while it was downloading. Similarly, I didn't immediately leap out of my chair, sprint across the house and rip that plug out as soon as I saw the message that it was going to reboot. I waited for quite some time before I even tried closing/re-opening my browser and trying various methods to navigate to the logon page. Then there's the time I spent watching the pretty lights on the back of the unit to make sure they weren't red or indicating it was still in the process of rebooting. And, then there's the time I spent trying to use PuTTY to navigate in across the network and getting nothing.
I don't know what happened, but it sure wasn't that a "Problem Exists Between Keyboard And Chair."
-
Again, watching the SERIAL/VGA console during an update if possible is full of all kinds of win.
-
Well, my next action was to unplug the thing, drag it over to my computer, and plug in the serial cord (well, it's actually a USB cord these days) to access the console directly. It's just not possible for me to connect via that cable in its operational position. I think that from now on I'll do updates from the console instead of from the Dashboard.
-
Just posting because it might help others:
Friend of mine had failed update as well; upgrade from gui but following on console.
Seems file system was read-only? (Could this be something left over from nanobsd days?)Attached the screenshot I got from him… (no credits here)
