Bug 67695
Summary: | multiple kernels fail to boot | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Alexander Farley <afarley> |
Component: | grub | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | ||
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: | 2002-07-02 13:13:27 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
Alexander Farley
2002-06-29 20:16:16 UTC
Based on the error, I'm guessing that you have /boot as a separate partition -- you need to specify the initrd as /initrd-foo instead of /boot/initrd-foo because grub's root is set such that it's already looking in the /boot partition. Does this solve the problem? Beautiful. Such a simple solution. Everything works perfectly now. However, souldn't the installer script for the kernel RPM packages be changed to install the initrd images without the "/boot" part. I thought that the default installation creates a boot partition separate from the root partition? They should be properly detecting whether or not you have a separate /boot or not -- what were the contents of your /boot/grub/grub.conf file and what version of the mkinitrd package do you have installed? I am using mkinitrd 3.4.12-1, which looks like the newest version of the package. My /boot/grub/grub.conf file: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda2 # initrd /initrd-version.img #boot=/dev/hda default=2 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.18-5.58) root (hd0,0) kernel /vmlinuz-2.4.18-5.58 ro root=/dev/hda2 initrd (/boot)/initrd-2.4.18-5.58.img title Red Hat Linux (2.4.18-5) root (hd0,0) kernel /vmlinuz-2.4.18-5 ro root=/dev/hda2 initrd /initrd-2.4.18-5.img title Red Hat Linux (2.4.18-3) root (hd0,0) kernel /vmlinuz-2.4.18-3 ro root=/dev/hda2 initrd /initrd-2.4.18-3.img title Red Hat Linux (2.4.17-openmosix2) root (hd0,0) kernel /vmlinuz-2.4.17-openmosix2 ro root=/dev/hda2 initrd (/boot)/initrd-2.4.17-openmosix2.img The boots in parentheses were inserted by the script/mkinitrd and prevented those kernels from booting. When the "/boot" was eliminated the kernels were able to boot up perfectly. mkinitrd was broken in rawhide for this at one point but has since been fixed. |