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

Unable to install firmware - new install of Sophos XG

I have been using Sophos UTM for several years and have a new computer I am trying to load XG Home Edition onto.  It is an AMD Ryzen 3 with 8GB memory, 256GB SSD, and there is one Intel NIC built into the motherboard.  I also have two more Intel NICs on a PCI Express card.  I installed Windows 10 on this computer first and verified that all the hardware works, including all three NICs.

I used Rufus to create a bootable USB drive with the ISO I downloaded for XG.  It starts to install and completes the step "Installing loader for appliance SF01V-S001".  It then fails at Installing firmware for appliance SF01V-S001 - unable to install firmware.

Not sure what to try on it next?  When I reboot all I get is a firmware loader menu.  I also have a DVD drive on the computer, will it work better if I try making a bootable DVD and install it that way?  Thanks.



This thread was automatically locked due to age.
  • an Update

     

    I have now added a new SSD as SDA, the original drive was SDB. I wondered if that may have anything to do with it ……. No change in behaviours

    I legitimately obtained the firmware .gpg file from MySophos. I booted the SF Loader and went through adding or updating firmware. I opted to upload the firmware via my browsers (Edge and chrome)  I see a completed message on the Browser and I see a count up to 100% on the appliance console port. After a short wait, the appliance displays a failure message.

     

    I am wondering if the installer is correctly addressing the drives.( the installer appear to only recognise the first drive) I do see the messages indicating it is making area and formatting them. However when I boot from a Ubuntu mem stick and look at the Primary disk I can see no structure on the drive. I have even copied the gpg firmware to the drive in the naive hope this would be recognised.   No Its not.

    The SF Loader is installed on SDA , but worryingly  I see no structure like swap or reporting.

     

    I remember with earlier version of the UTM you had to escape to the shell and mount the drive then let the installer complete. I can see no options within the SF Loader to perform a similar function.

     

    Does anyone have an understanding of what can be amended in the Install Script or indeed make its output be verbose in nature.

     

    all feedback welcome

     

    Don

     

     

     

  • Hi Don,

    there appears to be something strange with your bios. Normal bios does not call a drive SDA or SDB and the installer will identify the drive regardless of name.

    Ian

  • Morning Ian

     

    Thank you for your ongoing assistance.

    The XG installer is the only "Linux" versions that fails to see the drives. Its strange it gives progress indicators when the install is being progressed. If XG base system cant see the drives I an wondering why are thereprogress indicators.   The SF Loader is installed on the correct drive so it has been recognised at some part of the Install.

    Looking through the Forum I cant definatively ascertain the version of Linux it uses. There is talk of Suse and  that its no longer used. CyberoamOS, Astaro Security Linux are also mentioned but no definate statement.   I have seen outputs of "uname" but a generic GNU/Linux message is provided. I would install the native version of the base OS to check the drive status.

    I have used Untagle, Pfsense,IPfire,  ubunto, linux mint (both flavours) and  windows on this and all install correctly. So Im thinking what is unique about XG and the way it recognises SATA drives or the way it performs the Initial install.

     

    Many tahnks

     

    Don

  • I can confirm the disk has been set up. When rebooted the SF Loader is presented. Take the options to escape to sh.

    A directory structure is present and in the /bin,  I can execture  "df"  "fdisk -l" and strangely in this directorty a file called "gpg" exists at 918980 bytes which looks to me to be the appliance firmware.

    I played with the "loadfw" command but could not  accomplish extraction of the firmware.

     

     

    Regards

    Don

  • Fixed up and running.

     

    I take my hat of to Sophos customer support. They are an excellent bunch of professionals. The went way past my expectations.

     

    Solution was to load vers16.x GA code which installed first time,  and them, migrate up to the current 17 version.

     

    The downside is I think the CPU in my appliance may be under spec for the XG flavour of software. 

     

     

    Closed ...

  • Where can we download the version 16 installer?  I can only find the most recent v17 version of it for download.

  • Hi,

     

    Any idea what the issue is? - I'm having the same issue at boot, and did talk with Sophos support as well but no luck on fixing it. 

    They talking about hardware or bios issues, They want me to fix that first, but I don't know what the issue is!?

    I have been running the UTM9 for years now on that hardware, I just want to run XG instead..

    The UTM9 runs without any issues, I have a 500/500 mbit/s internet connecting and have no performance issues on that.. - so I don't think there is any issues with the hardware.

     

    Thanks,

     

    Henrik

  • I have the same issue on an N3700-ITX ASRock board (Intel Quadcore Atom) with an ISO installer downloaded on 2020-03-12. The loader runs without problems, but firmware does not install. Performance should most likely be sufficient. Board runs fine under other intel operating systems.

    Configs listed under the Sophos Memtest are off, Core i7, 32nm, etc., are all wrong. It s a 14nm chip. The amount of memory is recognized ok with 8GB. What is going on here? The linux kernel/version of the loader is actually a bit old for the board. Is there no newer version?

    Any advice, is XG not running on Atom at all?

    Thanks.

    HML