Bug 773576

Summary: Menu.lst file badly generated while migrating from 12.1
Product: [openSUSE] openSUSE 12.2 Reporter: Forgotten User fRmEabLy0D <forgotten_fRmEabLy0D>
Component: YaST2Assignee: Steffen Winterfeldt <snwint>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: forgotten_ZQyl6W2tr3, ismail, joachim
Version: Beta 2Flags: snwint: needinfo? (snwint)
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 12.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: The original generated file
All content of /var/log/Yast2

Description Forgotten User fRmEabLy0D 2012-07-29 22:35:05 UTC
Created attachment 500353 [details]
The original generated file

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20100101 Firefox/13.0.1

Hello,

I upgrade today from 12.1 to 12.2 and I get a problem with the generation of the GRUB config file "menu.lst".
Some installation were badly generated in the first lines only :

###Don't change this comment - YaST2 identifier: Original name: xen###
title Xen -- openSUSE 12.2 - 3.4.4-1.1
    kernel (hd0)/boot/xen.gz vga=mode-0x345 dom0_mem=2048M cpufreq=xen cpuidle
    module (hd0)/boot/vmlinuz-3.4.4-1.1-xen root=/dev/sdc1 splash=silent noresume showopts CPUFREQ=no
    module (hd0)/boot/initrd-3.4.4-1.1-xen

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.2 - 3.4.4-1.1
    kernel (hd0)/boot/vmlinuz-3.4.4-1.1-desktop root=/dev/sdc1 splash=silent quiet elevator=cfq  video=1920x1200 showopts vga=0x355
    initrd (hd0)/boot/initrd-3.4.4-1.1-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.2 - 3.4.4-1.1
    kernel (hd0)/boot/vmlinuz-3.4.4-1.1-desktop root=/dev/sdc1 showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x355
    initrd (hd0)/boot/initrd-3.4.4-1.1-desktop

###Don't change this comment - YaST2 identifier: Original name: linux###
title GNU GRUB 2 -- openSUSE 12.2 - GNU GRUB 2
    kernel (hd0)/boot/grub2/core.img root=/dev/sdc1 splash=silent quiet elevator=cfq  video=1920x1200 showopts vga=0x355

The disk is referenced as "hd0" instaed of "hd0,0" and the system can't boot.
After a simple repair the system boots OK.

I join a copy of the file done before any changes were made.






Reproducible: Always

Steps to Reproduce:
1) Migrate from 12.1
2) the system does not reboot after installation with messages like :
"can't mount partition" ...
Comment 1 Forgotten User fRmEabLy0D 2012-07-29 22:37:07 UTC
Some lines (all end of the file) were generated with the right disk references "hd0,0".
The device map is OK.
Comment 2 Steffen Winterfeldt 2012-07-31 06:31:10 UTC
Please add logs (all of /var/log/YaST2).
Comment 3 Forgotten User fRmEabLy0D 2012-07-31 20:55:44 UTC
Created attachment 500618 [details]
All content of /var/log/Yast2

Tar from /var/log/Yast2 done with :

/var/log/YaST2# tar -cvzf /var/tmp/yast2.tar.gz ./*
Comment 4 Steffen Winterfeldt 2012-08-02 13:19:41 UTC
Somehow the udev update causes udevd not to be restarted properly. How did
you do the update? Booted from a 12.2 DVD?
Comment 5 Forgotten User fRmEabLy0D 2012-08-02 17:26:21 UTC
Hello,

Yes I boot from a 12.2 DVD.

Regards

JP Pozzi
Comment 6 Forgotten User ZQyl6W2tr3 2012-08-13 13:51:06 UTC
On 2012-08-13, I saw a similar problem when upgrading my OpenSuSE 12.1 to 12.2rc2.

All references to grub boot files (kernel and initrd) are to (hd0) and not (hd0,0).  By altering the drive reference from (hd0) to (hd0,0) I was able to boot up successfully; but can no longer boot the system unattended.
--
James Tullett
Comment 7 Ismail Dönmez 2012-08-23 12:50:54 UTC
Any news on this one?
Comment 8 Joachim Ziebs 2012-09-07 19:52:49 UTC
Same happened here with an update from 12.1 to 12.2. Update went via DVD.
I was able to boot my system after changing to "hd0,0". However, I have a strange entry in my Grub menu that won't boot even then.

---
# Modified by YaST2. Last modification on Fr Sep  7 15:56:34 CEST 2012
# 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,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.2 - 3.4.6-2.10
    kernel (hd0,0)/vmlinuz-3.4.6-2.10-desktop root=/dev/system/root resume=/dev/system/swap splash=silent quiet processor.nocst=1 video=1440x900 showopts vga=0x364
    initrd (hd0,0)/initrd-3.4.6-2.10-desktop

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 12.2 - 3.4.6-2.10
    kernel (hd0)/vmlinuz-3.4.6-2.10-desktop root=/dev/system/root showopts apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe vga=0x364
    initrd (hd0)/initrd-3.4.6-2.10-desktop

###Don't change this comment - YaST2 identifier: Original name: linux###
title GNU GRUB 2 -- openSUSE 12.2 - GNU GRUB 2
    kernel (hd0)/grub2/core.img root=/dev/system/root resume=/dev/system/swap splash=silent quiet processor.nocst=1 video=1440x900 showopts vga=0x364

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Diskette
    rootnoverify (fd0)
    chainloader +1
---
Comment 9 Steffen Winterfeldt 2014-10-27 09:12:58 UTC
This was due to wrong udevd restating during package update. This has been solved meanwhile.