Bug 49260
Summary: | Can't choose correct dos partition for LILO from installer | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Torsten Schuetze <torsten.schuetze> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-09-27 19:32:19 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
Torsten Schuetze
2001-07-17 14:56:19 UTC
Strange. The installer looks for FAT partitions that are marked as active, so I can't explain why this would happen. Can you send the output of 'fdisk -l /dev/sda'? Okay, here is the output of fdisk -l /dev/sda Disk /dev/sda: 255 heads, 63 sectors, 2221 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 522 4192933+ 7 HPFS/NTFS /dev/sda2 523 2221 13647217+ f Win95 Ext'd (LBA) /dev/sda5 523 1044 4192933+ 7 HPFS/NTFS /dev/sda6 1045 1299 2048256 b Win95 FAT32 /dev/sda7 1300 1758 3686886 7 HPFS/NTFS /dev/sda8 1759 2221 3719016 7 HPFS/NTFS /dev/sda6 has been proposed by anaconda, but /dev/sda1 should be included. Ok, I can explain this behavior. The installer scans for FAT partitions. We don't currently handle NTFS partitions at all in the installer. If your /dev/sda1 partition was FAT instead of NTFS, then things would have gone smoothly. Some people apparently have problems booting NTFS from LILO. So, even if we let you add a boot image manually, it still may not work. We do need some work on the bootloader, but we can't handle it in the current development cycle. We will address this issue in the future, but I'm deferring it for now. This will be handled better, allowing you to add undetected options, for the next release. |