Bug 419911

Summary: Bootloader installation is incorrect when mixing RAID and non-RAID on the same system
Product: [openSUSE] openSUSE 11.0 Reporter: Forgotten User ryiKzbg8PU <forgotten_ryiKzbg8PU>
Component: YaST2Assignee: Jozef Uhliarik <juhliarik>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P2 - High CC: jsrain, mantel
Version: Final   
Target Milestone: ---   
Hardware: 64bit   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast logs

Description Forgotten User ryiKzbg8PU 2008-08-24 19:21:59 UTC
My system has one SATA disk that is non-RAID and was configured to hold the three partitions: /, /boot and swap. In addition to this I have a pair of disks using an HP SATA RAID controller configured to act as a mirror and mounted as /usr/local. Whilst most of the installation worked fine, the bootloader installation failed repeatably. I eventually tracked down the issue to the first disk /dev/sda being omitted from devices.map in the grub configuration causing the installation to be attempted against the wrong disk. Since the target partition was not there, this obviously failed. The work around was to use the option to edit the config files and add in the missing disk to the device map, but obviously this should not be needed. If you'd like any more information let me know.
Comment 1 Cyril Hrubis 2008-09-08 17:43:38 UTC
Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!
Comment 2 Forgotten User ryiKzbg8PU 2008-09-16 21:35:52 UTC
Created attachment 239916 [details]
yast logs

Please find attached the yast logs as requested.
Comment 3 Jiri Srain 2008-10-15 11:54:08 UTC
This bug has been fixed for openSUSE 11.1 Beta3.

When detecting disks order, YaST ignored all individual disks if a DM-RAID was detected.

Please, reopen if Beta3 still does not work for you and attach fresh logs.

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