Bug 198104 - bootloader configuration fails with dmraid
Summary: bootloader configuration fails with dmraid
Status: RESOLVED FIXED
: 208076 (view as bug list)
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Installation (show other bugs)
Version: Alpha 3
Hardware: x86 SUSE Other
: P5 - None : Critical with 5 votes (vote)
Target Milestone: ---
Assignee: Alexander Osthof
QA Contact: Stanislav Visnovsky
URL:
Whiteboard:
Keywords:
Depends on: 217807
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-09 12:12 UTC by Hannes Reinecke
Modified: 2006-11-24 14:21 UTC (History)
6 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
y2log of the failed bootloader installation (674.60 KB, text/plain)
2006-08-09 12:14 UTC, Hannes Reinecke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Hannes Reinecke 2006-08-09 12:12:18 UTC
When trying to install on a dmraid system the bootloader configuration fails.

System is setup as follows:

dmraid on /dev/sda & /dev/sdb,
One /boot partition under /dev/mapper/isw_ijebcgcji_Root-part1 (linked to
/dev/disk/by-name/isw_ijebcgcji_Root-part1) and an additional LVM logical volume as root.

After manually activating dmraid the installation works as designed, only the bootloader configuration is not able to detect the layout. Even manually configuring the respective files fails as /etc/grub.conf is always overwritten with wrong values.

/boot/grub/device.map:
(fd0)   /dev/fd0
(hd0)   /dev/disk/by-name/isw_ijebcgcji_Root

/boot/grub/menu.lst:
# Modified by YaST2. Last modification on Fri Jul  7 09:01:30 UTC 2006
color white/blue black/light-gray
default
timeout 8
gfxmenu (hd0,0)/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 10
    root (hd0,0)
    kernel /vmlinuz root=/dev/system/root vga=0x31a      splash=silent showopts
    initrd /initrd

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

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 10
    root (hd0,0)
    kernel /vmlinuz root=/dev/system/root vga=normal showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /initrd

The correct /etc/grub.conf should be:
setup --stage2=/boot/grub/stage2 (hd0) (hd0,0)
quit

The proposed /etc/grub.conf is:
setup --stage2=/boot/grub/stage2 (/dev/sda,0) (/dev/system/dev/mapper/system-root)
quit

Any attempt to modify /etc/grub.conf fails as it'll always be overwritten with incorrect values.
Comment 1 Hannes Reinecke 2006-08-09 12:14:14 UTC
Created attachment 95564 [details]
y2log of the failed bootloader installation

The y2log file of a 'yast2 bootloader' run.
Comment 2 Joachim Plack 2006-08-23 15:45:49 UTC
this code path is currently under complete rewrite.

don´t see the blocking character for 10.2alpha so I set this to critical
and make room for real blockers
Comment 3 Hannes Reinecke 2006-09-05 06:21:01 UTC
I've fixed my side of things (ie mkinitrd, device-mapper & dmraid), so booting works fine now.
Provide the kernel & initrd are loaded.
Comment 4 Thomas Fehr 2006-09-05 17:15:30 UTC
yast2-storage-2.14.4 contains support for partitionable DMRAID devices.
Comment 5 Andreas Jaeger 2006-10-22 14:43:20 UTC
Is this fixed now?
Comment 6 Christoph Thiel 2006-11-04 15:24:19 UTC
*ping* -- it most likely isn't. cf. #208076
Comment 7 Alexander Osthof 2006-11-08 16:42:42 UTC
*** Bug 208076 has been marked as a duplicate of this bug. ***
Comment 8 Alexander Osthof 2006-11-08 17:13:19 UTC
I've recently tested with an openSUSE 10.2 Beta 2: A manual configuration of the bootloader doesn't overwrite the config files anymore.

Nevertheless, the proposed grub.conf still contains the wrong device strings, thus something like "/dev/mapper/sil_agajddbjcefb,0" instead of "hd0,0".

This erroneous behaviour will be fixed ASAP.
Comment 9 Joachim Plack 2006-11-13 13:12:28 UTC
Alex please go ahead
Comment 10 Alexander Osthof 2006-11-13 15:48:56 UTC
As long as this one depends on Bug #217807, I'm blocked.
Comment 11 Alexander Osthof 2006-11-24 14:21:32 UTC
A fix is now in the recently submitted package yast2-bootloader, so in openSUSE 10.2 RC2 this problem shouldn't occur anymore.

Thus, I close this bug FIXED.