Attempted to update from 2.3.5 to 2.4.3 this morning on a SG-8860 and it didn't go as expected. Overall it looked like it went well, packages were downloaded and looked like they installed, firewall rebooted, but when it came back up it was still on version 2.3.5. However, it looks like the kernel did change to "11.1-RELEASE-p10". Almost like it partially upgraded.
- Rebooted 2nd time but no changes
- Running update from cli (option 13) says the following
Another instance is already running... Aborting!
Figured it was worth a quick post, we are going to reinstall via usb tomorrow morning unless some others have a suggestion?
Normally an upgrade goes like this:
- Fetch everything and get stuff ready
- Install new kernel and reboot
- Install everything else and reboot again
- Finish up upgrade tasks (e.g. upgrade config) and then done
It sounds like maybe it didn't make it all the way through the first reboot since it had the new kernel but didn't complete the upgrade.
What, if anything, is in
Appreciate the input, so it sounds like we are in a half way stuck state. Which is probably why DNS forwarding is broke as well.
All that was in that file is....
Updating repositories metadata...
Hmm, I haven't seen one get stuck like that in a while. It shouldn't need to hit the repos again at that stage, unless the file was wiped out some time after the actual failure.
Safest bet is to reinstall 2.4.3 and use the Recover config.xml option to pick up the current config
That is our current plan for the AM, I appreciate the input!