F17 (dracut) can't find root filesystem in LVM volume

[Todd Hesla]

Dear fellow Fedora users,

I just upgraded from F15 to F17, but it won't boot--says it can't find
the root filesystem, which is on a logical volume in an LVM volume group.
(See boot messages below.)  For the record, F15 booted just fine with this
structure.

I know this problem--or at least very similar problems--have been discussed many
times, both in this mailing list, and also in FedoraForum.org.  But none of the
suggestions I have seen so far in either of those places seem to fix my problem.
I did try one suggestion found in the Fedora docs (detailed below) which got me
past the first "bump", only to run into a second problem--this one apparently
involving udev.

So I'm stuck with an unbootable F17 system.  If anyone has any insight into what
might be going on, I'd be very grateful.

Thank you very much.



--- boot messages ---

Cannot open font file True

ata_id[237]: unable to open '$devnode'
ata_id[238]: unable to open '$devnode'

dracut Warning: Unable to process initqueue
dracut Warning: /dev/FedoraVolGroup/RootLogVol does not exist
dracut Warning: /dev/mapper/FedoraVolGroup-RootLogVol does not exist

Dropping to debug shell.

dracut:/# 



If I then enter 'lvm vgchange -ay',
followed by 'exit', the system begins to boot, but then encounters udev errors,
and aborts to emergency mode:



[ 1652.284204] udevd[678]: invalid rule '/etc/udev/rules.d/55-hpmud.rules:31
[ 1652.299298] udevd[678]: unknown key 'sysFS{idVendor} in /etc/udev/rules.d/55
   .
   .
   .
[ xxxx.xxxxxx] kvm: disabled by bios
[ xxxx.xxxxxx] udevd[678]: unknown key 'BUS' in /etc/udev/rules.d/85-pcscd-egate
[ xxxx.xxxxxx] udevd[678]: invalid rule 'etc/udev/rules.d/85-pcscd-egate.rules:
   .
   .
   .
[ xxxx.xxxxxx] udevd[788]: error: can not open 'sys/devices/platform/microcode/
   .
   .
   .
Dependency failed. Aborted start of /home
Dependency failed. Aborted start of Mark the need to relabel after reboot
Dependency failed. Aborted start of Relabel all filesystems, if necessary
Welcome to emergency mode.  ...



What's going on?  And how should I proceed?

Thank you very much.

Regards,

-- 
Todd Hesla