Encapsulating a disk

Question

Hi,&nbsp;

I have set up a &nbsp;new x86 server with Sol 10 and did a fresh installation of vxvm in that however, I have 2 disks in OS when I tried to online a root disk in vxvm it is not picking up.

I tried to encapsulate the root disk, it says that disk is successfully encapsulated and needs a shutdown, I did then when I checked it still shows disk in&nbsp;

online invalid state.

I humbly request you to look out into this.

Please let me &nbsp;know if anything else required.

Here is some O/p gathered,

bash-3.00# format
	Searching for disks...done

AVAILABLE DISK SELECTIONS:
	&nbsp; &nbsp; &nbsp; &nbsp;0. c1t0d0 &lt;DEFAULT cyl 3913 alt 2 hd 255 sec 63&gt;
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; /pci@0,0/pci15ad,1976@10/sd@0,0
	&nbsp; &nbsp; &nbsp; &nbsp;1. c1t1d0 &lt;DEFAULT cyl 3914 alt 2 hd 255 sec 63&gt;
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; /pci@0,0/pci15ad,1976@10/sd@1,0
	Specify disk (enter its number): 0
	selecting c1t0d0
	[disk formatted]
	Warning: Current Disk has mounted partitions.
	/dev/dsk/c1t0d0s0 is currently mounted on /. Please see umount(1M).
	/dev/dsk/c1t0d0s1 is currently used by swap. Please see swap(1M).
	/dev/dsk/c1t0d0s3 is currently mounted on /var. Please see umount(1M).
	/dev/dsk/c1t0d0s4 is currently mounted on /usr. Please see umount(1M).
	/dev/dsk/c1t0d0s5 is currently mounted on /temp. Please see umount(1M).

FORMAT MENU:
	&nbsp; &nbsp; &nbsp; &nbsp; disk &nbsp; &nbsp; &nbsp; - select a disk
	&nbsp; &nbsp; &nbsp; &nbsp; type &nbsp; &nbsp; &nbsp; - select (define) a disk type
	&nbsp; &nbsp; &nbsp; &nbsp; partition &nbsp;- select (define) a partition table
	&nbsp; &nbsp; &nbsp; &nbsp; current &nbsp; &nbsp;- describe the current disk
	&nbsp; &nbsp; &nbsp; &nbsp; format &nbsp; &nbsp; - format and analyze the disk
	&nbsp; &nbsp; &nbsp; &nbsp; fdisk &nbsp; &nbsp; &nbsp;- run the fdisk program
	&nbsp; &nbsp; &nbsp; &nbsp; repair &nbsp; &nbsp; - repair a defective sector
	&nbsp; &nbsp; &nbsp; &nbsp; label &nbsp; &nbsp; &nbsp;- write label to the disk
	&nbsp; &nbsp; &nbsp; &nbsp; analyze &nbsp; &nbsp;- surface analysis
	&nbsp; &nbsp; &nbsp; &nbsp; defect &nbsp; &nbsp; - defect list management
	&nbsp; &nbsp; &nbsp; &nbsp; backup &nbsp; &nbsp; - search for backup labels
	&nbsp; &nbsp; &nbsp; &nbsp; verify &nbsp; &nbsp; - read and display labels
	&nbsp; &nbsp; &nbsp; &nbsp; save &nbsp; &nbsp; &nbsp; - save new disk/partition definitions
	&nbsp; &nbsp; &nbsp; &nbsp; inquiry &nbsp; &nbsp;- show vendor, product and revision
	&nbsp; &nbsp; &nbsp; &nbsp; volname &nbsp; &nbsp;- set 8-character volume name
	&nbsp; &nbsp; &nbsp; &nbsp; !&lt;cmd&gt; &nbsp; &nbsp; - execute &lt;cmd&gt;, then return
	&nbsp; &nbsp; &nbsp; &nbsp; quit
	format&gt; p

PARTITION MENU:
	&nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp;- change `0' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 1 &nbsp; &nbsp; &nbsp;- change `1' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 2 &nbsp; &nbsp; &nbsp;- change `2' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 3 &nbsp; &nbsp; &nbsp;- change `3' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 4 &nbsp; &nbsp; &nbsp;- change `4' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 5 &nbsp; &nbsp; &nbsp;- change `5' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 6 &nbsp; &nbsp; &nbsp;- change `6' partition
	&nbsp; &nbsp; &nbsp; &nbsp; 7 &nbsp; &nbsp; &nbsp;- change `7' partition
	&nbsp; &nbsp; &nbsp; &nbsp; select - select a predefined table
	&nbsp; &nbsp; &nbsp; &nbsp; modify - modify a predefined partition table
	&nbsp; &nbsp; &nbsp; &nbsp; name &nbsp; - name the current table
	&nbsp; &nbsp; &nbsp; &nbsp; print &nbsp;- display the current table
	&nbsp; &nbsp; &nbsp; &nbsp; label &nbsp;- write partition map and label to the disk
	&nbsp; &nbsp; &nbsp; &nbsp; !&lt;cmd&gt; - execute &lt;cmd&gt;, then return
	&nbsp; &nbsp; &nbsp; &nbsp; quit
	partition&gt; p
	Current partition table (original):
	Total disk cylinders available: 3913 + 2 (reserved cylinders)

