Bug 786715

Summary:	cannot install onto 4TB drive without LVM
Product:	[Fedora] Fedora	Reporter:	Eric Smith <spacewar>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-03 02:37:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Eric Smith 2012-02-02 08:38:24 UTC

Description of problem:
Tried to install F16 onto a 4TB drive without LLVM, using default partitioning

Version-Release number of selected component (if applicable):
F16 x86_64 release ISO

How reproducible:
100%

Steps to Reproduce:
1. install a 4TB SATA drive
2. boot install DVD
3. tell Anaconda to use entire disk, but NOT to use LVM
 
Actual results:
Error Partitioning
Could not allocate requested partitions:
requested size exceeds maximum allowed.

Expected results:
installation

Additional info:
3TB drives are common, but I don't know whether this error will happen with them.  4TB drives are not yet common, but will be soon, and 4TB and larger RAID volumes are common.

Comment 1 David Lehman 2012-02-02 13:48:50 UTC

Please attach each of the following log files as type plain/text:

 /var/log/anaconda/anaconda.log
 /var/log/anaconda/anaconda.storage.log
 /var/log/anaconda/anaconda.syslog
 /var/log/anaconda/anaconda.program.log


Some detail about the procedure you tried could also be useful. Thanks.

Comment 2 Eric Smith 2012-02-02 16:12:29 UTC

I only have one 4TB SATA drive, and I eventually succeeded in installing F16 on it only by putting the drive on a machine already running F16 from a smaller drive, and partitioning it manually, and then moving it back to the new machine and running the install with it already partitioned.  As a result, I don't have the requested log files, and since the 4TB disk is now in production use, I can't try it again.

However, I originally tried this multiple times and got consistent results.

I don't know what additional details about the procedure you want. I just attemped an install from a DVD burned from the release ISO image, in the usual way, onto the unpartitioned 4TB SATA drive.  I don't think I was doing anything unusual, other than unchecking the "Use LVM" box.

Comment 3 Chris Lumens 2012-02-03 02:37:30 UTC

Without log files, there's really nothing we can do to debug this.  We don't have any of this hardware around to try things out with.  Sorry.

If you are able to reinstall and grab the logs, feel free to reopen.