Grub and I am starting to become agressive

Gps2010 · February 16, 2018, 1:20am

[rant]Lets start by the aggressive part, I have been reading multiple websites for days about grub, and still don’t have a clue on how to fix my problem.

I also start to get a feeling I want to kill the people who wrote grub.

Who ever thought it was a good idea, to have files in multiple , and I mean multiple places? >:(

This mostly annoys me, when I read the old grub had one bloody file. [/rant]

Whats the situation, I have 3 hard disk

sda NTFS WIN 7
sdb Ext4 Leap 42.3
sdc Ext4 Leap 42.1

After an failed update I managed to get 42.3 booting by first booting 42.1.

The grub screen now gives 5 options, which is good.

Leap 42.1 is first, and I want of course 42.3 at the first spot.
I am however getting an headache, because in yast under boot options in 42.3, 42.3 is listed as the os that should start first.

When I start the pc , grub greets me with 42.1 listed first.

Then an question about yast and the mbr under bootloader options.

Does linux ( opensuse ) have an mbr?

Or does this only apply to a pc like mine, were there is also a windows disk.

Is there a simple way to find out how grub is set up now ? Why it does what it does ?
Should I look in the grub file yast generates ?

Can I use grub for this? I noticed if I type ls in the Grub console

ls

it lists all hard disk.

gogalthorp · February 16, 2018, 3:10am

MBR references both an area at the start of the disk (Master Boot Record) and a boot method. Assuming you have a newer PC ( less then 6 or 7 years old) it has a thing called the UEFI which does the functions of the old BIOS and uses the EFI boot method. So today you have two different boot methods EFI and MBR (legacy). With multiple OS you should not mix the two. All OS should use the same method. First addressing only Linux OS’s each one will have it’s own grub which are totally independent. Now it all boils down to how they are set to boot MBR/EFI. So how do you have the boot setup???

It may help to show us the drive layouts ie copy/paste the output of fdisk -l. Please use code tags to preserve the formatting. (# in the editor tool bar)

In Yast you can set which entry is the default. Most setting can be done from Yast - boot loader. But remember each Linux has its own grub setup and the one you see at boot, the controlling one, is the one set to boot in the UEFI boot menu or the BIOS depending on how old the hardware is. You can’t change the listing order in Yast you have to edit the grub files for that just set the default.

Gps2010 · February 16, 2018, 3:50am

No UEFI here, thats one small part I do get.

You remark about mbr referring to two things, already makes things a bit more clear.

The output of Fdisk -l

wissel geheugen = swap

Schijf /dev/sda: 465,8 GiB, 500107862016 bytes, 976773168 sectoren
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 512 bytes
In-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: dos
Schijf-ID: 0x2b6d04f2

Apparaat   Op.  Begin     Einde  Sectoren Grootte ID Type
/dev/sda1  *     2048    206847    204800    100M  7 HPFS/NTFS/exFAT
/dev/sda2      206848 976771071 976564224  465,7G  7 HPFS/NTFS/exFAT


Schijf /dev/sdb: 931,5 GiB, 1000204886016 bytes, 1953525168 sectoren
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 4096 bytes
In-/uitvoergrootte (minimaal/optimaal): 4096 bytes / 4096 bytes
Schijflabeltype: dos
Schijf-ID: 0x00083323

Apparaat   Op.      Begin      Einde   Sectoren Grootte ID Type
/dev/sdb1  *         2048 1881843711 1881841664  897,3G 83 Linux
/dev/sdb2      1881843712 1945331711   63488000   30,3G 83 Linux
/dev/sdb3      1945331712 1953523711    8192000    3,9G 82 Linux wisselgeheugen


Schijf /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectoren
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 512 bytes
In-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: dos
Schijf-ID: 0x48e3d6ef

Apparaat   Op.    Begin     Einde  Sectoren Grootte ID Type
/dev/sdc1          2048   4208639   4206592      2G 82 Linux wisselgeheugen
/dev/sdc2  *    4208640  46153727  41945088     20G 83 Linux
/dev/sdc3      46153728 976773119 930619392  443,8G 83 Linux

eng-int · February 16, 2018, 3:52am

There is only one effective boot chain. This is primarily determined by motherboard BIOS settings and firmware.
Legacy boot (MBR-DOS partitioning) or UEFI (with or without secure boot)
Device boot order.
Partition boot flag
Grub2 or Grub2-EFI
Use of “device name” “label” or “UUID” to identify partitions.

You have evidently chosen not to use the default recommendations during the openSUSE installs. My guess is that:
You are using UUID, so once the boot gets as bar as Grub the deviice name (e.g. sdb1) is irrelevant.
Either MBR or EFI Boot are pointing to the Leap-42.1 Grub.
Try using YaST in 42.1 to set the default operating system boot order.

Otherwise more detailed information about your system is required.

hcvv · February 16, 2018, 9:03am

First: do not write things like "The output of Fdisk -l ". To begin with it is fdisk, not Fdisk, then you better include one more line at the top (the one that has the prompt and the fdisk -l command) to your copy/paste. Then we see what you saw and you do not have to write what you did (with or without typos).

Then: to avoid having dutch words in your output, you can do

LANG=C fdisk -l

(and that works also for other commands).

As example an part of such a listing from one of my systems:

boven:~ # fdisk -l

Schijf /dev/sda: 320.1 GB, 320072933376 bytes, 625142448 sectoren
Eenheid = sectoren van 1 * 512 = 512 bytes

Sectorgrootte (logischl/fysiek): 512 bytes / 512 bytes
in-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: dos
Schijf-ID: 0x1549f232

 Apparaat Opstart   Begin       Einde     Blokken   ID  Systeem
/dev/sda1              63     4209029     2104483+  82  Linux swap / Solaris
/dev/sda2   *     4209030    46154744    20972857+  83  Linux

boven:~ # LANG=C fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes, 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x1549f232

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              63     4209029     2104483+  82  Linux swap / Solaris
/dev/sda2   *     4209030    46154744    20972857+  83  Linux

eng-int · February 16, 2018, 9:47am

Gps2010:


Apparaat   Op.      Begin      Einde   Sectoren Grootte ID Type
/dev/sdb1  *         2048 1881843711 1881841664  897,3G 83 Linux
/dev/sdb2      1881843712 1945331711   63488000   30,3G 83 Linux
/dev/sdb3      1945331712 1953523711    8192000    3,9G 82 Linux wisselgeheugen

You have a Boot Flag set on the largest partition on sdb. Another guess: sdb1(897GB) is a data partition (e.g. “/home”), and sdb2 (30GB) hols the operating system (“/”).

karlmistelberger · February 16, 2018, 10:01am

Given that you may want to

boot Leap 42.3 and install grub without further tinkering using YAST2
enter UEFI and select sdb as boot device
save changes and exit

This solved similar problems on my machine with multiple disks and partitions.

Gps2010 · February 16, 2018, 3:47pm


Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x2b6d04f2

Device     Boot  Start       End   Sectors   Size Id Type
/dev/sda1  *      2048    206847    204800   100M  7 HPFS/NTFS/exFAT
/dev/sda2       206848 976771071 976564224 465.7G  7 HPFS/NTFS/exFAT


Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00083323

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sdb1  *          2048 1881843711 1881841664 897.3G 83 Linux
/dev/sdb2       1881843712 1945331711   63488000  30.3G 83 Linux
/dev/sdb3       1945331712 1953523711    8192000   3.9G 82 Linux swap / Solaris


Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x48e3d6ef

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sdc1           2048   4208639   4206592     2G 82 Linux swap / Solaris
/dev/sdc2  *     4208640  46153727  41945088    20G 83 Linux
/dev/sdc3       46153728 976773119 930619392 443.8G 83 Linux

sda = Win7
sdb = leap 43.3
sdc = leap 42.1

All three OS have their own harddisk.

leap 42.3 yast
http://i.imgur.com/ImuuMOa.png](https://imgur.com/ImuuMOa)

http://i.imgur.com/16ZcLEa.png](https://imgur.com/16ZcLEa)

http://i.imgur.com/t9cfZQf.png](https://imgur.com/t9cfZQf)

Gps2010 · February 16, 2018, 3:48pm

leap 42.1 yast.

http://i.imgur.com/iRkS2kH.png](https://imgur.com/iRkS2kH)

http://i.imgur.com/q4ttbBU.png](https://imgur.com/q4ttbBU)

http://i.imgur.com/HcMHNdG.png](https://imgur.com/HcMHNdG)

I have no idea what the default setting is or should be.
I do know, I have allot of history, and I would like to do some cleaning up (grub).

leap 42.3 is an updated leap 42.2, I used the zypper command for that. That update ended with a grub error.
I am 99.9 % sure that the cause of that grub error was the history of previous installs, maybe even back to opensuse 11.3.

karlmistelberger · February 16, 2018, 7:07pm

Checked against my working configuration and found different settings of boot loader location:

Boot from master boot record: unchecked
Boot from root partition: checked
Custom boot partion: unchecked

Try the above, quit Yast2 by clicking ok and reboot.

karlmistelberger · February 16, 2018, 7:24pm

Missed optional kernel command line parameter: splash=silent quiet showopts

Gps2010 · February 16, 2018, 9:46pm

You’re pc is dual boot with windows ?

I removed those comments, but it did not have the effect I was hoping for. I might have to uninstall plytmouth to achieve that. or hit escape during grub.
( see what is going on during boot up )

I have already added them back though. They are not that important, in relation to my problem.

gogalthorp · February 16, 2018, 10:25pm

Since you want 42.3 to be the controlling OS…

BIOS/UEFI should be set to boot from sdb (the one with 42.3) you set MBR code to generic so the boot flag counts

Unless you did something really weird sdb2 should be your root and thus the boot partition the flag is set wrong on sdb1 which appears to be the home partition

Gps2010 · February 17, 2018, 1:05am

Thank you, that even makes sense to me
I tried a few things, first only change sdb1 to sdb2, and then some more.
but …
I am starting to see a pattern, yast from 43.3 does nothing to the boot sequence, it seems I can change what ever I want, it wont affect grub.

Just some weird idea I had, is it possible?

What if I boot 42.1 and uninstall grub, then boot 43.3 and re install grub ?

My motherboard has a boot option menu, so Assume I can boot all three disk even without grub ?

I also have leap 42.3 install iso on a usb stick, so should be able to boot 43.3 that way too ?

gogalthorp · February 17, 2018, 2:08am

No…

You have generic code in MBR that means that the grub boot code is installed in the first sectors of the boot drive in this case root / what happens is the BIOS/UEFI code goes first to the MBR and runs the code there in this case it is generic and thus looks for the partition that has the boot flag set where it runs the code embedded in the first sectors. In this case that should be the grub boot code which then finds the /boot partition on the drive finds the main grub code which runs the GUI like grub boot screen. Then when a selection of OS is made grub will either start the OS kernel or chain to another OS even on another drive.

So to start this chain the BIOS/UEFI must boot to the drive where the OS lives that you wish to be the boot controller.
In this case each disk could be the boot disk since each has it’s own MBR and boot code setup. You just need to set the boot flag properly and tell the BIOS/UEFI to boot to that disk

Note that you can also install grub boot to the MBR in this case the grub code knows where to look for the rest of the boot chain and a boot flag is not used or needed. In cases where Windows and Linux are on the same drive this can cause problem when Windows decides to install it’s generic code in the MBR but this is not a consideration when each OS is on it’s own drive.

karlmistelberger · February 17, 2018, 6:11am

This does not matter, as your OSs are residing on different, independent drives.

I removed those comments, but it did not have the effect I was hoping for. I might have to uninstall plytmouth to achieve that. or hit escape during grub.
( see what is going on during boot up )

I have already added them back though. They are not that important, in relation to my problem.

Make sure UEFI boots from drive /dev/sdb, see e.g. in ftp://europe.asrock.com/Manual/Z170%20Pro4S.pdf 4.8 Boot Screen, boot priority settings.
Check your kernel command line. Mine is:

linux /boot/vmlinuz-4.15.3-1-default root=UUID=8b190950-c141-4351-9198-7a9592b4fb34  splash=silent quiet showopts

Post your values from /boot/grub2/grub.cfg4.8 Boot Screen

Gps2010 · February 17, 2018, 10:33pm

Been trying a few things, and found out a few things.

My window 7 still boots and works, but burning a dvd fails like it failed with Leap too. ( either dvd burner is dead on arrival, or I just need new dvd , better dvd disks )
Its not a problem related to this topic, and I already made an 42.3 install usb.

After again trying to change setting in yast, I went two steps backward and one step forward.

I do not longer get greeted by grub, windows 7 boots

When I however use my mobo boot option menu, and boot the 42.3 disk, next thing that pops up is grub, asking me if I want to boot 42.3 ( as first option, that’s the step forward) or win 7, or leap 42.1.

Something is messed up.

Question, how hard is it to clean out the mbr of windows7 ? , worse case scenario through win 7 ? ( with windows dvd ? cd ? inserted start something and type fix mbr from the top of my head)
Can I see and read, edit the windows mbr ? with Leap ? I tried google , but cant find a clear answer.

I am not an expert , but I can imagine the windows mbr file to have allot of Linux made entries.
from 11.3 install to 42.3 install, that could cause issues ?

Grub.cfg

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if  -f ${config_directory}/grubenv ]; then
  load_env -f ${config_directory}/grubenv
elif  -s $prefix/grubenv ]; then
  load_env
fi

if  "${env_block}" ] ; then
  load_env -f "${env_block}"
fi

if  "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   if  "${env_block}" ] ; then
     save_env -f "${env_block}" next_entry
   fi
   set boot_once=true
else
   set default="${saved_entry}"
fi

if  x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if  "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if  -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    if  "${env_block}" ] ; then
      save_env -f "${env_block}" saved_entry
    fi

  fi
}

function load_video {
  if  x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if  x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if  x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 --hint='hd0,msdos2'  c4f60c97-194b-4ffc-83a3-4f7af2b9d608
else
  search --no-floppy --fs-uuid --set=root c4f60c97-194b-4ffc-83a3-4f7af2b9d608
fi
    font="/usr/share/grub2/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos2'
if  x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 --hint='hd0,msdos2'  c4f60c97-194b-4ffc-83a3-4f7af2b9d608
else
  search --no-floppy --fs-uuid --set=root c4f60c97-194b-4ffc-83a3-4f7af2b9d608
fi
insmod gfxmenu
loadfont ($root)/boot/grub2/themes/openSUSE/ascii.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans10.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans12.pf2
loadfont ($root)/boot/grub2/themes/openSUSE/DejaVuSans-Bold14.pf2
insmod png
set theme=($root)/boot/grub2/themes/openSUSE/theme.txt
export theme
if  x${boot_once} = xtrue ]; then
  set timeout=0
elif  x$feature_timeout_style = xy ] ; then
  set timeout_style=menu
  set timeout=8
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
  set timeout=8
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/00_tuned ###
set tuned_params=""
### END /etc/grub.d/00_tuned ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'openSUSE Leap 42.3'  --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-c4f60c97-194b-4ffc-83a3-4f7af2b9d608' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos2'
    if  x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 --hint='hd0,msdos2'  c4f60c97-194b-4ffc-83a3-4f7af2b9d608
    else
      search --no-floppy --fs-uuid --set=root c4f60c97-194b-4ffc-83a3-4f7af2b9d608
    fi
    echo    'Loading Linux 4.4.114-42-default ...'
    linux    /boot/vmlinuz-4.4.114-42-default root=UUID=c4f60c97-194b-4ffc-83a3-4f7af2b9d608  resume=/dev/sdb2splash=silent quiet showopts
    echo    'Loading initial ramdisk ...'
    initrd    /boot/initrd-4.4.114-42-default
}
submenu 'Advanced options for openSUSE Leap 42.3' --hotkey=1 $menuentry_id_option 'gnulinux-advanced-c4f60c97-194b-4ffc-83a3-4f7af2b9d608' {
    menuentry 'openSUSE Leap 42.3, with Linux 4.4.114-42-default' --hotkey=2 --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.114-42-default-advanced-c4f60c97-194b-4ffc-83a3-4f7af2b9d608' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos2'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 --hint='hd0,msdos2'  c4f60c97-194b-4ffc-83a3-4f7af2b9d608
        else
          search --no-floppy --fs-uuid --set=root c4f60c97-194b-4ffc-83a3-4f7af2b9d608
        fi
        echo    'Loading Linux 4.4.114-42-default ...'
        linux    /boot/vmlinuz-4.4.114-42-default root=UUID=c4f60c97-194b-4ffc-83a3-4f7af2b9d608  resume=/dev/sdb2splash=silent quiet showopts
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd-4.4.114-42-default
    }
    menuentry 'openSUSE Leap 42.3, with Linux 4.4.104-18.44-default'  --class opensuse --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.4.104-18.44-default-advanced-c4f60c97-194b-4ffc-83a3-4f7af2b9d608' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos2'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 --hint='hd0,msdos2'  c4f60c97-194b-4ffc-83a3-4f7af2b9d608
        else
          search --no-floppy --fs-uuid --set=root c4f60c97-194b-4ffc-83a3-4f7af2b9d608
        fi
        echo    'Loading Linux 4.4.104-18.44-default ...'
        linux    /boot/vmlinuz-4.4.104-18.44-default root=UUID=c4f60c97-194b-4ffc-83a3-4f7af2b9d608  resume=/dev/sdb2splash=silent quiet showopts
        echo    'Loading initial ramdisk ...'
        initrd    /boot/initrd-4.4.104-18.44-default
    }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-807E884F7E883FC0' {
    insmod part_msdos
    insmod ntfs
    set root='hd0,msdos1'
    if  x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  807E884F7E883FC0
    else
      search --no-floppy --fs-uuid --set=root 807E884F7E883FC0
    fi
    parttool ${root} hidden-
    chainloader +1
}
menuentry 'openSUSE 42.1 (x86_64) (on /dev/sdc2)' --class suse --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-d7f4b56d-4dd4-436c-853e-1df028aea008' {
    insmod part_msdos
    insmod ext2
    set root='hd2,msdos2'
    if  x$feature_platform_search_hint = xy ]; then
      search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos2 --hint-efi=hd2,msdos2 --hint-baremetal=ahci2,msdos2  d7f4b56d-4dd4-436c-853e-1df028aea008
    else
      search --no-floppy --fs-uuid --set=root d7f4b56d-4dd4-436c-853e-1df028aea008
    fi
    linux /boot/vmlinuz-4.1.39-56-default root=UUID=d7f4b56d-4dd4-436c-853e-1df028aea008 resume=/dev/disk/by-uuid/898bf52e-faf9-4a5a-90ea-1cea63c290cc splash=silent quiet showopts
    initrd /boot/initrd-4.1.39-56-default
}
submenu 'Advanced options for openSUSE 42.1 (x86_64) (on /dev/sdc2)' $menuentry_id_option 'osprober-gnulinux-advanced-d7f4b56d-4dd4-436c-853e-1df028aea008' {
    menuentry 'openSUSE Leap 42.1 (on /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.1.39-56-default--d7f4b56d-4dd4-436c-853e-1df028aea008' {
        insmod part_msdos
        insmod ext2
        set root='hd2,msdos2'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos2 --hint-efi=hd2,msdos2 --hint-baremetal=ahci2,msdos2  d7f4b56d-4dd4-436c-853e-1df028aea008
        else
          search --no-floppy --fs-uuid --set=root d7f4b56d-4dd4-436c-853e-1df028aea008
        fi
        linux /boot/vmlinuz-4.1.39-56-default root=UUID=d7f4b56d-4dd4-436c-853e-1df028aea008 resume=/dev/disk/by-uuid/898bf52e-faf9-4a5a-90ea-1cea63c290cc splash=silent quiet showopts
        initrd /boot/initrd-4.1.39-56-default
    }
    menuentry 'openSUSE Leap 42.1, met Linux 4.1.39-56-default (on /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.1.39-56-default--d7f4b56d-4dd4-436c-853e-1df028aea008' {
        insmod part_msdos
        insmod ext2
        set root='hd2,msdos2'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos2 --hint-efi=hd2,msdos2 --hint-baremetal=ahci2,msdos2  d7f4b56d-4dd4-436c-853e-1df028aea008
        else
          search --no-floppy --fs-uuid --set=root d7f4b56d-4dd4-436c-853e-1df028aea008
        fi
        linux /boot/vmlinuz-4.1.39-56-default root=UUID=d7f4b56d-4dd4-436c-853e-1df028aea008 resume=/dev/disk/by-uuid/898bf52e-faf9-4a5a-90ea-1cea63c290cc splash=silent quiet showopts
        initrd /boot/initrd-4.1.39-56-default
    }
    menuentry 'openSUSE Leap 42.1, met Linux 4.1.15-8-default (on /dev/sdc2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.1.15-8-default--d7f4b56d-4dd4-436c-853e-1df028aea008' {
        insmod part_msdos
        insmod ext2
        set root='hd2,msdos2'
        if  x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd2,msdos2 --hint-efi=hd2,msdos2 --hint-baremetal=ahci2,msdos2  d7f4b56d-4dd4-436c-853e-1df028aea008
        else
          search --no-floppy --fs-uuid --set=root d7f4b56d-4dd4-436c-853e-1df028aea008
        fi
        linux /boot/vmlinuz-4.1.15-8-default root=UUID=d7f4b56d-4dd4-436c-853e-1df028aea008 resume=/dev/disk/by-uuid/898bf52e-faf9-4a5a-90ea-1cea63c290cc splash=silent quiet showopts
        initrd /boot/initrd-4.1.15-8-default
    }
}

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if  -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif  -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

