From: Aaron Gross (Aaron.Gross@openfirst.com)
Date: Mon Jun 27 2005 - 12:53:11 EDT
I did not have to use luxadm to bring the drive back into the loop before
replacing the drive. Simply swapping out the physical drive brought it back
online in the A5200. But Veritas was giving me "Duplicate Device" errors
while trying to work with the drive. I had to do a "devfsadm" to rebuild
the device tree and a "vxdctl enable" to allow Veritas to see the
replacement drive. There was a delay between running the vxdctl and when
vxdiskadm was able to work with the drive. I re-initialized the spare, and
brought it back online.
As soon as it was brought back online, another drive failed, so once again
we are down to 1 spare. When it rains it pours, I guess!
Big thanks to Vic Enbel, NetComrade and Alfredo Deluca. Replies are listed
below.
Aaron
-----------------------------------
NetComrade:
Try devfsadm;vxdctl enable.
If not reboot :) A5200 give trouble like that sometimes.
You can always try opening a ticket with Veritas, if above it not an
option.
On Mon, 27 Jun 2005, Aaron Gross wrote:
> The disk is online (confirmed via luxadm and the display console of the
> A5200), but Veritas is giving me "Duplicate Device" errors, before I
rebuild
> the device tables I wanted to see if you have any advice. Run into this
> issue at all?
>
> Thanks for you advice!
>
> Aaron
>
> -----Original Message-----
> From: NetComrade [mailto:netcomrade@bookexchange.net]
> Sent: Monday, June 27, 2005 10:09 AM
> To: Aaron Gross
> Subject: Re: A5200 Question
>
>
> It's no longer there, b/c the disk is dead.
> luxadm is an OS tool, has nothing to do with Veritas.
> Once you replace the disk, you'll be able to use option 5 in vxdiskadm to
> put the data back (or you can use it now).
> Since you had spares, I imagine data already relocated.
> Loops usually reset whenever there is a disk failure.
---------------------------------------
-----Original Message-----
From: EngleV@mont.disa.mil [mailto:EngleV@mont.disa.mil]
Sent: Monday, June 27, 2005 7:26 AM
To: Aaron.Gross@openfirst.com
Subject: RE: A5200 Question
Aaron,
What I've done in that situation before is to just pull out the old drive
then luxadm will show the slot empty. At that point you should be able to
use luxadm insert_device to install the spare drive. Once installed you
still need to run "vxdctl enable" and then vxdiskadm option 5 to replace the
disk in veritas.
Regards,
Vic Engle
-----Original Message-----
From: Aaron Gross [mailto:Aaron.Gross@openfirst.com]
Sent: Friday, June 24, 2005 11:56 AM
To: 'sunmanagers@sunmanagers.org'
Subject: A5200 Question
Greeting Managers,
Recently we had an event on our A5200, our loop went offline for a
second, and then came right back online. According the /var/adm/message log
files, it reported that the drive
(/sbus@1f,0/SUNW,socal@2,0/sf@0,0/ssd@w2200002037e41a6e,0 (ssd2)) offline
due to a "Not Ready" event. Veritas then vxdmp the drive, and the A5200
bypassed the drive (Slot 2 on the back plane) on both loops. I have a spare
drive that I was going to replace it with, but Veritas no longer sees the
drive (ext0dg14) as being managed by Veritas, so I'm unable to mark the
drive for replacement. We have an additional spare, so it is not an
extremely hot deal, but I would like to replace the drive for a peice of
mind.
Luxadm display (Pasted below) shows the drive as Bypassed. Do I have to
un-bypass the Drive prior to using Veritas to replace the drive? Any help
would be greatly appreciated. We are running 5.7 106541-19
Aaron
luxadm display /dev/es/ses0
SENA
DISK STATUS
SLOT FRONT DISKS (Node WWN) REAR DISKS (Node WWN)
0 On (O.K.) 2000002037e41fc2 On (O.K.)
2000002037e41837
1 On (O.K.) 2000002037e41d8e On (O.K.)
2000002037e417bc
2 On (O.K.) 2000002037d8edc1 On (Bypassed:AB)
3 On (O.K.) 2000002037e41ded On (O.K.)
2000002037e41aa5
4 On (O.K.) 2000002037e41f4f On (O.K.)
2000002037e41795
5 On (O.K.) 2000002037e41fb9 On (O.K.)
2000002037e41929
6 On (O.K.) 2000002037e41f44 On (O.K.)
2000002037e41b45
7 On (O.K.) 2000002037e418b4 On (O.K.)
2000002037e41b10
8 On (O.K.) 2000002037e418c0 On (O.K.)
2000002037e41888
9 On (O.K.) 2000002037e41a0d On (O.K.)
2000002037e41814
10 On (O.K.) 2000002037e41c3c On (O.K.)
2000002037e41783
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:58 EDT