Error Code details
V-5-2-338
Severity: Error 
Component: Volume Manager 
Message:
The encapsulation operation failed with the following error: `cat $tmpfile1`
Description:

Before Veritas Volume Manager (VxVM) encapsulates the partition slices of a disk, VxVM verifies that the disk partition meets the requirements for encapsulation. If the disk partition layout fails to meet these requirements, the encapsulation process fails with the following error message:

VxVM ERROR V-5-2-338
The encapsulation operation failed with the following error:
  VxVM vxencap ERROR V-5-2-213
  It is not possible to encapsulate disk_0, for the following reason:

An additional error  message displays with the reason the encapsulation cannot complete successfully.

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2010-05-04 22:42:29 PST
Platform: Generic
Release: Generic
Content:

The following list displays the messages and explanations of each:

564: Disk contains no partitions.

Explanation:  The disk does not contain any partitions to encapsulate.

754: Not enough free partitions.

5964: Unsupported disk layout. Encapsulation requires at least #sectors sectors of unused space either at the beginning or end of the disk drive.

Explanation: The disk does not contain enough unused partitions, or the disk does not contain the required amount of unused space required for encapsulation.

Solution: Free enough partitions and disk space for the encapsulation process. 

To encapsulate a boot or data disk in the sliced format, VxVM requires two unused partitions. One partition is required for the public region, which contains the space where subdisks are allocated. Another partition is required for the private region partition, which contains the VxVM metadata.

To encapsulate a data disk in the cdsdisk format, VxVM requires one unused partition for the public region partition, which contains the space where subdisks are allocated and the VxVM metadata.

The partition or partitions must have enough space for the private region (VxVM metadata) at the beginning of the disk, the end of the disk or from the swap partition. The current default size of the private region data is 32 megabytes which is rounded to the next cylinder.

The cdsdisk format also requires that the first 256 sectors are unused.

5444: Format cdsdisk cannot be specified with -r option.

5453: One or more partitions on the disk are not compatable with the 'cdsdisk' format. Please choose a different format.

5470: Unsupported disk layout for 'cdsdisk' format. Please choose a different format.

Explanation: The boot disk cannot be encapsulated as a cdsdisk format disk.

Solution: Reissue the encapsulation command and specify the sliced format.

11185: Cannot specify -r option with efi device.

11187: Format cdsdisk cannot be specified with EFI disk.

Explanation: VxVM currently does not support encapsulation with EFI devices.

11183: A file system is found in slice.

11188: Full slice is in use by a mounted file system.

Explanation: VxVM does not support encapsulation for a disk layout that has a "full" slice that contains a file system or a mounted file system.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service