Part &nbsp; &nbsp; &nbsp;Tag &nbsp; &nbsp;Flag &nbsp; &nbsp; Cylinders &nbsp; &nbsp; &nbsp; &nbsp;Size &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Blocks
	&nbsp; 0 &nbsp; &nbsp; &nbsp; root &nbsp; &nbsp;wm &nbsp; &nbsp; 470 - 1999 &nbsp; &nbsp; &nbsp; 11.72GB &nbsp; &nbsp;(1530/0/0) 24579450
	&nbsp; 1 &nbsp; &nbsp; &nbsp; swap &nbsp; &nbsp;wu &nbsp; &nbsp; &nbsp; 1 - &nbsp;261 &nbsp; &nbsp; &nbsp; &nbsp;2.00GB &nbsp; &nbsp;(261/0/0) &nbsp; 4192965
	&nbsp; 2 &nbsp; &nbsp; backup &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 - 3912 &nbsp; &nbsp; &nbsp; 29.98GB &nbsp; &nbsp;(3913/0/0) 62862345
	&nbsp; 3 &nbsp; &nbsp; &nbsp; &nbsp;var &nbsp; &nbsp;wm &nbsp; &nbsp; 368 - &nbsp;469 &nbsp; &nbsp; &nbsp;800.11MB &nbsp; &nbsp;(102/0/0) &nbsp; 1638630
	&nbsp; 4 &nbsp; &nbsp; &nbsp; &nbsp;usr &nbsp; &nbsp;wm &nbsp; &nbsp;2000 - 3912 &nbsp; &nbsp; &nbsp; 14.65GB &nbsp; &nbsp;(1913/0/0) 30732345
	&nbsp; 5 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; 355 - &nbsp;367 &nbsp; &nbsp; &nbsp;101.98MB &nbsp; &nbsp;(13/0/0) &nbsp; &nbsp; 208845
	&nbsp; 6 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
	&nbsp; 7 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
	&nbsp; 8 &nbsp; &nbsp; &nbsp; boot &nbsp; &nbsp;wu &nbsp; &nbsp; &nbsp; 0 - &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp; &nbsp;7.84MB &nbsp; &nbsp;(1/0/0) &nbsp; &nbsp; &nbsp; 16065
	&nbsp; 9 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0

===================================================

2. &nbsp;bash-3.00# &nbsp; &nbsp;df -h
	Filesystem &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; size &nbsp; used &nbsp;avail capacity &nbsp;Mounted on
	/dev/dsk/c1t0d0s0 &nbsp; &nbsp; &nbsp; 12G &nbsp; 3.1G &nbsp; 8.3G &nbsp; &nbsp;28% &nbsp; &nbsp;/
	/devices &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/devices
	ctfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/system/contract
	proc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/proc
	mnttab &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/etc/mnttab
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4G &nbsp; 1.1M &nbsp; 2.4G &nbsp; &nbsp; 1% &nbsp; &nbsp;/etc/svc/volatile
	objfs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/system/object
	sharefs &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/etc/dfs/sharetab
	/dev/dsk/c1t0d0s4 &nbsp; &nbsp; &nbsp; 14G &nbsp; 4.3G &nbsp; &nbsp;10G &nbsp; &nbsp;30% &nbsp; &nbsp;/usr
	/usr/lib/libc/libc_hwcap1.so.1
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 14G &nbsp; 4.3G &nbsp; &nbsp;10G &nbsp; &nbsp;30% &nbsp; &nbsp;/lib/libc.so.1
	fd &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/fd
	/dev/dsk/c1t0d0s3 &nbsp; &nbsp; &nbsp;752M &nbsp; &nbsp;90M &nbsp; 609M &nbsp; &nbsp;13% &nbsp; &nbsp;/var
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4G &nbsp; &nbsp;44K &nbsp; 2.4G &nbsp; &nbsp; 1% &nbsp; &nbsp;/tmp
	swap &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 2.4G &nbsp; &nbsp;36K &nbsp; 2.4G &nbsp; &nbsp; 1% &nbsp; &nbsp;/var/run
	/dev/dsk/c1t0d0s5 &nbsp; &nbsp; &nbsp; 95M &nbsp; 1.0M &nbsp; &nbsp;85M &nbsp; &nbsp; 2% &nbsp; &nbsp;/temp
	/dev/odm &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0K &nbsp; &nbsp; 0% &nbsp; &nbsp;/dev/odm
	/vol/dev/dsk/c0t0d0/sol_10_910_x86
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.0G &nbsp; 2.0G &nbsp; &nbsp; 0K &nbsp; 100% &nbsp; &nbsp;/cdrom/sol_10_910_x86

============================================================

3. &nbsp; &nbsp;
	bash-3.00# vxdisk -e list
	DEVICE &nbsp; &nbsp; &nbsp; TYPE &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; DISK &nbsp; &nbsp; &nbsp; &nbsp;GROUP &nbsp; &nbsp; &nbsp; &nbsp;STATUS &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; OS_NATIVE_NAME &nbsp; ATTR
	disk_0 &nbsp; &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; online invalid &nbsp; &nbsp; &nbsp; c1t1d0s2 &nbsp; &nbsp; &nbsp; &nbsp; -
	disk_1 &nbsp; &nbsp; &nbsp; auto:none &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; online invalid &nbsp; &nbsp; &nbsp; c1t0d0s2 &nbsp; &nbsp; &nbsp; &nbsp; -

&nbsp;

Thanks,

Gary

&nbsp;

gaurav_s · Answer

Hello,

This is same problem as per your previous post, partition table is having missing blocks, not sure why is it configured this way ..

Part &nbsp; &nbsp; &nbsp;Tag &nbsp; &nbsp;Flag &nbsp; &nbsp; Cylinders &nbsp; &nbsp; &nbsp; &nbsp;Size &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Blocks
	&nbsp; 0 &nbsp; &nbsp; &nbsp; root &nbsp; &nbsp;wm &nbsp; &nbsp; 470 - 1999 &nbsp; &nbsp; &nbsp; 11.72GB &nbsp; &nbsp;(1530/0/0) 24579450
	&nbsp; 1 &nbsp; &nbsp; &nbsp; swap &nbsp; &nbsp;wu &nbsp; &nbsp; &nbsp; 1 - &nbsp;261 &nbsp; &nbsp; &nbsp; &nbsp;2.00GB &nbsp; &nbsp;(261/0/0) &nbsp; 4192965&nbsp; &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; After 261, 262-355 ?
	&nbsp; 2 &nbsp; &nbsp; backup &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 - 3912 &nbsp; &nbsp; &nbsp; 29.98GB &nbsp; &nbsp;(3913/0/0) 62862345 &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; Full slice
	&nbsp; 3 &nbsp; &nbsp; &nbsp; &nbsp;var &nbsp; &nbsp;wm &nbsp; &nbsp; 368 - &nbsp;469 &nbsp; &nbsp; &nbsp;800.11MB &nbsp; &nbsp;(102/0/0) &nbsp; 1638630
	&nbsp; 4 &nbsp; &nbsp; &nbsp; &nbsp;usr &nbsp; &nbsp;wm &nbsp; &nbsp;2000 - 3912 &nbsp; &nbsp; &nbsp; 14.65GB &nbsp; &nbsp;(1913/0/0) 30732345
	&nbsp; 5 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; 355 - &nbsp;367 &nbsp; &nbsp; &nbsp;101.98MB &nbsp; &nbsp;(13/0/0) &nbsp; &nbsp; 208845
	&nbsp; 6 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
	&nbsp; 7 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0
	&nbsp; 8 &nbsp; &nbsp; &nbsp; boot &nbsp; &nbsp;wu &nbsp; &nbsp; &nbsp; 0 - &nbsp; &nbsp;0 &nbsp; &nbsp; &nbsp; &nbsp;7.84MB &nbsp; &nbsp;(1/0/0) &nbsp; &nbsp; &nbsp; 16065
	&nbsp; 9 unassigned &nbsp; &nbsp;wm &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp; (0/0/0) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 0

&nbsp;

Did you notice any errors in /var/adm/messages ?

&nbsp;

G

marianne · Answer

Two other posts regarding encapsulation:

Regarding encapsulation and initialization of the disk&nbsp;

Issue while encapsulating the root disk&nbsp;

The issue is still the same - something weird/wrong as far as partitioning of your boot disk is concerned.

It does not seem as if we are going to fix this from VxVM point of view.

Oh, I just remembered something...

If memory serves me right, VxVM needs to use slice 3 and 4 in order to encapsulate a disk, but your disk has var and usr on those partitions.

Let me see if I can find documentation....

marianne · Answer

I found this URL:

http://sfdoccentral.symantec.com/sf/5.0/solaris64/html/vxvm_admin/ag_ch_disks_vm22.html&nbsp;

So, it seems VxVM will use any 2 free partitions/slices.

Please follow steps as per your previous attempt and then carefully watch the screen while the system reboots.
	(Be sure you have a 'console' view of the server to see &amp; copy messages on the screen.)
	Try to do a shutdown and then boot -v &nbsp;(not sure if this option is available on x86, but being able to boot in 'verbose' mode should help to see everything happening at boot time).

You will see conversions steps on the screen followed by another reboot.

We need to see what is getting added/changed in vfstab and system files at this point.

I still think that the weird partition table may be preventing successful encapsulation, but boot/conversion messages should provide evidence of what/where it is failing. Check /var/adm/messages as well.

&nbsp;

Forum Discussion

Encapsulating a disk

3 Replies

Related Content

Cant encapsulate disk

Unable to encapsulate root disk

Doubts on VxVM,VCS Upgrade & root disk encapsulation

vxvm encapsulation

Regarding encapsulation and initialization of the disk

Recent Discussions

DataDomain To StoreOnce Migration

VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

vxprivutil

URGENT disk oublic region recover

super block corrupt