Red Hat Bugzilla – Bug 64883
7.2 to 7.3 upgrade: no init found
Last modified: 2008-03-06 14:57:03 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; Q312461)
Description of problem:
After doing out of box upgrade, ext3 file systems, where I had used GRUB as 7.2
boot loader, kernel hangs as init= isn't specified.
Kernel boots with following sequence:
Creating root device
Mounting root filesystem
EXT3fs mounted filesystem with ordered data mode
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
two drives are installed: hda and hdb.
GRUB on MBR of hda.
Booting as rescue mode, I can see /hda8 contents (my root partition)as it
Looking at grub.conf I see what I *think* is the right content.
kernel_module ro root=/dev/hda8 hdc=ide-scsi
I've tried both leaving boot loader alone (first time) and subsequently forcing
to grub. (which by the way requires I remove kernel otherwise I'm not allowed
to force a bootloader install if no kernel modules have been installed :-( I
should at least get asked!)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Out of box install
Actual Results: System hangs, unable to boot via floppy or loader image.
Expected Results: It should recognize the 7.2 stuff and work! Near as I can
tell, it's trying to do so as 7.2 and 7.3 grub configs are mostly identical
(less kernel specific versions)
Willing to be contacted if more information needed.
> After doing out of box upgrade
> Steps to Reproduce:
> 1. Out of box install
Install or upgrade?
I assume you've done an upgrade from 7.2. By any chance, have you deleted the
empty /initrd directory on your root partition? If so, mkdir /initrd from rescue
mode and reboot.
Yes, I did mean upgrade ;-)
The initrd directory was missing; I didn't remove it prior to the install as I
did a clean reboot before I began the install. Any clue how it got deleted?
Recreated, and all's well.
Whatever deleted this file, it wasn't the kernel. Assigning to anaconda
as the most likely component subject...
Anything in the upgrade.log about problems with the filesystem package?
Closing due to inactivity, please reopen if you have additional information.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.