Bug 432295

Summary:	installation sets up wrong disk order for GRUB
Product:	[openSUSE] openSUSE 11.1	Reporter:	Frank-Michael Fischer <fmfischer>
Component:	Installation	Assignee:	Jozef Uhliarik <juhliarik>
Status:	RESOLVED INVALID	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P5 - None	CC:	dmacvicar, jreidinger, kontakt
Version:	Beta 2
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:	428119
Bug Blocks:

Description Frank-Michael Fischer 2008-10-04 07:53:19 UTC

+++ This bug was initially created as a clone of Bug #428119 +++

I've installed Beta2 on a machine with 11.0 on it. Here is the menu.lst of the original 11.0 installation:

# Modified by YaST2. Last modification on Thu Sep 11 13:27:34 CEST 2008
default 0
timeout 8
gfxmenu (hd2,0)/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.0 - 2.6.25.16-0.1
    root (hd2,0)
    kernel /vmlinuz-2.6.25.16-0.1-default root=/dev/system/linux resume=/dev/system/swap splash=0 showopts vga=0x31a
    initrd /initrd-2.6.25.16-0.1-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.0 - 2.6.25.16-0.1
    root (hd2,0)
    kernel /vmlinuz-2.6.25.16-0.1-default root=/dev/system/linux showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
    initrd /initrd-2.6.25.16-0.1-default

###Don't change this comment - YaST2 identifier: Original name: linux-2.6.25.5-1.1-default###
title openSUSE 11.0
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-default root=/dev/system/linux resume=/dev/system/swap splash=0 showopts vga=0x31a
    initrd /initrd-2.6.25.5-1.1-default

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Diskette
    rootnoverify (hd0,0)
    chainloader (fd0)+1

###Don't change this comment - YaST2 identifier: Original name: failsafe-2.6.25.5-1.1-default###
title Failsafe -- openSUSE 11.0
    root (hd0,0)
    kernel /vmlinuz-2.6.25.5-1.1-default root=/dev/system/linux showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x31a
    initrd /initrd-2.6.25.5-1.1-default

Now here is menu.lst after installing Beta2:

# Modified by YaST2. Last modification on Sat Sep 20 13:32:29 UTC 2008
default 0
timeout 8
gfxmenu (hd0,5)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE Beta1 - 2.6.27-rc6-7
    root (hd0,5)
    kernel /boot/vmlinuz-2.6.27-rc6-7-pae root=/dev/disk/by-id/ata-WDC_WD2500BB-98GUC0_WD-WCAL76998618-part6 splash=0 resume=/dev/disk/by-id/ata-WDC_WD2500BB-98GUC0_WD-WCAL76998618-part5 showopts vga=0x31a
    initrd /boot/initrd-2.6.27-rc6-7-pae

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE Beta1 - 2.6.27-rc6-7
    root (hd0,5)
    kernel /boot/vmlinuz-2.6.27-rc6-7-pae root=/dev/disk/by-id/ata-WDC_WD2500BB-98GUC0_WD-WCAL76998618-part6 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off powersaved=off x11failsafe vga=0x31a
    initrd /boot/initrd-2.6.27-rc6-7-pae

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
    rootnoverify (fd0)
    chainloader +1

Meaning: I get no choice for booting the old installation.

And now the Beta 2 device map:

device.map
(hd1)	/dev/disk/by-id/scsi-SATA_SAMSUNG_SV0411NS01RJ20X314898
(fd0)	/dev/fd0
(hd2)	/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y24HTNBE
(hd0)	/dev/disk/by-id/ata-WDC_WD2500BB-98GUC0_WD-WCAL76998618

But the correct order would be:

(hd0)	/dev/disk/by-id/scsi-SATA_SAMSUNG_SV0411NS01RJ20X314898
(fd0)	/dev/fd0
(hd1)	/dev/disk/by-id/scsi-SATA_Maxtor_6Y080P0_Y24HTNBE
(hd2)	/dev/disk/by-id/ata-WDC_WD2500BB-98GUC0_WD-WCAL76998618

Meaning: System won't boot without changing the boot device order manually in BIOS after installation.

Workaround: change boot device order manually in BIOS after installation

Comment 1 Andreas Jaeger 2008-10-04 12:37:52 UTC

note: yast log files are in Bug #428119

Comment 2 Josef Reidinger 2008-10-06 09:27:01 UTC

device map during installation set yast-bootloader.

Comment 3 Jiri Srain 2008-10-06 10:16:22 UTC

You said it: When you change the disk order, the system will boot.

When you do installation, you need to change the boot order in order to boot the CD (or whatever media you install from). This means that YaST has only changed disk order available and it can only guess what it will look like for normal boot.

There is no way to detect the right disk order; the detection is mostly correct, but sometimes fails. For these cases you can change the disks order in the YaST bootloader module GUI.

I'm sorry but we cannot help here.

Comment 4 Frank-Michael Fischer 2008-10-06 10:49:05 UTC

This sounds reasonable, at first glance. However, bug 428119 is then still open. Installation bluntly ignores that there is an existing openSUSE 11.0 installation booting from /dev/disk/by-id/scsi-SATA_SAMSUNG_SV0411NS01RJ20X314898 (mbr). So if installation is incapable of figuring this one out as a matter of principle then you should indeed not fix this bug here. But then you can't also fix bug 428119 at all. Which means: 11.1 ignores existing installations in the boot choices. Is this what we want?

A fix would be at least to include existing installations in menu.lst, so I do not have to merge two menu.lst manually, right?

Comment 5 Jozef Uhliarik 2008-10-06 12:39:27 UTC

Frank the bug #428119 is really different from your bug #432295. Jirka wrote that the bug #432295 (actual bug) is not possible to fix it. I agree with him. You can only manually change order of disks during installation. I am using order by BIOS id and if the order is wrong I am not able to detect it. I am sorry.

Comment 6 Frank-Michael Fischer 2008-10-06 13:44:03 UTC

Tak dobře, let's hope, bug #428119 will get fixed then.