Red Hat Bugzilla – Bug 85424
grubby can leave grub.conf empty if /boot is full (system unbootable)
Last modified: 2007-04-18 12:51:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203
Description of problem:
If the /boot partition runs out of space while installing a new kernel then
grubby moves the grub.conf file to grub.conf~ and creates a zero sized grub.conf
When the system is rebooted Grub just drops into the command line.
I'm no grub expert, so I had to use a bootdisk to sort it out.
Version-Release number of selected component (if applicable):
Always (it has happened to me twice - both times when /boot became full)
Steps to Reproduce:
I noticed this while doing kernel development. grubby was being invoked from the
installkernel script during the kernel "make install".
0. Install lots of kernels so /boot is nearly full
1. Compile new kernel
2. Install with kernel "make install", no errors reported
3. Reboot machine
4. Grub drops into the commandline, no boot menu - help!
Expected Results: grubby should do something intelligent when it runs out of
space while creating the ne grub.conf, perhaps by creating it as grub.conf.new &
then only renaming the file once it is happy that it has written all of it.
Alternatively grub could look for "grub.conf~" if grub.conf is empty.
I do not know whether RPM would prevent this from happening through a normal
kernel install, perhaps it checks for the necessary disk space
Fixed for 3.5.51
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.
However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.