[Veritas-vx] Replacing encapsulated rootdisk

[Terrie Douglas]

Marcus,

 

You question of whether you are supposed to be able to boot off the
second device?  Short answer is "it appears so".  However there is an
odd looking vtoc on it.   

 

To answer your question of how to retrieve c0t0d0?

1.     In format replace the original partitioning/slicing

2.     Remove the tags and information on slices 6 and 7, in this case,
make sure they are zero'd out completely.

3.     Label disk as usual

4.     Re-encapsulate the boot disk using vxdiskadm, or comman line
options to do so.

5.     Verify the vtoc with a prtvtoc command.

6.     It should look similar to what you show below.

 

As long as this is a real boot disk the above should recover it.   There
are a few other minor steps to take to really clean  things up in
Solaris.  Like commenting out the boot info in the /etc/system file,
creating an install-db file so if the system boots you may want to
prevent veritas from starting up until you get this all sorted out. 

 

Worse case you will have to begin with a completely wiped/clean disk and
start a Solaris install on it, then encapsulate and then mirror.

 

The mirrored device will look similar to the original boot disk's vtoc
in that it will show a slice 0,1 and 2 as the bootable/root disk has.
This is necessary for Solaris to use to boot from.  Remember that a
bootblock must reside on slice 0 for Solaris to boot.

 

The device that shows only slice 2 and the tags of "14" and "15" on two
other slices is a blank or empty disk that is under VxVM control.  This
would NOT be what a root mirrored device would look like.

 

Good luck and if you get royally stuck, please phone in for support!

 

 

==========

Marcus Wrote:

First, why are the partition tables different for c0t0d0

and c0t1d0?

 

prtvtoc /dev/rdsk/c0t0d0:

 

    *                          First     Sector    Last

    * Partition  Tag  Flags    Sector     Count    Sector  Mount
Directory

           0      2    00          0   2049720   2049719

           1      3    01    2049720   2049720   4099439

           2      5    00          0  35368272  35368271

           3      7    00    4099440   2049720   6149159

           4      8    00   10248600   2049720  12298319

           5      4    00    6149160   4099440  10248599

           6     14    01          0  35368272  35368271

           7     15    01   35363560      4712  35368271

 

 

prtvtoc /dev/rdsk/c0t1d0s2:

 

    *                          First     Sector    Last

    * Partition  Tag  Flags    Sector     Count    Sector  Mount
Directory

           0      2    00    6153872   2049720   8203591

           1      3    01    8203592   2049720  10253311

           2      5    00          0  35368272  35368271

           3     15    01          0      4712      4711

           4     14    01       4712  35363560  35368271

           6      7    00   10253312   2049720  12303031

 

Am I supposed to be able to boot off of either t0 or t1

in this config?

 

Also, upon failure of c0t0d0, when the disk is replaced I

end up with:

 

prtvtoc /dev/dsk/c0t0d0s2

 

*                          First     Sector    Last

* Partition  Tag  Flags    Sector     Count    Sector  Mount Directory

       2      5    01          0  35368272  35368271

       3     15    01          0      4712      4711

       4     14    01       4712  35363560  35368271

 

 

***** NOTE:  This does not constitute support help!!*******

 

Thanks, 

Terrie Douglas
Sr. Prin. Technical Support Engineer
Symantec Software Corporation
Email: terrie_douglas at symantec.com

Phone: 650-527-3040
Customer Support: 1(800) 342-0652

 

 

 

View your case online at: https://mysupport.symantec.com
<https://mysupport.symantec.com> 

 

Save time and visit the Veritas Installation Assessment Services website
and check out our automated tools: https://vias.symantec.com/main.php
<https://vias.symantec.com/main.php> 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20100909/0687c441/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1765 bytes
Desc: image001.gif
Url : http://mailman.eng.auburn.edu/pipermail/veritas-vx/attachments/20100909/0687c441/attachment-0001.gif