SG-3100: Upgrade stopped part way through due to network dropout



  • Hi, I have an SG-3100 and was upgrading from 2.4.5 to 2.4.5_1 using the WebGUI when the internet dropped out. You can see below the process had made some updates but had just started to download packages.

    Having left it on that page for more than half an hour I went back to the dashboard and started again. It went back in to the upgrade page and instantly jumped back to where it had been, but the download (and overall process) did not resume.

    I don't know if I am stuck half way between versions, and so I am not sure what to do next. It is still running, but would rebooting allow me to start again, or would it brick the device?

    All help appreciated.

    c>>> Updating repositories metadata... 
    Updating pfSense-core repository catalogue...
    Fetching meta.conf: . done
    Fetching packagesite.txz: . done
    Processing entries: . done
    pfSense-core repository update completed. 10 packages processed.
    Updating pfSense repository catalogue...
    Fetching meta.conf: . done
    Fetching packagesite.txz: .......... done
    Processing entries: .......... done
    pfSense repository update completed. 429 packages processed.
    All repositories are up to date.
    >>> Setting vital flag on pkg... done.
    >>> Removing vital flag from php72... done.
    >>> Downloading upgrade packages... 
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up to date.
    Updating pfSense repository catalogue...
    pfSense repository is up to date.
    All repositories are up to date.
    Checking for upgrades (13 candidates): .......... done
    Processing candidates (13 candidates): .......... done
    The following 13 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	bind-tools: 9.14.9 -> 9.14.12 [pfSense]
    	json-c: 0.13.1_1 -> 0.14 [pfSense]
    	openvpn: 2.4.8 -> 2.4.9 [pfSense]
    	pfSense: 2.4.5 -> 2.4.5_1 [pfSense]
    	pfSense-base: 2.4.5 -> 2.4.5_1 [pfSense-core]
    	pfSense-default-config-serial: 2.4.5 -> 2.4.5_1 [pfSense-core]
    	pfSense-kernel-pfSense-SG-3100: 2.4.5 -> 2.4.5_1 [pfSense-core]
    	pfSense-rc: 2.4.5 -> 2.4.5_1 [pfSense-core]
    	pfSense-u-boot-sg3100: 2.4.5 -> 2.4.5_1 [pfSense-core]
    	python37: 3.7.6 -> 3.7.7 [pfSense]
    	sshguard: 2.4.0_3,1 -> 2.4.0_4,1 [pfSense]
    	strongswan: 5.8.2 -> 5.8.4 [pfSense]
    	unbound: 1.9.6 -> 1.10.1 [pfSense]
    
    Number of packages to be upgraded: 13
    
    The process will require 8 MiB more space.
    63 MiB to be downloaded.
    [1/13] Fetching unbound-1.10.1.txz: .......
    
    

  • Netgate Administrator

    It doesn't look to have got past downloading the pkgs so you can probably just try to upgrade again.

    However if you have any doubt just backup the config, install 2.4.5p1 clean and restore your config into it.

    Open a ticket with us to get firmware access if you do not have it. https://go.netgate.com/

    Steve



  • Thanks Steve. I have tried a few times to do the upgrade again and each time the process goes directly back to where it last left off, but the download process that was going does not restart.

    If the next step is to reinstall the firmware, it sounds like there is no reboot the device and then if it comes back up, try the upgrade again?


  • Netgate Administrator

    You can certainly try that.

    Installing clean is a relatively quick and easy process if you have access to the serial console. I would probably go straight to that to be sure.

    https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html

    Steve


Log in to reply