Page 1 of 4 123 ... LastLast
Results 1 to 10 of 37

Thread: Newly-installed Leap 42.1 OS not available in bootloader

  1. #1

    Default Newly-installed Leap 42.1 OS not available in bootloader

    I installed an additional Linux system (Leap 42.1) in previously-unused space on a drive that has a SuSE 13.2 system. Here is the configuration of the drive (from the install process drive configuration dialog and now showing in the 13.2 partitioner [less the “/” mount point in the latter]):

    Code:
    /dev/sde    476.94 GB
    
    /dev/sde1       2.01 GB             Linux swap     Swap     swap    [SuSE 13.2]
    /dev/sde2      99.61 GB            Linux native     Ext4      /
    
    /dev/sde3    375.31 GB             Extended
    /dev/sde5    375.31 GB       F    Linux native    BtrFS     /          [Leap 42.1]
    The current version of grub2 in 13.2: 2.02~beta2-20.14.2

    I took the default options in the bootloader dialog:
    Code:
    Booting
            . . .
            Change Location:
                Install bootcode into MBR [do not install]
                Do not install bootcode into “/” partition [do not install]
    When the installation completed (with updates), the system rebooted into 13.2 but does not provide an option for 42.1 on the boot loader page. Nor is it available under the bootloader option tab in Yast2/bootloader (in the 13.2 system).

    Will the command "grub2-mkconfig -o /boot/grub2/grub.cfg" detect and add the new system to the bootloader and grub?

    Thank you.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,190

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    You left 13.2 in charge you must now tell it a new OS is installed.

    In Yast -boot loader set scan for foreign OS box that should find it

  3. #3

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    gogalthorp -

    Thank you for the reply.

    In YaST2 > Boot loader > Bootloader Options (third or right-most tab), the option "Probe Foreign OS" is (and was) checked.

    Is that what you meant by "set scan for foreign OS box?"

    I also ran os-prober in the shell with no luck on 42.1 Only two other installations popped up: Windows XP and openSuSE 13.1, both on other drives; these are available on the boot loader page when the machine starts up.

  4. #4

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    gogalthorp -

    On a hunch, I checked and found more recent versions of os-prober (as well as grub2, of which I was aware). I just updated both os-prober and four grub2 files (grub2-2.02~beta2-20.14.2.x86_64; grub2-i386-pc-2.02~beta2-20.14.2.x86_64; grub2-x86_64-efi-2.02~beta2-20.14.2.x86_64; and grub2-snapper-plugin-2.02~beta2-20.14.2).

    Leap 42.1 now appears in the os-prober results and in YaST2 bootloader options.

    Should I now run the "grub2-mkconfig -o /boot/grub2/grub.cfg" command?

  5. #5
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,190

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    You can or just do it in Yast a small change and back again then accept. A tweak will make Yast modal think a change is made and thus rebuild things. Using the command line is ok too bu I think Yast is less prone to mistakes

  6. #6

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    I do not see any option in Yast other than to select a specific default installation, which is not what I'm attempting to do here.

    The issue now seems be that the bootloader menu is not updating. Running "update-bootloader --refresh" did not resolve the issue.

    And 42.1 is showing in grub.cfg:
    Code:
    ### BEGIN /etc/grub.d/30_os-prober ###
     . . .
    
    menuentry 'openSUSE 42.1 (x86_64) (on /dev/sde5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-0f039c98-77ff-45ba-9c39-a16194c124be' {
        insmod part_msdos 
        insmod btrfs
        set root='hd0,msdos5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 --hint='hd0,msdos5'  0f039c98-77ff-45ba-9c39-a16194c124be
        else
          search --no-floppy --fs-uuid --set=root 0f039c98-77ff-45ba-9c39-a16194c124be
        fi
        linux /@/.snapshots/1/snapshot/boot/vmlinuz-4.1.21-14-default root=UUID=0f039c98-77ff-45ba-9c39-a16194c124be ${extra_cmdline} resume=/dev/disk/by-uuid/c7dbed1d-6fb7-489b-8737-bd866c0f915d splash=silent quiet showopts
        initrd /@/.snapshots/1/snapshot/boot/initrd-4.1.21-14-default
    }
    submenu 'Advanced options for openSUSE 42.1 (x86_64) (on /dev/sde5)' $menuentry_id_option 'osprober-gnulinux-advanced-0f039c98-77ff-45ba-9c39-a16194c124be' {
        menuentry 'openSUSE Leap 42.1 (on /dev/sde5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/.snapshots/1/snapshot/boot/vmlinuz-4.1.21-14-default--0f039c98-77ff-45ba-9c39-a16194c124be' {
            insmod part_msdos 
            insmod btrfs
            set root='hd0,msdos5'
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 --hint='hd0,msdos5'  0f039c98-77ff-45ba-9c39-a16194c124be
            else
              search --no-floppy --fs-uuid --set=root 0f039c98-77ff-45ba-9c39-a16194c124be
            fi
            linux /@/.snapshots/1/snapshot/boot/vmlinuz-4.1.21-14-default root=UUID=0f039c98-77ff-45ba-9c39-a16194c124be ${extra_cmdline} resume=/dev/disk/by-uuid/c7dbed1d-6fb7-489b-8737-bd866c0f915d splash=silent quiet showopts
            initrd /@/.snapshots/1/snapshot/boot/initrd-4.1.21-14-default
        }
        menuentry 'openSUSE Leap 42.1, with Linux 4.1.21-14-default (on /dev/sde5)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/.snapshots/1/snapshot/boot/vmlinuz-4.1.21-14-default--0f039c98-77ff-45ba-9c39-a16194c124be' {
            insmod part_msdos 
            insmod btrfs
            set root='hd0,msdos5'
            if [ x$feature_platform_search_hint = xy ]; then
              search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos5 --hint-efi=hd4,msdos5 --hint-baremetal=ahci4,msdos5 --hint='hd0,msdos5'  0f039c98-77ff-45ba-9c39-a16194c124be
            else
              search --no-floppy --fs-uuid --set=root 0f039c98-77ff-45ba-9c39-a16194c124be
            fi
            linux /@/.snapshots/1/snapshot/boot/vmlinuz-4.1.21-14-default root=UUID=0f039c98-77ff-45ba-9c39-a16194c124be ${extra_cmdline} resume=/dev/disk/by-uuid/c7dbed1d-6fb7-489b-8737-bd866c0f915d splash=silent quiet showopts
            initrd /@/.snapshots/1/snapshot/boot/initrd-4.1.21-14-default
        }
    }
    
    ### END /etc/grub.d/30_os-prober ###
    How do I get 13.2 to update the menu? grub2-mkconfig?

  7. #7

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    Does anyone know how to refresh/repopulate the bootloader menu (the splash page with boot options at login)?

  8. #8

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    While waiting for a response to my query immediately above, I ran grub2-mkconfig, but the menu remains without the 42.1 entries, even though the YaST bootloader lists them:

    Code:
    linux-5:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
    Generating grub configuration file ...
    Found theme: /boot/grub2/themes/openSUSE/theme.txt
    Found linux image: /boot/vmlinuz-3.16.7-21-desktop
    Found initrd image: /boot/initrd-3.16.7-21-desktop
    Found linux image: /boot/vmlinuz-3.16.7-7-desktop
    Found initrd image: /boot/initrd-3.16.7-7-desktop
      WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
      No volume groups found
    Found Microsoft Windows XP Professional on /dev/sda1
    Found openSUSE 13.1 (x86_64) on /dev/sda6
    Found openSUSE 42.1 (x86_64) on /dev/sde5
    done
    linux-5:~ #
    I don't think the lvmetad warning applies in my situation, but I may be wrong about that.

    (I hope that I do not have to uninstall and then re-install grub2.)

  9. #9
    Peter_Abc NNTP User

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    On 15/06/16 07:46, w2tq wrote:
    >
    > While waiting for a response to my query immediately above, I ran
    > grub2-mkconfig, but the menu remains without the 42.1 entries, even
    > though the YaST bootloader lists them:
    >
    >
    > Code:
    > --------------------
    > linux-5:~ # grub2-mkconfig -o /boot/grub2/grub.cfg
    > Generating grub configuration file ...
    > Found theme: /boot/grub2/themes/openSUSE/theme.txt
    > Found linux image: /boot/vmlinuz-3.16.7-21-desktop
    > Found initrd image: /boot/initrd-3.16.7-21-desktop
    > Found linux image: /boot/vmlinuz-3.16.7-7-desktop
    > Found initrd image: /boot/initrd-3.16.7-7-desktop
    > WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
    > No volume groups found
    > Found Microsoft Windows XP Professional on /dev/sda1
    > Found openSUSE 13.1 (x86_64) on /dev/sda6
    > Found openSUSE 42.1 (x86_64) on /dev/sde5
    > done
    > linux-5:~ #
    >
    >
    > --------------------
    >
    >
    > I don't think the lvmetad warning applies in my situation, but I may be
    > wrong about that.
    >
    > (I hope that I do not have to uninstall and then re-install grub2.)
    >
    >

    Hi,
    Did you install bootloader for Leap as well?
    If 13.2 is your bootloader, your above grub2 config should work, IMHO.

  10. #10

    Default Re: Newly-installed Leap 42.1 OS not available in bootloader

    Peter_Abc -

    In the opening post, I indicated that I accepted the default options in the bootloader dialog:
    Code:

    Code:
    Booting
            . . .         Change Location:
                Install bootcode into MBR [do not install]
                Do not install bootcode into “/” partition [install]
    The MBR is on the drive where I initially loaded 13.2 (see the first code section in the opening post for the drive layout).

    Is the second and last line where the problem occurred?

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •