Bug 37017
Summary: | Installer indicates Win98 drive is corrupt | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Lee A. Wentzel <lawentzel> |
Component: | installer | Assignee: | Brent Fox <bfox> |
Status: | CLOSED WORKSFORME | QA Contact: | Brock Organ <borgan> |
Severity: | high | 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-20 23:52:39 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
Lee A. Wentzel
2001-04-21 20:01:30 UTC
What is the exact wording of the message which indicates the drive is corrupt? Closing due to inactivity. Please reopen if you have more information. I have decided to use a stable version of RH reverting back to 7.0. There is a problem, however I haven't had the time to do your work for you. The exact error indicated the hardrive (hda) was corrupted and would need to be initiallized. It then asked me if I wanted to proceed. I said No. It waited forever and came up with the same error indicating that hda was corrupted and would need to be initiallized and again it asked me if I wanted to proceed. I said no. At that point it found my second hard drive and proceeded to partician it and set it up. When it was done, Lilo didn't even offer me a choice for Windows. RH 7.0 had no problem at all. It sounds like the installer couldn't read the partition table on the disk...that might explain why Lilo didn't give you the option to set up a windows partition, because it didn't find any partitions at all. I can't really explain why this happened, except for the fact the 2.4 kernel is more strict in it's reading of disk geometry. The only thing I can think of to try is booting the installer with the 'linux expert' boot option. This will cause the kernel to be more lenient in it's disk geometry rules. If you feel like trying that, please reopen the bug and tell us if that changed anything. Thanks for your report. |