V-5-2-1814 c0d1: Invalid disk device for 'cdsdisk' format
| Article:TECH162220 | | | Created: 2011-06-14 | | | Updated: 2012-08-18 | | | Article URL http://www.symantec.com/docs/TECH162220 |
Problem
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0d1s2 auto:none - - online invalid
c0d2s2 auto:none - - online invalid
c0d3s2 auto:none - - online invalid
# vxdisk -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
c0d1s2 auto - - online c0d1s2 -
c0d2s2 auto - - online c0d2s2 -
c0d3s2 auto - - online c0d3s2 -
# vxdisk path
SUBPATH DANAME DMNAME GROUP STATE
c0d1s2 c0d1s2 - - ENABLED
c0d2s2 c0d2s2 - - ENABLED
c0d3s2 c0d3s2 - - ENABLED
# vxdisksetup -i c0d1s2
VxVM vxdisksetup ERROR V-5-2-2206 c0d1s2: An invalid device address was specified; it must be of
the form cCtTdD, mcCtTdD or <enclosurename>_<diskno> where
C = host bus adapter controller number
T = target device controller number, if used
D = logical unit (disk) number within target device controller
<enclosurename> is the logical name of the enclosure to which the
disk belongs
<diskno> is the logical number of the disk
# vxdisksetup -i c0d1
VxVM vxdisksetup ERROR V-5-2-1814 c0d1: Invalid disk device for 'cdsdisk' format
Environment
Solaris 5.0mp3rp1 LDOM
Solution
From 5.0mp3, vxvm could support LDOM, in LDOM disk naming is like c#d#, not c#t#d#, the target number is dropped.
customer used to map one partition from one physical disk as a LDOM virtual disk, such as c0d1, we can check the health of c0d1 first
1) disk is not accessed:
# /etc/vx/diag.d/vxdmpinq -d /dev/rdsk/c0d1s2
ioctl failed: Inappropriate ioctl for device
2) check vtoc:
# prtvtoc /dev/rdsk/c0d1s2
* /dev/rdsk/c0d1s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 32 sectors/track
* 64 tracks/cylinder
* 2048 sectors/cylinder
* 211 cylinders
* 209 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 0 2048 2047
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 0 00 2048 425984 428031
2 5 00 0 428032 428031
suggest cu to try:
1. if vtoc is writable
2. if vxdisksetup succeeds with only slice 2 existing
commands are like:
# cat /tmp/a
2 5 00 0 428032 428031
# fmthard –s /tmp/a /dev/rdsk/c0d1s2
# prtvtoc /dev/rdsk/c0d1s2
Or you also can use format command to remove slice 0.
found vtoc is not writable, customer remove the virtual disk and map whole physical disk to LDOM c0d1, vxvm initialize successfully
|
|
Article URL http://www.symantec.com/docs/TECH162220
Terms of use for this information are found in Legal Notices
Thank you.