Bug 32103
Summary: | Lilo installs broken MBR when | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | drdoc |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | paulmcq |
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-04-23 15:43:47 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
drdoc
2001-03-17 21:46:38 UTC
This error happens anytime I choose not to install lilo during install, regardless of other OS's present or partitioning. Also reproduced on 2 other systems. Did your old kernel get replaced by the new kernel? If this happens then LILO will not suceeded because the old kernel is no longer present. No. The old kernel does not get replaced. If I boot to the v6.2 install via boot floppy and run lilo with the original lilo.conf, I can then boot WinME and 6.2. The intention was that I would add astanza to the v6.2 lilo.conf to boot the v7.0 install. This also works, after editting lilo.conf. The same problem exists if only WinXX or no OS are initially on the machine. RH 7, instead of not installing lilo at all, writes a corrupted MBR. Can you reproduce this with 7.1? I am unable to duplicate this with Red Hat Linux 7.1. Resolving as 'Current Release'. |