Bug 56452
| Summary: | Need to handle invalid data in lilo.conf better on upgrades | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | stuart boreen <stuart> | ||||||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 7.2 | ||||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2006-02-21 18:48:15 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 61590 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
stuart boreen
2001-11-18 22:52:57 UTC
Created attachment 37903 [details]
anaconda dump to floppy from failed upgrade
katzj, any ideas here? You don't happen to have a copy of the /etc/lilo.conf from prior to the upgrade would you? (it would have been /etc/lilo.conf.rpmsave, but that probably got overwritten on the second upgrade) Created attachment 39104 [details]
lilo.conf from before upgrade
lilo.conf from before backup is available. I was using lilo and had made a custom 2.4.8 kernel. With the install I took RedHat's advice and migrated to grub -- still keeping grub on the 1st sector of boot partition, not the MBR due to sharing with Win2000 I will also show you the lilo.anaconda Created attachment 39105 [details]
lilo.conf.anaconda
A similar problem is when doing a "fresh" install over a previous install. If you used lilo on the previous redhat, and install grub, the MBR doesn't get wiped, grub goes into the first partition, and at boot it hangs on half a lilo (LI). The last thing reported we can't do anything about (though we handle upgrade bootloader stuff differently now). The others are due to quotes in the lilo.conf and we handle that better now in CVS Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |