Bug 38311
Summary: | Automatic paritioning and disk druid fall if empty partition / previous linux installation is > 1024 cylinders | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mike Zingale <zingale> |
Component: | installer | Assignee: | Brent Fox <bfox> |
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
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: | 2001-05-15 18:37:25 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
Mike Zingale
2001-04-29 15:16:52 UTC
What do you mean by 'fails'? By fails, I mean that disk druid will not allow me to create a /boot partition, as it keeps issueing the > 1024 cylinder error message. I could not find a way to manually partition the disk that would allow me to continue with the RH 7.1 installation process. Basically, I could not get past the partitioning screens. I finally gave up, put in the RH 7.0 CD, rebooted, and it installed without any problems. By fails, I mean that disk druid will not allow me to create a /boot partition, as it keeps issueing the > 1024 cylinder error message. I could not find a way to manually partition the disk that would allow me to continue with the RH 7.1 installation process. Basically, I could not get past the partitioning screens. I finally gave up, put in the RH 7.0 CD, rebooted, and it installed without any problems. By fails, I mean that disk druid will not allow me to create a /boot partition, as it keeps issueing the > 1024 cylinder error message. I could not find a way to manually partition the disk that would allow me to continue with the RH 7.1 installation process. Basically, I could not get past the partitioning screens. I finally gave up, put in the RH 7.0 CD, rebooted, and it installed without any problems. Red Hat Linux 7.0 did not create /boot above the 1024 limit automatically. If it did then this was in error. We never wrote the lba32 option out in the 7.0 installer because we decided the option was too experimental in our experience. In 7.1 we made a slightly different attempt. If you manually partition your drive with fdisk, then assign '/boot' to a partition above the 1024 limit, you should see a message saying to make a boot disk in case the lba32 option does not work. Then when we write out lilo.conf we'll put the lba32 option in the file. So try partitioning manually and see if this works better. I would claim that the RH 7.0 error is a desired feature then. With RH 7.0, the automatic partitioner creates my /boot and / partitions both above 1024 cylinders. The disk druid in RH 7.1 confirmed that the partitions created by RH 7.0 were all above 1024 cylinders. I did try doing the manual partitioning with disk druid in RH 7.1, but if I understand your reply correctly, the installation procedure will only proceed if I use fdisk to create the partitions-- is that correct? I installed RH 7.0 on my system and I will most likely leave it there for a while, as I do not want to go through the trouble of a reinstall again. Unfortunately an upgrade to RH 7.1 also fails on this system for a different reason, but that's another story. I will most likely wait until the next .1 release before trying again. I have read atleast one other report of this problem posted in the question area of linuxtoday.com. Mike The other reference to this problem that I referred to above is at: http://losc.internet.com//read.php?f=13&i=1845&t=1845 Mike That's right. Does the install proceed correctly if you use fdisk to make a /boot above 1024? Closing due to inactivity. Please reopen if you have more information. |