Bug 499165

Summary: grub fails to write bootrecord on dmraid controlled disk
Product: [Fedora] Fedora Reporter: Winfrid Tschiedel <Winfrid.Tschiedel>
Component: grubAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: gasmith, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 12:22:32 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 Winfrid Tschiedel 2009-05-05 13:59:19 UTC
Description of problem:

On a system with ICH10R and a RAID1 I cannot write a new bootrecord with grub


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

grub-0.97-48.fc11.x86_64


How reproducible:
always


Steps to Reproduce:
1. Install fedora 11 preview on a system with ICH10R and Intelfirmware
   and RAID1
2. Create a new bootrecord with grub

  
Actual results:

grub
Probing devices to guess BIOS drives. This may take a long time.


    GNU GRUB  version 0.97  (640K lower / 3072K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> device (hd0,2) /dev/mapper/isw_ibhajaede_Volume0p3
device (hd0,2) /dev/mapper/isw_ibhajaede_Volume0p3
grub> device (hd0) /dev/mapper/isw_ibhajaede_Volume0
device (hd0) /dev/mapper/isw_ibhajaede_Volume0
grub> root (hd0,2)
root (hd0,2)

Error 18: Selected cylinder exceeds maximum supported by BIOS
grub> quit
quit



Expected results:
Successful creation of a new bootrecord


Additional info:

There was no problem to create later a new bootrecord with an alternate 
linuxdistribution (SLED 11) on the same system.

Comment 1 Bug Zapper 2009-06-09 15:10:43 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2010-04-27 14:08:00 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-06-28 12:22:32 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.