Red Hat Bugzilla – Bug 217292
/boot is empty after install
Last modified: 2007-11-30 17:11:50 EST
Description of problem:
I made a respin using anaconda and libdhcp from rawhide and otherwise took the
latest updates from fc6. When I do installs /boot gets reformatted but no grub
or kernels get put there. I am able to make respins successfully using the fc6
version of ananconda. So I am not sure if this is user error, a problem with
ananconda or that the versions of some packages required for the fc7 anaconda
haven't been updated and I used ones from fc6 that were too old.
Version-Release number of selected component (if applicable):
anaconda-184.108.40.206-1 (I built new rpms from the source rpm under fc6 after
installing the fc7 libdchp* stuff to meet a requirement for rebuilding anaconda.
While installing from the respun dvd it happens every time whether doing a text
or graphical install that I have tried. I have been unchecking the office (?)
package selection, but otherwise not doing any customization of packages to be
Steps to Reproduce:
This might be hard for you to do, though you could try doing an install with
rawhide and see if you get the same results. I can't test that yet, because I
don't have more than a couple of the rawhide rpms downloaded.
/boot just contained lost+fond
It should have had a grub directory and some parts of the kernel needed to boot.
I saw some errors in the install log that might or might not be related.
Right at the start was:
error: failed to stat /mnt/sysimage/sys: No such file or directory
I had a lot of errors reporting that /proc didn't get mnounted.
I used two raid partitions for the install, one for /, the other for /boot.
There were other raid partitions on the disks that weren't used in the install.
Can you attach /var/log/anaconda.log?
Created attachment 142385 [details]
anaconda.log from text install
This is from a text based install I was doing to test for the software raid
Created attachment 142386 [details]
anaconda.log from graphical install
Now that I check the timestamps, I am not absolutly sure the previous log was
from a text based install. This one is from a graphical install for sure, since
I made a big oops and wrote over the wrong /dev/md5 array and I clearly
doing that in a graphical install.
/boot is getting mounted onto /mnt/sysimage/boot first, and then / is getting
mounted onto /mnt/sysimage later. So all the grub stuff is being written to
/boot on the root device, not on the boot device. That leaves the boot device
empty when you reboot.
This will be fixed in the next build of anaconda.
Thanks. I'll keep an eye out for the update, retest it when it shows up and
*** Bug 217416 has been marked as a duplicate of this bug. ***
The update still hasn't shown up yet (rawhide's anaconda is still from Nov 30).
Is there someplace I can grab the source, so that I get feedback on the fix back
to you a bit sooner? I tried using anonymous CVS as documented on
http://fedora.redhat.com/About/Projects/anaconda-installer/ but the login
Nevermind about my last comment. CVS works, I was just stupidly copying and
pasting the 3 commands at once, so that the 3rd command was being sent as the
password and causing the login to fail.
Is there a reason the anaconda in the full rawhide tree has not been built since
Nov 30? It would be nice to be able to install again but installing nightly
builds is still blocked due to this.