Error importing diskgroup: No valid disk found containing disk group
book
Article ID: 100027461
calendar_today
Updated On:
Description
Error Message
# vxdg import rcbdg
VxVM vxdg ERROR V-5-1-10978 Disk group rcbdg: import failed:
No valid disk found containing disk group
Cause
The hostid field will be populated with the name of the server where the diskgroup was last imported. This field will be erased upon a logical export. Typically, when a system crashes, this field is left populated and will produce the error above on a subsequent import.
Resolution
Use the -C switch at the command line to clear this field.
# vxdg -C import rcbdg
# vxdg list|grep rcbdg
rcbdg enabled,cds 1341857906.36.karena
Applies To
This will apply to any non-shared diskgroup in any version of standalone Voume Manager environment (standalone server or failover cluster) on any supported Operating System.
Issue/Introduction
See message in ERROR section below.
While the issue discussed here applies to stand-alone Volume Manager (stand-alone or failover cluster), the import locking method used in a Clustered Volume Manager environment is similar (CVM, CFS or RAC). Stand-alone Volume Manager (non-shared diskgrup) will use the field of "hostid" while Clustered Volume Manager (shared diskgroups) will use field of "clustid" (for a shared disk group).
See the Volume Manager Admistator's Guide for more information on import locking.
In other words, a stand-alone Volume Manager environment (stad-alone server or failover cluster), a non-shared diskgroup will use the field of "hostid" for the import locking mechanism.
When any error is encountered importing a disk group (and this will apply in all enviroments), the first steps in troubleshooting are to make sure that all disks have an online status (error or online invalid is not good) and to validate the deported state of the diskgroup (vxdisk -o alldgs list).
For example:
# vxdisk -o alldgs list
DEVICE TYPE DISK GROUP STATUS
disk_0 auto:sliced rootdg01 rootdg online
disk_1 auto:sliced rootdg02 rootdg online
emc_clariion0_6 auto:cdsdisk - - online
emc_clariion0_16 auto:cdsdisk - - online
emc_clariion0_17 auto:cdsdisk - (fendg) online
emc_clariion0_18 auto:cdsdisk - (fendg) online
emc_clariion0_62 auto:cdsdisk - (fendg) online
(note: these three disks are in a deported state; check hostid field to see if imported elsewhere)
emc_clariion0_63 auto:cdsdisk disk0 rcbdg online
emc_clariion0_183 auto:cdsdisk disk1 rcbdg online
emc_clariion0_184 auto:simple - - online invalid
(note: this disk is online but is invalid from a Volume Manager perspective; typically uninitialized)
emc_clariion0_185 auto:cdsdisk - (zonedg) online
emc_clariion0_186 auto:cdsdisk - (zonedg) online
emc_clariion0_187 auto:cdsdisk - (zonedg) online
emc_clariion0_188 auto:cdsdisk - - online
emc_clariion0_189 auto:cdsdisk - - online
emc_clariion0_190 auto:simple - - online invalid
emc_clariion0_191 auto:simple - - online invalid udid_mismatch
emc_clariion0_192 auto:none - - online invalid
sun35100_12 auto:sliced - - error
(note: error status indicates that a valid private region could not be read; typically unable to be read at Operating System layer using something like dd)
Was this article helpful?
thumb_up
Yes
thumb_down
No