Bug 874365 - 16 terabyte Logical Volume keeps grub from booting
Summary: 16 terabyte Logical Volume keeps grub from booting
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-08 02:34 UTC by joshua
Modified: 2013-08-01 09:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 09:04:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description joshua 2012-11-08 02:34:35 UTC
Description of problem:

Fedora 17 x86_64 install to a massive 84 terabyte megaraid HW raid single drive.

Everything works well.  Here is the gdisk -l output:

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  
   2            4096    175781189631   81.9 TiB    8E00  

... and the lvs output:

# lvs
  LV            VG       Attr     LSize  Pool Origin Data%  Move Log Copy%       
  root_fs       VolGrp01 -wi-ao-- 48.00g                                           
  swap          VolGrp01 -wi-ao-- 32.00g                                           
  tmp_fs        VolGrp01 -wi-ao--  2.00g         


So far, so good... until I create my VMs_nfs_store Logical Volume, of size 16.00 terabytes.  Next boot grub2 refuses to operate, seems to read LVM structures just before displaying menu, never comes back from that, doesn't display menu at all.


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

grub2-2.0-0.38.beta6.fc17.x86_64
grub2-tools-2.0-0.38.beta6.fc17.x86_64

Comment 1 Mads Kiilerich 2012-11-08 10:48:24 UTC
Please try with the final grub 2.0 - for instance with
  yum --releasever=18 upgrade grub2
and install and mkconfig. That will give an indication whether a update/backport will fix be a viable solution.

Comment 2 joshua 2012-11-08 20:25:44 UTC
Yes, that works!

grub2-2.00-12.fc18.x86_64 fixes the issue.

Can you take this or the upcoming final version of grub2 from F18 to F17 ?

Comment 3 Mads Kiilerich 2012-11-08 21:07:16 UTC
The bootloader is a very critical component to update. I doubt the package maintainer wants to update it in f17 ... but this is one argument for doing it.

Comment 4 Fedora End Of Life 2013-07-04 02:40:17 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 5 Fedora End Of Life 2013-08-01 09:04:25 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.


Note You need to log in before you can comment on or make changes to this bug.