Bug 736377 - Grub will not work on a drive larger that 1 TB
Summary: Grub will not work on a drive larger that 1 TB
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: grub
Version: 6.1
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-07 14:21 UTC by Steve Simpson
Modified: 2011-09-15 13:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-15 13:42:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Steve Simpson 2011-09-07 14:21:19 UTC 
Description of problem:
See FC bug: https://bugzilla.redhat.com/show_bug.cgi?id=623597

Grub will not load on a disk larger than 1 TB.


Version-Release number of selected component (if applicable):
grub-0.97-70.el6.x86_64

How reproducible:
Very

Steps to Reproduce:
Create a single Raid 5 partition larger than 3 TB & run the default RHEL Install.
  
Actual results:
After reboot it will stop at the "grub>" prompt. When you manually enter grub commands you will get the error:
Error 18: Selected cylinder exceeds maximum supported by BIOS

Expected results:
Grub menu / system login

Additional info:
Comment 2 David Lehman 2011-09-07 14:54:13 UTC 
Which is it? 1TB or 3TB?
Comment 3 Steve Simpson 2011-09-07 15:07:51 UTC 
Please read the referenced FC bug report. I don't know exactly where the limit lies and it may be (somewhat) dependent on the architecture of the (virtual) drive. The initial reporter stated that he had problems with 1.5TB drive. My original configuration was with a 3+TB. My guess is that it is slightly over 1 TB.
Comment 4 Peter Jones 2011-09-15 13:42:13 UTC 
I've successfully used 2TB drives to boot from, so this appears to be a problem with >2TB boot volumes. This is unsupported on BIOS machines.
Note You need to log in before you can comment on or make changes to this bug.