Re: [Veritas-vx] couldn't encapsulate boot disk
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 FlagsSector CountSector Mount Directory
0 200 0 62928384 62928383 /
1 301 62928384 16790400 79718783
And then we changed the partition table for slice 2.
* Partition Tag FlagsSector CountSector Mount Directory
0 200 0 62928384 62928383 /
1 301 62928384 16790400 79718783
2 500 0 286698624 286698623
The tag is also very important.
After that, it worked.
Thanks to everyone.
Regards;
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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 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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: Hudes, Dana; ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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;
Re: [Veritas-vx] couldn't encapsulate boot disk
Hello,
All requirements meet. I have many disk just one is problematic for both the
same model system. I think there may be any bug or any point patch. Regards
From: veritas-vx-boun...@mailman.eng.auburn.edu
To: Hudes, Dana
Cc: Asiye Yigit; veritas-vx@mailman.eng.auburn.edu
Sent: Wed Oct 06 19:07:55 2010
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 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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: Hudes, Dana; ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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 physical
Re: [Veritas-vx] couldn't encapsulate boot disk
Yes,
But it is in error state. I will open a case to symantec support I think.
From: Hudes, Dana
To: Asiye Yigit; ger...@gotadsl.co.uk ; veritas-vx@mailman.eng.auburn.edu
Sent: Wed Oct 06 18:46:49 2010
Subject: RE: [Veritas-vx] couldn't encapsulate boot disk
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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: Hudes, Dana; ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: 06 October 2010 14:5
Re: [Veritas-vx] couldn't encapsulate boot disk
Hello,
I am using vxdisk -e list to see the physical adress. There is no cinfusion at
this part. The disk is really disk that I would like to encapsulate . It is the
boot disk.
From: DeMontier, Frank
To: Asiye Yigit; hud...@hra.nyc.gov ; ger...@gotadsl.co.uk ;
veritas-vx@mailman.eng.auburn.edu
Sent: Wed Oct 06 18:35:55 2010
Subject: RE: [Veritas-vx] couldn't encapsulate boot disk
By default, the upgrade changes the naming from osn ( os native ) to ebn (
enclosure based ). Additionally, disk_0 will not necessarily be c0t0d0s2, it
could be c0t1d0s2. Run the following command and see if this clears up some of
the confusion:
vxddladm set namingscheme=osn persistence=yes lowercase=yes use_avid=yes
Hope this helps. Good luck !
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: hud...@hra.nyc.gov; ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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.
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 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-boun...@mailman.eng.auburn.edu [mailto: > veritas-vx-boun...@mailman.eng.auburn.edu] *On Behalf Of *Asiye Yigit > *Sent:* Wednesday, October 06, 2010 11:29 AM > *To:* Hudes, Dana; ger...@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-boun...@mailman.eng.auburn.edu [mailto: > veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu [mailto: > veritas-vx-boun...@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&#
Re: [Veritas-vx] couldn't encapsulate boot disk
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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye Yigit Sent: Wednesday, October 06, 2010 11:29 AM To: Hudes, Dana; ger...@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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS 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: [,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 [,list,q,?] rootdg Create a new group named r
Re: [Veritas-vx] couldn't encapsulate boot disk
By default, the upgrade changes the naming from osn ( os native ) to ebn
( enclosure based ). Additionally, disk_0 will not necessarily be
c0t0d0s2, it could be c0t1d0s2. Run the following command and see if
this clears up some of the confusion:
vxddladm set namingscheme=osn persistence=yes lowercase=yes use_avid=yes
Hope this helps. Good luck !
From: veritas-vx-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Asiye
Yigit
Sent: Wednesday, October 06, 2010 11:29 AM
To: hud...@hra.nyc.gov; ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS
disk_2 auto--error
disk_3 auto:none --online
invalid
st2540-0_0 auto:none -
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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu
[mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS
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:
[,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 [,list,q,?] rootdg
Create a new group named rootdg? [y,n,q,?]
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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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:ger...@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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS 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: [,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 [,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 [,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
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:ger...@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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS 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: [,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 [,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 [,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
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-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@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 TYPEDISK GROUPSTATUS 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: [,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 [,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 [,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
[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 TYPEDISK GROUPSTATUS 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: [,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 [,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 [,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
