I am looking at my vmsa GUI and one of my disks in rootdg shows a X
sign on it. I looked in properties and alerts for the disk and I didnt
see anything on it.

vxdisk list | grep c3t2d0s2
c3t2d0s2 sliced inboard-1 rootdg online

vxprint -ht | grep c3t2d0s2
dm inboard-1 c3t2d0s2 sliced 4711 35363560 -

It looks like I am not using the correct CLI which will show whats
going wrong with the disk in Question. Any suggestions?

Thanks,
Shivakanth.

Shivakanth Mundru wrote:

> I am looking at my vmsa GUI and one of my disks in rootdg shows a X
> sign on it. I looked in properties and alerts for the disk and I didnt
> see anything on it.
>
> vxdisk list | grep c3t2d0s2
> c3t2d0s2 sliced inboard-1 rootdg online
>
> vxprint -ht | grep c3t2d0s2
> dm inboard-1 c3t2d0s2 sliced 4711 35363560 -
>
> It looks like I am not using the correct CLI which will show whats
> going wrong with the disk in Question. Any suggestions?
>
> Thanks,
> Shivakanth.

Don't trust GUI. That is the only suggestion I can give to you at this
moment. What Veritas version are you using?

Greetz,
Frank

Frank wrote:
> Shivakanth Mundru wrote:
>
>> I am looking at my vmsa GUI and one of my disks in rootdg shows a X
>> sign on it. I looked in properties and alerts for the disk and I didnt
>> see anything on it.
>>
>> vxdisk list | grep c3t2d0s2
>> c3t2d0s2 sliced inboard-1 rootdg online
>>
>> vxprint -ht | grep c3t2d0s2
>> dm inboard-1 c3t2d0s2 sliced 4711 35363560 -
>>
>> It looks like I am not using the correct CLI which will show whats
>> going wrong with the disk in Question. Any suggestions?
>>
>> Thanks,
>> Shivakanth.
>
>
> Don't trust GUI. That is the only suggestion I can give to you at this
> moment. What Veritas version are you using?
>
> Greetz,
> Frank

Running VXVM 3.1 on Solaris 8. Have to check whether all vmsa patches
are loaded or not.

Thanks,
Shivakanth.

smundru@cox-internet.com (Shivakanth Mundru) wrote in message news:<c3dd8461.0403010949.1deb7ac9@posting.google. com>...
> I am looking at my vmsa GUI and one of my disks in rootdg shows a X
> sign on it. I looked in properties and alerts for the disk and I didnt
> see anything on it.
>
> vxdisk list | grep c3t2d0s2
> c3t2d0s2 sliced inboard-1 rootdg online
>
> vxprint -ht | grep c3t2d0s2
> dm inboard-1 c3t2d0s2 sliced 4711 35363560 -
>
> It looks like I am not using the correct CLI which will show whats
> going wrong with the disk in Question. Any suggestions?
>

Since I never use Vx GUI, I've got no idea what X means
(except guessing it's somehow related to a bad Russian word
that starts with such a character :-)

Why don't you post the whole vxprint -g rootdg , maybe the problem
is not with disk itself but with a plex or volume using it?

If you find nothing there, try to insert a spare disk and relocate
the affected plex over there, then re-init the disk in question
and relocate the plex back. (all outside of production hours,
of course, and preferably using CLI, vxassist for instance).
See how GUI likes it.

Regards,
Andrei

Shivakanth Mundru wrote:
>

> Running VXVM 3.1 on Solaris 8. Have to check whether all vmsa patches
> are loaded or not.
>
>

showrev -p| grep patch_base_id

toomas
--
That's no moon...
-- Obi-wan Kenobi

Frank <no@spam.org> wrote in message news:<4043b745$0$560$e4fe514c@news.xs4all.nl>...
> Shivakanth Mundru wrote:
>
> > I am looking at my vmsa GUI and one of my disks in rootdg shows a X
> > sign on it. I looked in properties and alerts for the disk and I didnt
> > see anything on it.
> >
> > vxdisk list | grep c3t2d0s2
> > c3t2d0s2 sliced inboard-1 rootdg online
> >
> > vxprint -ht | grep c3t2d0s2
> > dm inboard-1 c3t2d0s2 sliced 4711 35363560 -
> >
> > It looks like I am not using the correct CLI which will show whats
> > going wrong with the disk in Question. Any suggestions?
> >
> > Thanks,
> > Shivakanth.
>
> Don't trust GUI. That is the only suggestion I can give to you at this
> moment. What Veritas version are you using?
>
> Greetz,
> Frank


That has been my mantra for years... especially with Veritas... DON'T
TRUST THE GUI! (have a big sign in my cube to remind me... lol)

aryzhov wrote:
> smundru@cox-internet.com (Shivakanth Mundru) wrote in message news:<c3dd8461.0403010949.1deb7ac9@posting.google. com>...
>
>>I am looking at my vmsa GUI and one of my disks in rootdg shows a X
>>sign on it. I looked in properties and alerts for the disk and I didnt
>>see anything on it.
>>
>>vxdisk list | grep c3t2d0s2
>>c3t2d0s2 sliced inboard-1 rootdg online
>>
>>vxprint -ht | grep c3t2d0s2
>>dm inboard-1 c3t2d0s2 sliced 4711 35363560 -
>>
>>It looks like I am not using the correct CLI which will show whats
>>going wrong with the disk in Question. Any suggestions?
>>
>
>
> Since I never use Vx GUI, I've got no idea what X means
> (except guessing it's somehow related to a bad Russian word
> that starts with such a character :-)
>
> Why don't you post the whole vxprint -g rootdg , maybe the problem
> is not with disk itself but with a plex or volume using it?
>
> If you find nothing there, try to insert a spare disk and relocate
> the affected plex over there, then re-init the disk in question
> and relocate the plex back. (all outside of production hours,
> of course, and preferably using CLI, vxassist for instance).
> See how GUI likes it.
>
> Regards,
> Andrei


I dont use GUI a lot either. One of our team member noticed it on the
GUI. I generally use vxprint & vxdg for looking at the status. The same
disk in Q is being shown online and nice without any bad status with CLI.

Thanks,
Shivakanth.