Bug 801966

Summary: YasT migration from GRUB2 to GRUB results in unbootable system
Product: [openSUSE] openSUSE Tumbleweed Reporter: Forgotten User xRcrmyYBVX <forgotten_xRcrmyYBVX>
Component: YaST2Assignee: Steffen Winterfeldt <snwint>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P3 - Medium CC: jreidinger
Version: 13.1 Beta 1   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard: GOLD
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs for 1)
y2logs for 2)

Description Forgotten User xRcrmyYBVX 2013-02-04 13:06:45 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17

A fresh install of openSUSE 12.3 Beta 1 with GRUB2 as default.

Go to Yast -> System -> Bootloader and switch to GRUB.
1) Select "Propose new config" leads to a "-kdump" initrd being installed in /boot/grub/menu.lst (while kdump is not installed), also results in unbootable system!
----------
# Modified by YaST2. Last modification on Mon Feb  4 07:45:09 EST 2013
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader

default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 12.3
    root (hd0,1)
    kernel /boot/vmlinuz-3.7.2-1-desktop root=/dev/disk/by-id/ata-VBOX_HARDDISK_VBa6143e10-d16731b9-part2    resume=/dev/disk/by-id/ata-VBOX_HARDDISK_VBa6143e10-d16731b9-part1 splash=silent quiet showopts
    initrd /boot/initrd-3.7.2-1-desktop-kdump

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.3
    root (hd0,1)
    kernel /boot/vmlinuz-3.7.2-1-desktop root=/dev/disk/by-id/ata-VBOX_HARDDISK_VBa6143e10-d16731b9-part2 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset  x11failsafe
    initrd /boot/initrd-3.7.2-1-desktop-kdump

###Don't change this comment - YaST2 identifier: Original name: linux###
title Kernel-3.7.2-1-desktop
    root (hd0,1)
    kernel /boot/vmlinuz-3.7.2-1-desktop root=/dev/disk/by-id/ata-VBOX_HARDDISK_VBa6143e10-d16731b9-part2    resume=/dev/disk/by-id/ata-VBOX_HARDDISK_VBa6143e10-d16731b9-part1 splash=silent quiet showopts
    initrd /boot/initrd-3.7.2-1-desktop
----------



2) Select "Convert current config" results in basically empty /boot/grub/menu.lst and subsequent boot fails:
----------
# Modified by YaST2. Last modification on Mon Feb  4 07:45:08 EST 2013
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader

default 0
timeout 8
##YaST - generic_mbr
##YaST - activate
terminal gfxterm
----------

The first part looks like bnc#786016, where LILO is used.

See y2logs attached for 1) and 2)

Reproducible: Always

Steps to Reproduce:
1. Install default OS12.3
2. Use YaST2 to convert boot loader config from GRUB2 to GRUB

Actual Results:  
Boot broken
Comment 1 Forgotten User xRcrmyYBVX 2013-02-04 13:07:42 UTC
Created attachment 523209 [details]
y2logs for 1)
Comment 2 Forgotten User xRcrmyYBVX 2013-02-04 13:08:08 UTC
Created attachment 523210 [details]
y2logs for 2)
Comment 3 Forgotten User xRcrmyYBVX 2013-02-13 18:27:28 UTC
Actually, on a running system installed with GRUB, the YaST2-bootloader seems to be broken.

Clicking on "Propose new configuration" on an installed system creates an near-empty "menu.lst" file as in case 2) from above. 

Also, the "mkinitrd" command does not seems to create an initrd at all. I remove the current initrd/vmlinuz files, but running "mkinitrd" exists within 1-2 seconds and nothing happens. System is unbootable after reboot.
Comment 4 Josef Reidinger 2016-10-10 12:35:05 UTC
switch back to grub1 nor proposing grub1 is no longer supported. So closing as won't fix.