Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 10912 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

Sophos XG v18 is not booting automatically

Kubiac6666

I have a little but annoying problem with my Sophos XG Home installation.

After installing the new v18 onto my Hardware, Grub does not boot automatically the OS. I have to plugin a keyboard and hit Enter every time.

Is there a way to tell Grub to boot automatically "18_0_0_321" ?



This thread was automatically locked due to age.
Parents
  • 0

    Kubiac,

    I suggest you to format and install XG home. I am not sure you can edit the boot loader.I guess that the boot loader should be editable in the following file:

    cat /proc/cmdline
    BOOT_IMAGE=/18_0_0_321 quiet console=tty0 console=ttyS0,38400n8 maxcpus=4 memlimit=6G

    This is my output.

    Regards

  • 0 in reply to lferrara

    OK. Strange.

    The cmdline on my machine looks like this:

    BOOT_IMAGE=/18_0_0_321 quiet console=tty0 console=ttyS0,38400n8

    The limitations of 4 cpus an 6GB ram of the home license are not present like on yours.

    And yes this is an a complete new installation of XG v18.

  • 0 in reply to Kubiac6666

    Same thing here.

    SFVH_SO01_SFOS 18.0.0 GA-Build321# cat /proc/cmdline
    BOOT_IMAGE=/18_0_0_321 quiet console=tty0 console=ttyS0,38400n8

    All my new v18 installations SW/VM didn't came with the CPU/MEM Limits, I've been using a 8C/12GB VM with the XG Home license without any issue lately.

     

    Also, what motherboard are you using?

     

    Inside /boot/grub/grub.cfg, is "set timeout=5" present on the first line?

Reply
  • 0 in reply to Kubiac6666

    Same thing here.

    SFVH_SO01_SFOS 18.0.0 GA-Build321# cat /proc/cmdline
    BOOT_IMAGE=/18_0_0_321 quiet console=tty0 console=ttyS0,38400n8

    All my new v18 installations SW/VM didn't came with the CPU/MEM Limits, I've been using a 8C/12GB VM with the XG Home license without any issue lately.

     

    Also, what motherboard are you using?

     

    Inside /boot/grub/grub.cfg, is "set timeout=5" present on the first line?

Children
  • 0 in reply to Prism

    Thanks Prism for the grub.cfg file. Since this is the file that manages the boot loader options, the issue is inside this file. My grub.cfg file is:

    SFVH_SO01_SFOS 18.0.0 GA-Build321# cat /boot/grub/grub.cfg
    set timeout=5
    set default=1
    insmod all_video
    serial --unit=0 --speed=38400 --word=8 --parity=no --stop=1
    terminal_input --append serial; terminal_output --append serial
    menuentry "SFLoader" {
    linux /SFLoader quiet console=tty0 console=ttyS0,38400n8 BOOT_IMAGE=SFLoader
    }
    menuentry "18_0_0_321" {
    linux /18_0_0_321 quiet console=tty0 console=ttyS0,38400n8 maxcpus=4 memlimit=6G
    }
    menuentry "18_0_0_285" {
    linux /18_0_0_285 quiet console=tty0 console=ttyS0,38400n8 maxcpus=4 memlimit=6G
    }
    SFVH_SO01_SFOS 18.0.0 GA-Build321#

    Take note, mine was an upgrade, so you will see 2 entries. I guess set default is missing.

  • 0 in reply to lferrara

    This is my grub.cfg:

    set timeout=5

    set default=1
    insmod all_video
    serial --unit=0 --speed=38400 --word=8 --parity=no --stop=1
    terminal_input --append serial; terminal_output --append serial
    menuentry "SFLoader" {
    linux /SFLoader quiet console=tty0 console=ttyS0,38400n8 BOOT_IMAGE=SFLoader
    }
    menuentry "18_0_0_321" {
    linux /18_0_0_321 quiet console=tty0 console=ttyS0,38400n8
    }

    This is a fresh installation from the v18 ISO. No upgrade.

    As you can see, timeout is set. But it doesn't boot automatically 18_0_0_321

    My hardware is a mini itx pc with 6 Intel LAN ports and Core i3 6xxxU CPU from ALI Express. I don't remember the name.