Thread Info
  • State Suggested Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 23 replies
  • Answers 1 answer
  • Subscribers 44 subscribers
  • Views 10611 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

After installing, sophos xg dont see hard drive after reboot

Sophos User2290

Hi

After installing latest sophos xg (.ISO), pressing "y" to reboot at the end of installtion process - sophos, after this reboot dont see hard drive any more (or rather BIOS is not able to boot sophos from this drive). My SSD is Crucial BX120GB, 4GB RAM on board and 2 CPUs.

Here i found screen in which it ask for "y" and reboot to present stage of this process.

https://community.sophos.com/products/xg-firewall/f/initial-setup/111941/computer-can-not-find-hard-disk-after-installing-sophos-xg-home

 

How can i solve this problem?




[locked by: emmosophos at 9:33 PM (GMT -8) on 27 Jan 2021]
  • 0 in reply to Bob Rich

    Did you managed to install xg?

    I tried today reinstall older UTM9 and everything went fine.

    XG comparing to old UTM is just still defective.

  • 0

    Hello, I have similar or the same problems.

    I install it on two different computers and the same error occurs everywhere. During installation, I can install either an SSD drive or an M2 drive.

    After installation, the system does not find a boot disk, but when I restart the system, the system boots. If I trigger a restart from the system, the error repeats, ... it helps to restart manually again. The error is identical on both different systems (intel i7 4 generation and i7 9 generation).

  • +1 in reply to Taurus
    Hi folks, I’m on mobile so I can’t see everything but I thought I updated this thread. I was able to successfully install XG on my Qorom by disabling all UEFI everywhere. Everything I set to Legacy for boot and disk support, that did the trick. I don’t have any way to get you screenshots or anything right now, just dig around in the bios for chipsets and boot devices
  • 0 in reply to Bob Rich

    Lukcy you. As i mentioned before turning on legacy didnt help at all in my case. Besides.... its not solution to turn off relatively modern disc technologies.  It should be considered at most as temporary workaround, all the more older utm9 has no such problems.

  • 0

    I believe this is what I'm now experiencing as well. I guess there's been no solution or work around? I've tried putting CMS in all legacy mode. (this is the only legacy options I could find in the bios) No idea where to go from this point. 

  • 0 in reply to Matt Lebowski

    Wow, just as I said that I solved the problem. I just had to reinstall yet again once everything was in legacy. After that, it finally booted and continued setup. Thanks guys.

  • 0

    After a few months still not solved (bios legacy version).

    Moreover home download version is still the same faulty installer old version (SW-18.0.1_MR-1-Build396-396.iso) instead of .MR-3 which is newer after update. No possibility to try and download .mr-3. Maybe it could help.

    ps. i checked partitions after installing XG. It create only 4 (120GB SSD):

    - pri/log 18,5GB FREE SPACE

    - primary 146MB ex4

    - primary 67MB fat32

    - pri/log 101GB FREE SPACE.

  • 0 in reply to Sophos User2290

    small update.

    Doesnt work also with 18.01-MR3 build.

    During instalation  "installer loader for appliance SVxxx" for one second appear additional message on screen:

    sh: cant kill pid 1051; no such process

    I'm giving up. No real support here. The worst thing is  this stupid installer, say that everything went "OK" and give you absolute no clues what is wrong. Time to go back again to older utm9.

    In my opinion devs should implement minimum errors checking/traps messages/warnings during installation.As i said before. I can boot any linux distro or windows, also utm9, XG still not. This is frustrating.

  • 0

    I managed to get my Qotom Q355G4 working with Sophos XG (SW-18.0.3_MR-3-457). It was quite frustrating but the following worked for me.

    BIOS Settings
    Advanced

    Restore From AC Power Loss = Power on

    Advanced > CSM Configuration

    Boot option filter = Legacy only
    Storage = Legacy
    Video = Legacy
    Other PCI devices = Legacy

    Advanced > USB Configuration

    XHCI Mode = Disabled

    Advanced > SATA Configuration > Serial ATA Port 0

    SATA Device Type = Solid State Drive

    Rufus (USB Key Image)

    Make sure you "Write in DD mode" when requested.

    After setting all of these I was finally able to install Sophos XG. It does sit at the underscore cursor for a long time though. Prior to that I was getting the message:

    Reboot and select proper Boot device
or Insert Boot Media in selected Boot device and press a key

  • 0 in reply to icemonkey

    thx for sharing.

    In my situation (wyse terminal) i dont even have half of these options what you have. My terminal bios is only legacy (no uefi) and dont have any "advanced" options.

    For me problem still exist only for XG firewall installer.  I dont know what they have spoiled, but installer dont see disk after installation. Propably i will give a chance to pfsense or come back to UTM9 without proxy imap  (what is oddity).

Unfiltered HTML