English Bengali
This is usually caused by cloning the device image resulting in duplication of the UUID value which should be unique. In that case you can either disconnect one of the devices or reformat it.
For some reason we were unable to locate a disklabel on a disk that the kernel is reporting partitions on. It is unclear what the exact problem is. Please file a bug at http://bugzilla.redhat.com
Either restore the disklabel to a completely working state or remove it completely.
Hint: parted can restore it or wipefs can remove it.
Rename one of the volume groups so the names are distinct.
Hint 1: vgrename accepts UUID in place of the old name.
Hint 2: You can get the VG UUIDs by running 'pvs -o +vg_uuid'.
No iSCSI nodes discovered
Could not log in to any of the discovered nodes
unable to allocate aligned partition
requested size exceeds maximum allowed
disk %s inaccessible
partition is too small for %(format)s formatting (allowable size is %(min_size)s to %(max_size)s)
partition is too large for %(format)s formatting (allowable size is %(min_size)s to %(max_size)s)
Unable to allocate requested partition scheme.
not enough free space after creating extended partition
failed to allocate aligned partition
cannot reclaim more than request has grown
DiskChunk requests must be of type PartitionRequest
partitions allocated outside disklabel limits
VGChunk requests must be of type LVRequest
not enough space for LVM requests
Executing %(action)s