This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting the default firmware to boot

I came across an interesting problem today - an XG135 coming up with a kernel panic error when booting up.

No problem, switch to the other firmware image via the boot loader menu. However, this doesn't change the default choice - so when the XG was rebooted off we went into the broken partition.

I got round this by booting into the working firmware, uploading another version into the broken partition, booting into it, then reverting back to the previous partition (the code that I uploaded to get me out of this was 18MR1).

There didn't seem to be a way I could find that you could do this from the boot menu, or when the XG was up from the CLI or GUI.

If anyone can tell me how it's done without this going back and forth that would be great, I'm assuming it can be though .....

 

Thanks. 



This thread was automatically locked due to age.
  • Hi  

    What is the current state of the device? In which firmware it is booted?

    You need to connect the device over serial console access- https://community.sophos.com/kb/en-us/125209

  • It is up and working.

    The question is how you can set the default firmware that the XG will boot from when it's up using commands from either the CLI or the SF Loader - otherwise you need to go through the process I described if you have a un-bootable partition (that is use the boot menu to boot the device from the previous working firmware, upload a new firmware to the broken partition and boot into that, then select the first partition to boot from by default from the GUI).

    Regards

  • Hi  

    It will boot with default firmware select in the firmware, you can switch it from Boot loader but if the device gets reboot than again it will load with default, you have to rollback if you want to use previous firmware as a default one, You need to select the firmware from GUI to make it default and boot into that.

    SFOS v18 has grub so it will wipe out partition, I would request you to contact technical support and open a support case to investigate the issue further.