From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Description of problem: I tried to install FC2t2, I partitioned using Disk Druid. I asked for one LVM group, vg00, on a single disk partition with one volume in it called home. On the first boot, it complained "No such file or directory while trying to open /dev/vg00/home" when it tried to fsck it and dropped me to single user maintenance. lvm vgdisplay shows me that vg00 was created, but the directory /dev/vg00 doesn't exist and I get stuff like "/dev/mapper/control: open failed: No such file or directory" For someone who's used to dealing with it, this stuff is easy enough to set up by hand after installing. LVM/RAID support in the installer (Disk Druid?) has had weird quirks like this for a long time. I remember the installer would just crash if I tried to set up RAID in RHL 9, and there was something in RHL 8 also, but I don't remember exactly what it was. Maybe it's time to fix it or take LVM/RAID options out of the installer? Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Install using LVM. Create at least one volume group and one volume inside it. Actual Results: Unbootable system (could not find/fsck the logical volume(s)). Expected Results: Bootable system. Additional info:
I had the same problem. Solution was as follows (at "repair filesystem" stage): - modprobe dm-mod - echo "mkdmnod" | nash - restorecon /dev/mapper/control - lvm vgscan (this has exited with code 5, why?) - lvm vgchange -a y - mount -a - exit after the second reboot everything went fine automatically
this is a duplicate of bug 118787
*** This bug has been marked as a duplicate of 118787 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.