Error Code details
V-5-1-16253
Severity: Error 
Component: Volume Manager 
Message:
Disk group import of %s failed with error %d - %s
Description:

This message applies to VxVM 6.0 and higher releases.

This message is displayed when the disk group import operation fails. Import operation can fail in various scenarios with different reasons. The following table shows the possible scenarios and directs you to their corresponding solutions.

Scenarios

Solutions

Basic VxVM licenses are not present or FMR, Disk Group Split Join (DGSJ) licenses are not present in case of disk group import with cloned disks.

See solution 1.

VxVM is disabled.

 

See solution 2.

Vxconfigd (Volume Manager’s configuration daemon)  is running in disabled mode.

See solution 3.

IO fencing or SCSI-3 persistent  reservation is disabled in case of import with group reserve.

See solution 4.

Disk issues.

See solution 5.

Disks specified in the import command do not meet import requirements.

See solution 6.

Disks have host ID mismatch.

  • When a disk group is created or imported on any host, all the disks in that disk group are stamped with the host ID of importing host to ensure that SAN-accessed disks are not used by multiple hosts at the same time.
     
  • When the disk group is deported, host ID is cleared on all disks of the deported disk group.
     
  • If the deport fails or cannot complete cleanly (in cases such as system crashes during deport), host ID on the disks is not cleared and on subsequent import of this disk group on another host fails due to disks having host ID mismatch.

 

See solution 7.

 

 

Veritas solutions
Solution 1 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:59:05 PST
Platform: Generic
Release: 6.0
Content:

Check that basic VxVM, FMR, DGSJ and other necessary Veritas licenses are present on the system on which import is to be done. Use the following command to check the licenses:
 

 # vxdctl license

Solution 2 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:58:52 PST
Platform: Generic
Release: 6.0
Content:

Check that VxVM is enabled. Use the following command to enable VxVM:

 
#vxlicrep

 

It lists all Veritas licenses installed and the corresponding features enabled on the system. Check if basic license of VxVM is installed and VxVM feature is enabled.

Solution 3 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:59:40 PST
Platform: Generic
Release: 6.0
Content:

Ensure that vxconfigd is up and running in enable mode. Perform the following step: 

 

  1. check if vxconfigd is in enabled mode or not. Enter the following:

    #vxdctl mode 
     
  2. If vxconfigd is not enabled, enter the following to enable it:

    #vxdctl enable
Solution 4 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:40:49 PST
Platform: Generic
Release: 6.0
Content:

Check if IO fencing is configured and enabled with SCSI-3 persistent reservation on all nodes in case of import with group reserve.

 

Use the command # vxfenconfig –a to check the IO fencing mode. If IO fencing is disabled, perform the following steps:
 

  1. Stop all nodes. Enter the following:

    # /etc/vx/bin/vxclustadm –m gab stopnode
     
  2. Unconfigure fencing. Enter the following:

    # vxfenconfig –U
     
  3. Stop fencing. Enter the following:

    #/etc/init.d/vxfen stop
     
  4. Initialize a coordinator disk group consisting of minimum 3 disks, preferably small. Enter the following:

    #vxdg -o coordinator=on init coorddg diskname1 diskname2 diskname3
     
  5. Deport the disk group, then re-import it with -t option so that the auto-import is disabled, then deport it again. Enter the following:

    #vxdg deport coorddg

    #vxdg -t import coorddg

    #vxdg deport
    coorddg
     
  6. Configure the disk group which is created above. Make it as the fencing disk group. Enter the following:

    #echo "coorddg" > /etc/vxfendg
     
  7. Setup the vxfenmode file appropriately. Copy /etc/vxfen.d/vxfenmode_scsi3_dmp to /etc/vxfenmode.
     
  8. Start fencing by running the following command:

    /etc/init.d/vxfen start
     
  9. Verify that the disks you configured for fencing are reflected in the vxfentab file:

    cat /etc/vxfentab
     
  10. Configure fencing as follows:

    vxfenconfig -c
Solution 5 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:41:46 PST
Platform: Generic
Release: 6.0
Content:

Check that all the disks in the disk group to be imported are available and accessible.

Solution 6 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 08:01:28 PST
Platform: Generic
Release: 6.0
Content:

Ensure that disks specified in import operation meet the import requirements.
 

E.g. For import with cloned disks, provide cloned disks as parameter to import operation. etc

Solution 7 Vote: [Useful] [Not useful]
Last Modified: 2014-02-25 07:43:15 PST
Platform: Generic
Release: 6.0
Content:

Choose one of the following to clear the host ID:
 

  • Clear the host ID on all disks using “vxdisk clearimport” utility before import.
     
  • Use –C option to import the disk group. It clears the host ID on all the disks.

 

User solutions
No user solutions yet.

 

Read and accept Terms of Service