Bug 526822 - Installer didn't install boot loader if /boot is on mdraid1
Summary: Installer didn't install boot loader if /boot is on mdraid1
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Radek Vykydal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-01 21:15 UTC by Alexey Torkhov
Modified: 2010-02-23 19:34 UTC (History)
2 users (show)

Fixed In Version: anaconda-12.36-1
Clone Of:
Environment:
Last Closed: 2010-02-23 19:34:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
anaconda.log (128.19 KB, text/plain)
2009-10-01 21:15 UTC, Alexey Torkhov 		no flags Details
program.log (11.01 KB, text/plain)
2009-10-01 21:17 UTC, Alexey Torkhov 		no flags Details
storage.log (209.24 KB, text/plain)
2009-10-01 21:18 UTC, Alexey Torkhov 		no flags Details
View All

Description Alexey Torkhov 2009-10-01 21:15:17 UTC 
Created attachment 363396 [details]
anaconda.log

Description of problem:
I performed installation and anaconda did not install bootloader properly.

Partitioning was for 2 disks:
/boot on raid1
lvm with / and /home on raid1
swap on raid0

This is perhaps have connection with bug #526789 (same installation).

Version-Release number of selected component (if applicable):
anaconda-12.32-1.fc12.i686
Comment 1 Alexey Torkhov 2009-10-01 21:17:37 UTC 
Created attachment 363397 [details]
program.log
Comment 2 Alexey Torkhov 2009-10-01 21:18:14 UTC 
Created attachment 363398 [details]
storage.log
Comment 3 Hans de Goede 2009-10-02 07:52:56 UTC 
Radek has been working on some fixes for bootloader stuff with /boot on mdraid1, assigning to him.
Comment 4 Radek Vykydal 2009-10-02 13:09:17 UTC 
I guess you were installing bootloader on boot partition, that is /dev/md0 (it is default option if I am not mistaken). Anaconda used to install in mbrs of both members in such a case, but it has changed with commit 45a7048e5f56316e052e4699b5ec70aa291ddd5e. So bootloader is probably correctly installed in /dev/md0 (that is /dev/vda1 and /dev/vdb1). The question is if boot partition is good default bootloader target.
Comment 5 Alexey Torkhov 2009-10-02 13:22:29 UTC 
Right, seems I was installing it in boot partition. I was intending to setup on mbr, just selected the default option.
It was new clear disk image, so perhaps there was clean mbr.
Comment 6 Hans de Goede 2009-10-02 13:31:46 UTC 
(In reply to comment #4)
> I guess you were installing bootloader on boot partition, that is /dev/md0 (it
> is default option if I am not mistaken). Anaconda used to install in mbrs of
> both members in such a case, but it has changed with commit
> 45a7048e5f56316e052e4699b5ec70aa291ddd5e. So bootloader is probably correctly
> installed in /dev/md0 (that is /dev/vda1 and /dev/vdb1). The question is if
> boot partition is good default bootloader target.  

Right, the partition not the mbr used to be the default as we used to only install grub to one disk in the mbr case, with the patch you've got queued up this is fixed and we should make mbr the default. We should do this before RHEL-6 I believe.

Making the mbr the default should be easy, currently there actually is some special case code to not make the mbr be the default in the mdraid1 /boot case, remove that code and done :)
Comment 7 Radek Vykydal 2009-10-08 15:14:33 UTC 
Default bootloader target for mdraid1 /boot device was changed back to mbr.
Comment 8 Bug Zapper 2009-11-16 13:10:50 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Note You need to log in before you can comment on or make changes to this bug.