Bug 10916
Summary: | Cannot create Linux partition on drive with existing NTFS | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David Lawrence <dkl> |
Component: | anaconda | Assignee: | David Lawrence <dkl> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-04-19 19:44:02 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
David Lawrence
2000-04-19 14:28:11 UTC
This is definitely not the problem that you were seeing in 6.1. The problem which is causing this message with the 6.2 installation is that you are attempting to put the /boot partition outside of the 1024 cylinder limit. The installer is complaining because under this condition, you will not be able to boot linux. There are a couple of options that you can try. You can attempt to create a small partition (something like 16-32M) right at the end of the NTFS partition and assign this as root. This will work fine, depending on the size of the NTFS partition. In other words, as long as that new partition lies below the 1024 cylinder limit, this solution will work for you. Once you have that partition defined, you can create the other partitions that you would like on your system. If you are not going to be able to create a partition below the 1024 cylinder limit, then you are going to have to use a thrid-party utility to create space below this 1024 cylinder limit. I read on freshmeat (4/26) that lilo 0.21.4.2 can go up to 2 TB Joe There seems to be an error... I am listed as the originator of this bug... but I was not. You may want to check and see if you can find the original reporter of this bug. |