Bug 80723

Summary: Grub doesn't install on all disks of a software raid device automatically
Product: [Retired] Red Hat Linux Reporter: Hansjoerg Maurer <hansjoerg.maurer>
Component: grubAssignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:50:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hansjoerg Maurer 2002-12-30 15:01:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518
Netscape6/6.2.3

Description of problem:
After installing /boot and / on a software Raid1 device, I recognized, that grub
is only installed on one of the disks of the raid array.
I one disk fails, the system won't boot any more

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Install /boot and / on a software raid1 system (2 disks)
2.halt system and plug out one disk
3.try to reboot
    

Actual Results:  system doesn't boot any more

Expected Results:  system should boot from second disk

Additional info:

It is possible to install it manually on both disks by entering the following
commands (in my case).
But grub should do this automatically or ther should be a note, that the
bootloades is only installed on one disk.
Otherwise the redundancy of a raid 1 system is not reached

grub
device (hd0) /dev/hda
root (hd0,1)
install /grub/stage1 <*> (hd0) /grub/e2fs_stage1_5 /grub/stage2 /grub/grub.conf
device (hd0) /dev/hdb
root (hd0,1)
install /grub/stage1 <*> (hd0) /grub/e2fs_stage1_5 /grub/stage2 /grub/grub.conf

Comment 1 Jeremy Katz 2002-12-30 18:24:51 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:50:47 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.