Bug 21573
| Summary: | Installer does not detect duplicate LILO labels | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Stephen Rasku <redhat> | ||||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 7.0 | ||||||||
| 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-09-18 19:34: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: | |||||||||
| Attachments: |
|
||||||||
Something strange happened in your upgrade in that it's booting your old kernel. Did you boot off an old bootdisk? What does your /etc/lilo.conf say? Assigining to the installer, since that's the most likely place this happened. Created attachment 5948 [details]
lilo.conf after upgrade to RH7
Created attachment 5949 [details]
DIfferences from previous version of lilo.conf
I have attached the lilo.conf created for RH7 as well as the differences from the previous version. When specifying the name for my other partition, I changed it from "dos" to "nt". This creates a duplicate label and LILO doesn't like it. It looks like the installer isn't smart enough to detect this problem. When I removed the duplicate label, and re-ran lilo. The computer booted fine. Was this a GUI or TUI install? GUI install. I have reproduced this bug and I'm looking into it further. Actually, the problem can be demonstrated in an even simpler way. If you do an install of RHL 7 and change the lilo label from 'linux' to something else, after reboot you will have a lilo.conf file that has been concatenated to itself. This, of course, leaves you with an unbootable machine. Ok, for some reason I can't reproduce the behavior that I was seeing yesterday with the exact same tree. The problem with upgrading the kernel version seems to be fixed. However, changing the dos label to something else, like 'windows' now results in duplicate entries...that is, there's the original entry for http://www.news.com/'dos' and a new one for 'windows'. Lilo works fine with the duplicate labels...it doesn't hurt anything, but it is annoying. However, since it isn't a critical bug, I'm reluctant to fix it at this point. Deferring to a future release. Uhh, I don't know what voodoo bugzilla did with my last post, but the hyperlink in there was not supposed to be there. What I meant was when you change the label from dos to windows, you get an entry for both in the resulting lilo.conf file. This should be fixed as of Red Hat Linux 7.2 |
I just upgraded from 6.2 and 7.0 and modutils isn't finding modules.dep. I see the following error in /var/log/messages: modprobe: modprobe: Can't open dependencies file /lib/modules/2.2.14-5.0/modules.dep (No such file or directory) The specified directory doesn't exist but /lib/modules/{2.0.36-0.7,2.2.5-15,2.2.16-22}/modules.dep do exist. /etc/issue says the kernel version is 2.2.14-5.0 but that doesn't exist on my system. The release notes say that the kernel version is 2.2.16. I don't know how it is deciding to search for 2.2.14-5.0.