Comment 27 for bug 115616

the solutions is already provided by link provided by Richard Kleeman:

from:
http://evms.sourceforge.net/install/kernel.html#bdclaim

The end result is that a single disk cannot be used both for EVMS and for mounting the kernel's built-in partitions.

There are three solutions to this problem.

    * Switch to using EVMS for ALL your volumes and partitions. If none of the kernel's built-in partitions are mounted, then there won't be any conflicts when DM tries to claim the disks. This is, of course, the preferred solution, but also requires some extra work on your part to convert to mounting your root filesystem using an EVMS volume. Please see the Root-Volume section of this install guide as well as the Converting-To-EVMS guide for more details on this option.

    * Tell EVMS to exclude any disks that contain partitions that you are going to mount using the kernel's built-in partitions. You can do this by adding the names of these disks to the sysfs_devices.exclude line in your /etc/evms.conf file. If you choose this option, EVMS will completely ignore the specified disks and not discover any of the partitions or volumes on those disks.

    * Apply this patch, which will is a reversal of the patch that prevents Device-Mapper and the kernel's built-in partitions from using the same disk at the same time. This patch is not supported by the kernel community, and in fact removes functionality that they specifically added. However, it will allow you to share your disks between EVMS and the kernel's built-in partitioning code, if that's the choice you wish to make for your system.

      patch -p1 < /usr/src/evms-2.5.5/kernel/2.6/bd-claim.patch

This issue does not exist on 2.4 kernels.