Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 26 subscribers
  • Views 1987 views
  • Users 0 members are here
Options
Suggested
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

SFOS 18.0.0_GA-379 fresh install via HW-18.0.0_GA-Build379-379.iso fails to boot. Stuck at the Shell prompt while booting.

Big_Buck

Hello

On the same machine, I previously upgraded from v17 to v18.  I wanted to test a fresh v18 ISO install.

Burned a CD and installed it.  No obvious error message on the screen.  Will eventually ask to eject the CD and press "Y" to reboot.

But then stuck here:

Will not boot any further.  It would be realy dump to punch a Shell command everytime a firewall boot ...

I check the UEFI.  There's only to boot choices.  "GRUB" and "UEFI OS".  Tried both, just in case.  Same result.

Another day, another waste of time ...

So you guys have an idea ?

Paul Jr 



This thread was automatically locked due to age.
  • 0

    Hi  

    What is the Hardware or Software specification on which you are trying to install? XG home is still available for v17.5 MR12 ISO.

  • 0 in reply to Keyur

    Hardware is a XG125W.

    Paul Jr

  • 0 in reply to Keyur

    Hello

    Not surprisingly, booting from USB key delivered the same result as booting from a USB CD.

    I reach this click "Y", then "Enter" ...

    When it boots, it hangs there:

    There are a few things to underline here.  The first time I attempted the upgrade earlier via a CD Rom, I noticed the "Boot mode select" parameter was at "UEFI OS".  My first few attempts were done with that setting.  I switched it to "LEGACY" and tried again with no luck.  Then I burned a USB Key exactly as mentionned on your instructions and made sure the "Boot mode select" parameter was at "LEGACY" before booting with the USB key.

    Then I tried with the "UEFI Os" parameter with no luck.

    I never reach this point:

    So, clearly, Sophos' ISO fail to work.

    Paul Jr

  • 0

    OK.

    Found how to boot it in BIOS mode.  That was hidden deep and should have never happen.  "Storage" setting in "Compatibility Support Module CSM" was set at "Do not Launch" instead of "Legacy" or "UEFI".  Is it me or this is an enterely stupid "default" configuration ?  Most motherboard I play with will have a third option "UEFI first, then Legacy".

    Clearly, when a Sophos ISO updates the UEFI/BIOS, it should upload as well a working configuration.

    Paul jr

  • 0

    Ok.  Among other things I tested today: Upgrading from v17 to v18 have become absolutely erratic.

    I have fresh installed a XG125w today to version v17.5.8  and v17.5.12.  Then upgrade both to version v18_379.

    Boy !!!  When I upgraded from version early 17.5.x to v18, it was far smooter than.

    Both test were fresh install with standard config for network and wifi.  I mean standard.

    SFOS V17 fresh install would bridge all ports except Port2 and GuestAP.  But once upgraded to v18:

    The bridge is gone and most of the setup.  Some of the few things that remained was one DHCP setup.

    This happened few times.  Because I tested many things.  And yes, restoring from a backup is a total mess.  This "pasword" idea has to be re molded.  More of a tragic nuisance than anything else for now.

    The BIOS.   Holy cow.  This is under any imaginable standards.  I do not know why some manufacturers are still using Aptio.  This UEFI/BIOS is confused, unreliable, bugged, unintuitive.  Today, it was confusing a USB key with a CD/ROM player.  Among other problems.

    Those who wants to run their appliance in UEFI mode.  Good luck.

    Paul Jr