Red Hat Bugzilla – Bug 239626
F7T4 RAID1/LVM Install Issues - Empty /boot, /, /var
Last modified: 2007-11-30 17:12:04 EST
Description of problem:
Installing F7T4 over an FC6 install that utilizes software RAID1 and LVM seems
to work flawlessly, but after clicking Reboot button system ends up at grub
prompt. Inspection shows empty /boot (ext3), /var (RAID1), and / (RAID1)
Version-Release number of selected component (if applicable):
Seems to be consistent; same result from two attempts.
Steps to Reproduce:
1. Install FC6 Re-Spin to match attached disk, RAID, and LVM layout.
2. Install F7T4 over the top of it using same layout. Choose to reformat all
partitions except non-OS data partitions, /opt, and /home. Install should
3. Click Reboot button.
Install seems to finish without issue. Reboot results in the grub prompt.
Several key partitions are empty (/, /boot, /var).
Reboot after install should result in the system booting and the First Time boot
MB: Asus A7V600
CPU: AMD Athlon XP3000+
RAM: 1.5 GB DDR
HD1: Samsung SP1213C 120GB SATA (/dev/sda)
HD2: Samsung SP1213C 120GB SATA (/dev/sdb)
HD3: WDC 80GB IDE (/dev/hda)
CD1: Plextor PX-712A (/dev/hdc)
CD2: Lite-On LTR-32123S (/dev/hdd)
Video: Gainward GeForce2 Ti AGP
Created attachment 154442 [details]
Disk Layout Info
Can you grab /var/log/anaconda* and attach them here?
(In reply to comment #2)
> Can you grab /var/log/anaconda* and attach them here?
Interesting is that I don't have any files that match /var/log/anaconda*. I
performed the install two more times last night and the behaviour was somewhat
different that what I saw originally. This time, the install never happens. It
gets to the point where the install should start (post partitioning and PKG
selection) and it pops up this error:
Error mounting device Volume02/lv_images as /prod/images: No such file or
This most likely means this partition has not been formatted.
Press OK to reboot your system.
This directory was not formatted and should not have been. I contains existing
data files that were supposed to be preserved by the install.
I'm guessing that this is the root cause of the behavior that I originally
I think I've somewhat similar test case:
Using Fedora 7 KDE Live CD i386, when I choose to install /boot partition plus
LVM based /, /usr, /var, /home etc., the installer is unhappy with / LV with
lesser than ~4GB, an indication (to me) installer is unable to understand that
besides / LV there are other LVs & thus / LV could be a smaller LV.
So I had to install it using only / LV (~4GB). I've the system running fine now.
I'm happy to provide any other info needed. Also, this installation problem is
rather easy to reproduce.
This could be due to messing up the order for mounting partition requests. I
did some work in this area recently. Can you please try F8 test 1 and see if
this is fixed for you?
This appears to be fixed, so I am going to close.