06-19-2014 10:31 PM
Hi,
I have set up a 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
online invalid state.
I humbly request you to look out into this.
Please let me know if anything else required.
Here is some O/p gathered,
bash-3.00# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <DEFAULT cyl 3913 alt 2 hd 255 sec 63>
/pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0 <DEFAULT cyl 3914 alt 2 hd 255 sec 63>
/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:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
fdisk - run the fdisk program
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> p
PARTITION MENU:
0 - change `0' partition
1 - change `1' partition
2 - change `2' partition
3 - change `3' partition
4 - change `4' partition
5 - change `5' partition
6 - change `6' partition
7 - change `7' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table
label - write partition map and label to the disk
!<cmd> - execute <cmd>, then return
quit
partition> p
Current partition table (original):
Total disk cylinders available: 3913 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 root wm 470 - 1999 11.72GB (1530/0/0) 24579450
1 swap wu 1 - 261 2.00GB (261/0/0) 4192965
2 backup wm 0 - 3912 29.98GB (3913/0/0) 62862345
3 var wm 368 - 469 800.11MB (102/0/0) 1638630
4 usr wm 2000 - 3912 14.65GB (1913/0/0) 30732345
5 unassigned wm 355 - 367 101.98MB (13/0/0) 208845
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
===================================================
2. bash-3.00# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 12G 3.1G 8.3G 28% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 2.4G 1.1M 2.4G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/dev/dsk/c1t0d0s4 14G 4.3G 10G 30% /usr
/usr/lib/libc/libc_hwcap1.so.1
14G 4.3G 10G 30% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
/dev/dsk/c1t0d0s3 752M 90M 609M 13% /var
swap 2.4G 44K 2.4G 1% /tmp
swap 2.4G 36K 2.4G 1% /var/run
/dev/dsk/c1t0d0s5 95M 1.0M 85M 2% /temp
/dev/odm 0K 0K 0K 0% /dev/odm
/vol/dev/dsk/c0t0d0/sol_10_910_x86
2.0G 2.0G 0K 100% /cdrom/sol_10_910_x86
============================================================
3.
bash-3.00# vxdisk -e list
DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR
disk_0 auto:none - - online invalid c1t1d0s2 -
disk_1 auto:none - - online invalid c1t0d0s2 -
Thanks,
Gary
06-20-2014 12:26 AM
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 Tag Flag Cylinders Size Blocks
0 root wm 470 - 1999 11.72GB (1530/0/0) 24579450
1 swap wu 1 - 261 2.00GB (261/0/0) 4192965 <<<<<<<<<< After 261, 262-355 ?
2 backup wm 0 - 3912 29.98GB (3913/0/0) 62862345 <<<<<<<<<< Full slice
3 var wm 368 - 469 800.11MB (102/0/0) 1638630
4 usr wm 2000 - 3912 14.65GB (1913/0/0) 30732345
5 unassigned wm 355 - 367 101.98MB (13/0/0) 208845
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 unassigned wm 0 0 (0/0/0) 0
Did you notice any errors in /var/adm/messages ?
G
06-20-2014 01:40 AM
Two other posts regarding encapsulation:
Regarding encapsulation and initialization of the disk
Issue while encapsulating the root disk
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....
06-20-2014 01:51 AM
I found this URL:
http://sfdoccentral.symantec.com/sf/5.0/solaris64/html/vxvm_admin/ag_ch_disks_vm22.html
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 & copy messages on the screen.)
Try to do a shutdown and then boot -v (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.