Bug 105660

Summary: /boot/grub/menu.lst not correct, if another suse linux present
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Andreas Klein <asklein>
Component: InstallationAssignee: Jiri Srain <jsrain>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: vetter
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast2 logs

Description Andreas Klein 2005-08-18 19:21:06 UTC
Make a new 10.0b2 installation into an empty partition on a machine, where a
SuSE 9.3 is present. 
There will be entries for both systems in /boot/grub/menu.lst with the following
errors:

- The entry for the old SuSE 9.3 is missing an initrd line and the system will
  not be bootable, untill the initrd line is added.

- If 10.0b1 is installed on /dev/sda (1st drive) and the 9.3 is located on
  /dev/hda (2nd drive) the menu.lst will show hd(0,X) for both drives!

Example:
###Don't change this comment - YaST2 identifier: Original name: SUSE LINUX 9.3
(/dev/hda6)###
title SUSE LINUX 9.3 (/dev/hda6) /// this must be kernel (hd1,5)
    kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 vga=0x374 selinux=0 
splash=silent resume=/dev/hda5  showopts
//// Here is the initrd line missing

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
    root (hd0,0)
    kernel /boot/vmlinuz root=/dev/sda1 vga=0x374 selinux=0    resume=/dev/hda5
 splash=silent showopts
    initrd /boot/initrd
Comment 1 Arvin Schnell 2005-08-18 21:06:46 UTC
Please provide YaST2 logs.
Comment 2 Andreas Klein 2005-08-18 21:09:26 UTC
Created attachment 46605 [details]
yast2 logs
Comment 3 Jiri Srain 2005-08-19 07:03:08 UTC
Removed "initrd" is duplicate of bug 104048 and will be fixed in Beta3. 
Comment 4 Jiri Srain 2005-08-19 07:03:28 UTC
*** Bug 105574 has been marked as a duplicate of this bug. ***
Comment 5 Jiri Srain 2005-08-19 07:09:51 UTC
Incorrect device has been fixed, check with Beta3. 
 
Note that it affected only sections with the 'root' statement and device not 
specified in the kernel/initrd command.