|
Bugzilla – Full Text Bug Listing |
| Summary: | bootloader configuration fails with dmraid | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Hannes Reinecke <hare> |
| Component: | Installation | Assignee: | Alexander Osthof <aosthof> |
| Status: | RESOLVED FIXED | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | aj, aosthof, fhassel, ihno, jplack, suse-beta |
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 217807 | ||
| Bug Blocks: | |||
| Attachments: | y2log of the failed bootloader installation | ||
Created attachment 95564 [details]
y2log of the failed bootloader installation
The y2log file of a 'yast2 bootloader' run.
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 I've fixed my side of things (ie mkinitrd, device-mapper & dmraid), so booting works fine now. Provide the kernel & initrd are loaded. yast2-storage-2.14.4 contains support for partitionable DMRAID devices. Is this fixed now? *ping* -- it most likely isn't. cf. #208076 *** Bug 208076 has been marked as a duplicate of this bug. *** 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. Alex please go ahead As long as this one depends on Bug #217807, I'm blocked. 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. |
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.