FC1 -> Rawhide, LVM2 can't lock disks due to LVM1?

[Mika Hirvonen]

I recently upgraded to Rawhide with yum, and I'm running into problems 
with my LVM setup.
My /boot is ext3, but everything else, including / is using ext3 over 
LVM1. The new kernel (2.6.3-2.1.253.2.1) doesn't seem to find my root 
partition, although it did find and activate my volume group. If I try 
to mount my root manually, mount complains about an invalid block 
device. I can boot using my old kernel (2.4.22-1.2174), though.

I did try to follow the instructions in 
http://www.redhat.com/archives/fedora-test-list/2004-February/msg00208.html 
and made the /etc/lvm directory and tried rebooting with the old kernel, 
but /sbin/lvm vgscan --mknodes complains that it couldn't lock the drives:

--clip--
[root at nightwatch root]# /sbin/lvm vgscan --mknodes
  Reading all physical volumes.  This may take a while...
  /dev/cdrom: open failed: Read-only file system
  /proc/lvm/VGs/disks exists: Is the original LVM driver using this 
volume group
?
  Can't lock disks: skipping
  /proc/lvm/VGs/disks exists: Is the original LVM driver using this 
volume group
?
  Can't lock disks: skipping
--clip--

So, how can I disable LVM1 temporarily so LVM2 can access the disks?

-- 
  Mika Hirvonen <hirvox at welho.com>
  http://nightwatch.mine.nu/