Bug 375173

Summary: Yast claims falsely that grub can't be installed
Product: [openSUSE] openSUSE 11.0 Reporter: Volker Kuhlmann <bugz57>
Component: InstallationAssignee: Jozef Uhliarik <juhliarik>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: bugz57
Version: Alpha 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Yast log just before just before initial reboot

Description Volker Kuhlmann 2008-03-29 09:54:20 UTC
System with a RAID1 setup like this:

Disk /dev/sda: 80.0 GB, 80060424192 bytes
   Device Boot      Start         End      Blocks   Id  System
/dev/sda2              51         150      803250   82  Linux swap / Solaris
/dev/sda3   *         151        9733    76975447+   5  Extended
/dev/sda7            1291        1918     5044378+  fd  Linux raid autodetect

md2 : active raid1 sda7[0]
      5044288 blocks [2/1] [U_]

(Yes there is only 1 disk in there.)

The suggested grub installation comes up with a red "can't be done", which is nonsense. Explicitly, I set things to install grub in MBR, install generic boot loader, and use sda7 as root device (for loading menu.lst and the kernel from).
System rootfs is md2.

Once upon a time a SuSE 8.x or 9.x was able to configure this (install grub correctly on both disks of a RAID1), I'd really like to see this working again.

I had to fix up the broken syntax of the yast-generated grub config files too, after that, the config files worked although the installer kept its opinion of "can't install this boot loader" in red. I'd attach a screen shot if yast hadn't saved an empty PNG instead.
Comment 1 Volker Kuhlmann 2008-03-29 09:55:49 UTC
Created attachment 204798 [details]
Yast log just before just before initial reboot
Comment 2 Jozef Uhliarik 2008-03-31 14:30:03 UTC
It is duplicated of bug# 374365

*** This bug has been marked as a duplicate of bug 374365 ***