### BEGIN /etc/grub.d/80_suse_btrfs_snapshot ###
### END /etc/grub.d/80_suse_btrfs_snapshot ###

### BEGIN /etc/grub.d/90_persistent ###
### END /etc/grub.d/90_persistent ###

### BEGIN /etc/grub.d/95_textmode ###
### END /etc/grub.d/95_textmode ###

gogalthorp · February 17, 2018, 10:51pm

The MBR is for Windows is on the Windows disk. But that is not needed if chaining from grub from another disk or even the same disk. You only need that MBR if you boot Windows from the the BIOS/UEFI. When chaining to a different OS from grub the MBR step is skipped. The boot goes straight to the partition that has been discovered to be that OS and starts running the code at the beginning of the partition. There are Windows rescue disks available from MS if it is some how really broken

You say “something is messed up” but don’t tell use what???

So you got to the 42.3 grub boot screen then what? What works what does not.

Gps2010 · February 17, 2018, 11:47pm

The situation as it is now, when I start my pc , the grub screen does not show, and windows 7 boots.
My mobo has a feature though, if I hit F8 during boot, I get a boot option menu, and can choose what disk I want to boot. ( as far as I know this works for all asus motherboards )

Then I choose the leap 42.3 disk and hit enter, after this I do get a grub screen, with 42.3 listed first.
I am thinking of disconnecting the old leap 42.1 hard disk, and try again.

I am posting this with leap 42.3, booted with help of the motherboard.

So there seem to be a correct grub entry, on the leap 42.3 disk, but for some reason when I start my pc, its not used.

I am thinking of disconnecting the leap 42.1 disk and try again.

gogalthorp · February 17, 2018, 11:57pm

There should be an option to set the default boot disk in the BIOS