[prev in list] [next in list] [prev in thread] [next in thread]
List: veritas-vx
Subject: Re: [Veritas-vx] couldn't encapsulate boot disk
From: "Asiye Yigit" <asiye.yigit () gantek ! com>
Date: 2010-10-07 9:02:11
Message-ID: EC79C5A11A89A54FA0896E9513C30B2A03C8EDBF () ganexch ! gantek ! local
[Download RAW message or body]
--===============2958838404926004275==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01CB65FE.54A40F7A"
This is a multi-part message in MIME format.
Hello All;
We have solve the problem.
S2 slice was missed on my disk.
I have given the proper size to s2 slice and give the proper tag.
After that, I am able to encapsulate the disk.
It was like this:
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 62928384 62928383 /
1 3 01 62928384 16790400 79718783
And then we changed the partition table for slice 2.
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 0 62928384 62928383 /
1 3 01 62928384 16790400 79718783
2 5 00 0 286698624 286698623
The tag is also very important.
After that, it worked.
Thanks to everyone.
Regards;
From: veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] On Behalf Of \
William Havey
Sent: Wednesday, October 06, 2010 7:08 PM
To: Hudes, Dana
Cc: Asiye Yigit; veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] couldn't encapsulate boot disk
Since your following the Symantec suggestions, they state the boot disk must
Ø Two free partitions.
Ø 2048 consecutive sectors free.
Ø Enclosure-based names (EBN) has not been implemented (pre 5.1).
Ø Partition 2 spans the whole device with no defined file system.
You've still got to deal with the "error" state.
Bill
On Wed, Oct 6, 2010 at 11:46 AM, Hudes, Dana <hudesd@hra.nyc.gov> wrote:
yes it is still supported. Veritas has to support the same features on any platform. \
that's part of the point of Veritas.
go right ahead and do your experiment. while you're at it you could dig out the \
procedure for a more pure veritas disk.
________________________________
From: veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: Hudes, Dana; gerbra@gotadsl.co.uk; veritas-vx@mailman.eng.auburn.edu
Subject: Re: [Veritas-vx] couldn't encapsulate boot disk
Hello,
I am really aware of zfs and other features. Just test purpose I am trying to do \
boot disk encapsulation. I think it is still supported on this system.
________________________________
From: Hudes, Dana
To: Asiye Yigit; Christian Gerbrandt ; veritas-vx@mailman.eng.auburn.edu
Sent: Wed Oct 06 17:45:29 2010
Subject: RE: [Veritas-vx] couldn't encapsulate boot disk
don't do it.
There is no longer, with a Solaris 10 system such as your 5120, a valid reason to \
use VERITAS boot disk encapsulation.
Use ZFS. As I recall the 5120 has hardware mirroring so you could use that or you \
could use ZFS mirroring. The advantage of hardware mirroring is that it doesn't come \
up to the OS -- but a 5120 has enough CPUs to deal with mirroring. Managing the \
mirror with ZFS gives you more ready access via fmadm to any disk errors rather than \
having them buried behind the raid controller.
Use Solaris 10, preferably update 9, and ZFS for your boot. This is also very \
important for zones and for Live Upgrade.
VERITAS has its advantages in some situations for managing data disks (for example, \
raw volumes and Oracle if you have an ODM license), especially older Oracle releases \
(all of which are certified to work on Solaris 10). LU will make ZFS snapshots and \
clones if you have a ZFS boot disk. If you have VERITAS-encapsulated it will first \
unencapsulate the boot slice.
VERITAS boot encapsulation also lacks a mirrored dump device: since Vx doesn't have \
the API for dump, you have to give the underlying swap slice. Lose that disk lose \
your dump device. Vx requires swap is a slice, it's fixed in size until you manually \
go in and grow that slice -- if you left room on your root disk to do that operation. \
ZFS root, by contrast, uses a zvol for dump and a zvol for swap. They are sparse \
devices only using space when needed. Of course that means you can fill your entire \
root disk and leave nothing for dump or swap -- so you could also just create them as \
regular zvols with nailed-up space which you can shrink and grow manually as desired \
without worrying that you left room in your disk layout.
boot encapsulation was the thing to do on Solaris 8 and 9. Not 10.
________________________________
From: veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: \
Wednesday, October 06, 2010 10:18 AM To: Christian Gerbrandt; \
veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] couldn't encapsulate \
boot disk
Hello;
Disk is okay.
I know it should be online invalid.
For both T5120 systems, the problem is same.
I have many disk from san and two disks internal.
For the boot disk, for both system, it says error state.
Disks are okay physically.
There may be some point patch for SF 5.1RP2 for boot disk mirroring?
From: Christian Gerbrandt [mailto:gerbra@gotadsl.co.uk]
Sent: Wednesday, October 06, 2010 5:17 PM
To: Asiye Yigit; veritas-vx@mailman.eng.auburn.edu
Subject: RE: [Veritas-vx] couldn't encapsulate boot disk
As you can see, disk_2 is showing in 'error' state.
But it should show as 'online invalid'.
There seems to be an error with the disk.
Check the status of the disk from OS/VxVM and SAN.
From: veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: 06 \
October 2010 14:55 To: veritas-vx@mailman.eng.auburn.edu
Subject: [Veritas-vx] couldn't encapsulate boot disk
Hello;
I have installed SP 5.1RP2 on solaris 10 system.
I am trying to encapsulate the boot disk and after that I will make mirror.
In the vxdisk list,
It shows
DEVICE TYPE DISK GROUP STATUS
disk_2 auto - - error
disk_3 auto:none - - online invalid
st2540-0_0 auto:none - - online invalid
when I try to encapsulate the disk disk_2;
it says
Select disk devices to encapsulate:
[<pattern-list>,all,list,q,?] disk_2
Here is the disk selected. Output format: [Device_Name]
disk_2
Continue operation? [y,n,q,?] (default: y)
You can choose to add this disk to an existing disk group or to
a new disk group. To create a new disk group, select a disk group
name that does not yet exist.
Which disk group [<group>,list,q,?] rootdg
Create a new group named rootdg? [y,n,q,?] (default: y)
Use a default disk name for the disk? [y,n,q,?] (default: y)
A new disk group will be created named rootdg and the selected
disks will be encapsulated and added to this disk group with
default disk names.
disk_2
Continue with operation? [y,n,q,?] (default: y)
This disk device is disabled (offline) and cannot be used.
Output format: [Device_Name]
disk_2
Hit RETURN to continue.
When I try to make online;
It says
Select a disk device to enable [<disk>,list,q,?] disk_2
VxVM vxdisk ERROR V-5-1-531 Device disk_2: online failed:
Device path not valid
Enable another device? [y,n,q,?] (default: n)
Is there any idea?
Best regards;
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
[Attachment #3 (text/html)]
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-9">
<html xmlns:v="urn:schemas-microsoft-com:vml" \
xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Lucida Bright";
panose-1:2 4 6 3 7 5 5 2 4 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.hd1arrow, li.hd1arrow, div.hd1arrow
{mso-style-name:hd1arrow;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=WordSection1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hello All;<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>We have solve the problem.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>S2 slice was missed on my disk.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have given the proper size to s2 slice and give the proper
tag.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>After that, I am able to encapsulate the disk.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It was like this:<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>* Partition Tag Flags Sector Count Sector Mount
Directory<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> 0 2 00 0 62928384 62928383 \
/<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> 1 3 01 62928384 16790400 \
79718783<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>And then we changed the partition table for slice \
2.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>* Partition Tag Flags Sector Count Sector Mount
Directory<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> 0 2 00 0 62928384 62928383 \
/<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> 1 3 01 62928384 16790400 \
79718783<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'> 2 5 00 0 286698624 \
286698623<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>The tag is also very important.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>After that, it worked.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks to everyone.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards;<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> \
veritas-vx-bounces@mailman.eng.auburn.edu \
[mailto:veritas-vx-bounces@mailman.eng.auburn.edu] <b>On Behalf Of </b>William \
Havey<br> <b>Sent:</b> Wednesday, October 06, 2010 7:08 PM<br>
<b>To:</b> Hudes, Dana<br>
<b>Cc:</b> Asiye Yigit; veritas-vx@mailman.eng.auburn.edu<br>
<b>Subject:</b> Re: [Veritas-vx] couldn't encapsulate boot disk<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Since your following the Symantec suggestions, they state
the boot disk must <o:p></o:p></p>
<p class=hd1arrow><span style='font-family:Wingdings'>Ø</span><span
style='font-size:7.0pt'> </span>Two free partitions.<o:p></o:p></p>
<p class=hd1arrow><span style='font-family:Wingdings'>Ø</span><span
style='font-size:7.0pt'> </span>2048 consecutive sectors free.<o:p></o:p></p>
<p class=hd1arrow><span style='font-family:Wingdings'>Ø</span><span
style='font-size:7.0pt'> </span>Enclosure-based names (EBN) has not been
implemented (pre 5.1).<o:p></o:p></p>
<p class=hd1arrow><span style='font-family:Wingdings'>Ø</span><span
style='font-size:7.0pt'> </span>Partition 2 spans the whole device with no
defined file system.<o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>You've still got to deal with
the "error" state.<br>
<br>
Bill<o:p></o:p></p>
<div>
<p class=MsoNormal>On Wed, Oct 6, 2010 at 11:46 AM, Hudes, Dana <<a
href="mailto:hudesd@hra.nyc.gov">hudesd@hra.nyc.gov</a>> wrote:<o:p></o:p></p>
<div>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>yes
it is still supported. Veritas has to support the same features on any
platform. that's part of the point of Veritas.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>go
right ahead and do your experiment. while you're at it you could dig out the
procedure for a more pure veritas disk. </span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<blockquote style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm \
4.0pt; margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<div>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a \
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a> [mailto:<a \
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a>] <b>On Behalf Of \
</b>Asiye Yigit<o:p></o:p></span></p>
</div>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Sent:</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Wednesday, October 06, \
2010 11:29 AM<br> <b>To:</b> Hudes, Dana; <a href="mailto:gerbra@gotadsl.co.uk" \
target="_blank">gerbra@gotadsl.co.uk</a>; <a \
href="mailto:veritas-vx@mailman.eng.auburn.edu" \
target="_blank">veritas-vx@mailman.eng.auburn.edu</a><o:p></o:p></span></p>
<div>
<div>
<p class=MsoNormal><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'><br> <b>Subject:</b> Re: \
[Veritas-vx] couldn't encapsulate boot disk<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<div>
<p><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Hello,<br>
I am really aware of zfs and other features. Just test purpose I am trying to
do boot disk encapsulation. I think it is still supported on this \
system.</span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal><b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From</span></b><span \
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>: Hudes, Dana <br> \
<b>To</b>: Asiye Yigit; Christian Gerbrandt ; <a \
href="mailto:veritas-vx@mailman.eng.auburn.edu" \
target="_blank">veritas-vx@mailman.eng.auburn.edu</a> <br>
<b>Sent</b>: Wed Oct 06 17:45:29 2010<br>
<b>Subject</b>: RE: [Veritas-vx] couldn't encapsulate boot disk \
</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>don't
do it.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>There
is no longer, with a Solaris 10 system such as your 5120, a valid reason to use
VERITAS boot disk encapsulation.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>Use
ZFS. As I recall the 5120 has hardware mirroring so you could use that or you
could use ZFS mirroring. The advantage of hardware mirroring is that it
doesn't come up to the OS -- but a 5120 has enough CPUs to deal with mirroring.
Managing the mirror with ZFS gives you more ready access via fmadm to any disk
errors rather than having them buried behind the raid controller. \
</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>Use
Solaris 10, preferably update 9, and ZFS for your boot. This is also very
important for zones and for Live Upgrade.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida \
Bright","serif";color:blue'>VERITAS has its advantages in some situations for \
managing data disks (for example, raw volumes and Oracle if you have an ODM license), \
especially older Oracle releases (all of which are certified to work on Solaris \
10). LU will make ZFS snapshots and clones if you have a ZFS boot disk. If you \
have VERITAS-encapsulated it will first unencapsulate the boot \
slice.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida \
Bright","serif";color:blue'>VERITAS boot encapsulation also lacks a mirrored dump \
device: since Vx doesn't have the API for dump, you have to give the underlying swap \
slice. Lose that disk lose your dump device. Vx requires swap is a slice, it's \
fixed in size until you manually go in and grow that slice -- if you left room on \
your root disk to do that operation. ZFS root, by contrast, uses a zvol for dump and \
a zvol for swap. They are sparse devices only using space when needed. Of course that
means you can fill your entire root disk and leave nothing for dump or swap --
so you could also just create them as regular zvols with nailed-up space which
you can shrink and grow manually as desired without worrying that you left room
in your disk layout.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Lucida Bright","serif";color:blue'>boot
encapsulation was the thing to do on Solaris 8 and 9. Not 10.</span><o:p></o:p></p>
<p class=MsoNormal> <o:p></o:p></p>
<blockquote style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm \
4.0pt; margin-left:3.75pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>
<p class=MsoNormal><o:p> </o:p></p>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> <a
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a> [mailto:<a \
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a>] <b>On Behalf Of \
</b>Asiye Yigit<br>
<b>Sent:</b> Wednesday, October 06, 2010 10:18 AM<br>
<b>To:</b> Christian Gerbrandt; <a
href="mailto:veritas-vx@mailman.eng.auburn.edu" \
target="_blank">veritas-vx@mailman.eng.auburn.edu</a><br> <b>Subject:</b> Re: \
[Veritas-vx] couldn't encapsulate boot disk</span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Hello;</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Disk is okay.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I know it should be online invalid.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>For both T5120 systems, the problem is \
same.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>I have many disk from san and two disks \
internal.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>For the boot disk, for both system, it says error \
state.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>Disks are okay physically.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'>There may be some point patch for SF 5.1RP2 for boot disk
mirroring?</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'>
Christian Gerbrandt [mailto:<a href="mailto:gerbra@gotadsl.co.uk"
target="_blank">gerbra@gotadsl.co.uk</a>] <br>
<b>Sent:</b> Wednesday, October 06, 2010 5:17 PM<br>
<b>To:</b> Asiye Yigit; <a href="mailto:veritas-vx@mailman.eng.auburn.edu"
target="_blank">veritas-vx@mailman.eng.auburn.edu</a><br>
<b>Subject:</b> RE: [Veritas-vx] couldn't encapsulate boot disk</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB style='color:#1F497D'>As you can see, disk_2 is showing in \
‘error’ state.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB style='color:#1F497D'>But it should show as ‘online \
invalid’.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB style='color:#1F497D'>There seems to be an error with the \
disk.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB style='color:#1F497D'>Check the status of the disk from OS/VxVM and
SAN.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB style='color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;
border-color:-moz-use-text-color -moz-use-text-color'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a> [mailto:<a \
href="mailto:veritas-vx-bounces@mailman.eng.auburn.edu" \
target="_blank">veritas-vx-bounces@mailman.eng.auburn.edu</a>] <b>On Behalf Of \
</b>Asiye Yigit<br>
<b>Sent:</b> 06 October 2010 14:55<br>
<b>To:</b> <a href="mailto:veritas-vx@mailman.eng.auburn.edu" \
target="_blank">veritas-vx@mailman.eng.auburn.edu</a><br> <b>Subject:</b> \
[Veritas-vx] couldn't encapsulate boot disk</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
lang=EN-GB> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hello;<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
have installed SP 5.1RP2 on solaris 10 system.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I
am trying to encapsulate the boot disk and after that I will make \
mirror.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>In
the vxdisk list,<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It
shows <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>DEVICE
TYPE
DISK
GROUP STATUS<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>disk_2
auto
-
- \
error<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>disk_3
auto:none
-
- online
invalid<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>st2540-0_0
auto:none
-
- online
invalid<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>when
I try to encapsulate the disk disk_2;<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>it
says<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Select
disk devices to
encapsulate: &n \
bsp;
<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>[<pattern-list>,all,list,q,?]
disk_2<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
Here is the disk selected. Output format: [Device_Name]<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
disk_2<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Continue
operation? [y,n,q,?] (default: y) <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
You can choose to add this disk to an existing disk group or to<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
a new disk group. To create a new disk group, select a disk \
group<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
name that does not yet exist.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Which
disk group [<group>,list,q,?] rootdg<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Create
a new group named rootdg? [y,n,q,?] (default: y) <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Use
a default disk name for the disk? [y,n,q,?] (default: y) <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
A new disk group will be created named rootdg and the selected<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
disks will be encapsulated and added to this disk group with<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
default disk names.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
disk_2<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Continue
with operation? [y,n,q,?] (default: y) <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
This disk device is disabled (offline) and cannot be used.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
Output format: [Device_Name]<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
disk_2<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hit
RETURN to continue.<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>When
I try to make online;<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It
says<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Select
a disk device to enable [<disk>,list,q,?] disk_2<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
VxVM vxdisk ERROR V-5-1-531 Device disk_2: online failed:<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>
Device path not valid<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Enable
another device? [y,n,q,?] (default: n)<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Is
there any idea?<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Best
regards;<o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
Veritas-vx maillist - <a
href="mailto:Veritas-vx@mailman.eng.auburn.edu">Veritas-vx@mailman.eng.auburn.edu</a><br>
<a href="http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx"
target="_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx</a><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>
_______________________________________________
Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
--===============2958838404926004275==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic