Hi,
I am trying to mirror a disk (which was already mirror and after breaking it, doing it again). This is root disk and in control of veritas. Somehow, slice information is not coming correctly on this. Can somebody give some pointer to fix it ?
root@tdrp091:/root# prtvtoc /dev/rdsk/c3t0d0s2 | fmthard -s - /dev/rdsk/c3t1d0s2
fmthard: Partition 0 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
root@tdrp091:/root#
partition> p
Current partition table (unnamed):
Total disk sectors available: 286722911 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 unassigned wm 0 0 0
1 unassigned wm 0 0 0
2 unassigned wm 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 unassigned wm 0 0 0
8 reserved wm 286722912 8.00MB 286739295
partition> 2
Part Tag Flag First Sector Size Last Sector
2 unassigned wm 0 0 0
Enter partition id tag[usr]: backup
Enter partition permission flags[wm]: wu
Enter new starting Sector[34]: 0
`0' is out of range.
Enter new starting Sector[34]:
partition> 8
`8' is not expected.
partition> l
Ready to label disk, continue? y
partition>
Be careful - once handed to Veritas you may not use prtvtoc or format/label! Instead use the appropriate vx commands.
c3t1d0 is free disk and I am try different commands on it. In vxdisk list also, it is showing strange output, without slice-2 (disk_2)
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_2 auto:none - - online invalid c3t1d0 -
disk_3 auto:sliced rootdisk rootdg online c3t0d0s2 -
Looks like the disk has an EFI label. Check with format -e and set a SMI label if necessary.
After setting SMI Label on disk, I am able to label disk and vxdisk list also showing slice 2, but not able to place vtoc
root@tdrp091:/root# prtvtoc /dev/rdsk/c3t0d0s2 | fmthard -s - /dev/rdsk/c3t1d0s2
fmthard: Partition 0 overlaps partition 3. Overlap is allowed
only on partition on the full disk partition).
root@tdrp091:/root#
root@tdrp091:/root# vxdisk -e -oalldgs list | head
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_2 auto:none - - online invalid c3t1d0s2 -
disk_3 auto:sliced rootdisk rootdg online c3t0d0s2 -
-------------------------------------------------------------------------------------------
partition> p
Current partition table (unnamed):
Total disk cylinders available: 14087 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wu 0 0 (0/0/0) 0
2 backup wu 0 - 14086 136.71GB (14087/0/0) 286698624
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
Without distracting from the main line of conversation which I believe is very relevant (especially post#2 and post#4), I do wonder whether the hard disk in question has retained some mode page parameters from a previous life and is therefore misbehaving (eg, perhaps its got a reserve flag set on it). So just to be sure I would run format in expert mode
# format -e
and carefully ensure to select the right hard disk, enter the scsi menu and take the option to 'set all mode pages to default'. This won't alter any data on the drive but will remove any previously set parameters and return the drive to factory default. A hard disk drive is a highly programmable device so, personally, I would make sure the drive is not the culprit.
Show us the vtoc of the disk c3t0d0s2.