Troubleshooting a "failed" disk

Question

Hello all,
First things first, I have looked at this article to try and solve my problem, without success.
My server is configured this way:
SunOS hunahpu 5.9 Generic_122300-45 sun4u sparc SUNW,Netra-T12
System Configuration: Sun Microsystems&nbsp; sun4u Sun Fire E2900
	System clock frequency: 150 MHZ
	Memory size: 49152 Megabytes
pkginfo&nbsp; -l VRTSvxvm
	&nbsp;&nbsp; PKGINST:&nbsp; VRTSvxvm
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NAME:&nbsp; Binaries for VERITAS Volume Manager by Symantec
	&nbsp; CATEGORY:&nbsp; system
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ARCH:&nbsp; sparc
	&nbsp;&nbsp; VERSION:&nbsp; 5.0,REV=05.11.2006.17.55
	&nbsp;&nbsp; BASEDIR:&nbsp; /
	&nbsp;&nbsp;&nbsp; VENDOR:&nbsp; Symantec Corporation
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DESC:&nbsp; Virtual Disk Subsystem
	&nbsp;&nbsp;&nbsp; PSTAMP:&nbsp; Veritas-5.0-MP3.50:2008-08-17
	&nbsp; INSTDATE:&nbsp; Nov 09 2009 18:41
	&nbsp;&nbsp; HOTLINE:&nbsp; http://support.veritas.com/phonesup/phonesup_ddProduct_.htm
	&nbsp;&nbsp;&nbsp;&nbsp; EMAIL:&nbsp; support@veritas.com
	&nbsp;&nbsp;&nbsp; STATUS:&nbsp; completely installed
	&nbsp;&nbsp;&nbsp;&nbsp; FILES:&nbsp;&nbsp;&nbsp;&nbsp; 1007 installed pathnames
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 37 shared pathnames
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 19 linked files
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 111 directories
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 443 executables
	&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 435179 blocks used (approx)
	&nbsp;
The server is connected to a NetApp FAS 3070 cluster..
On saturday night, we had to do UPS maintenance and powered off the servers.&nbsp; When I powered this server up we saw the following error messages from vxvm:
May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 803759 kern.notice] NOTICE: VxVM vxdmp V-5-0-34 added disk array 3090882, datype = FAS3070
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 803759 kern.notice] NOTICE: VxVM vxdmp V-5-0-34 added disk array DISKS, datype = Disk
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 415628 kern.notice] NOTICE: VxVM vxdmp V-5-3-1700 dmpnode 275/0x0 has migrated from enclosure FAKE_ENCLR_SNO to enclosure DISKS
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x3f58 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x15e0 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x1d68 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x2638 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:24 hunahpu vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 32/0x15e0 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 899070 kern.notice] NOTICE: VxVM vxdmp V-5-0-147 enabled dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 32/0x2638 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 32/0x1d68 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 736771 kern.notice] NOTICE: VxVM vxdmp V-5-0-148 enabled path 32/0x3f58 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x3f58 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x15e0 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x1d68 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 917986 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 32/0x2638 belonging to the dmpnode 275/0x28
	May&nbsp; 5 02:10:57 hunahpu vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 275/0x28
	May&nbsp; 5 02:11:00 hunahpu vxvm:vxconfigd: [ID 702911 daemon.warning] V-5-1-546 Disk capadg01 in group capadg: Disk device not found
	May&nbsp; 5 02:11:00 hunahpu vxesd[474]: [ID 360244 daemon.notice] Event Source daemon started
	May&nbsp; 5 02:11:01 hunahpu vxesd[474]: [ID 342331 daemon.notice] HBA API Library Loaded
	May&nbsp; 5 02:11:02 hunahpu vxdmp: [ID 238993 kern.notice] NOTICE: VxVM vxdmp 0 dmp_tur_temp_pgr: open failed: error = 6 dev=0x113/0x2a
	&nbsp;
And indeed, the disk "capadg01" appears failed:
juanca@hunahpu / # vxdisk -o alldgs list
	DEVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DISK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS
	c1t0d0s2&nbsp;&nbsp;&nbsp;&nbsp; auto:none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online invalid
	c9t0d92s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg08&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d93s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg07&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d94s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg06&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d95s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg05&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d96s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg03&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d97s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg04&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d98s2&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; capadg02&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online nohotuse
	c9t0d99&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; error
	-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; capadg01&nbsp;&nbsp;&nbsp;&nbsp; capadg&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; failed nohotuse was:c9t0d99s2
	&nbsp;
Weird thing is, the server never lost connectivity to the SAN, all the other LUNs are OK and without errors.
When I looked at the disk with format, it said it didn't have a label.&nbsp; So I labeled it, but it appears to be incorrect (there's no partition 2):
partition&gt; pr
	Current partition table (original):
	Total disk sectors available: 2201993182 + 16384 (reserved sectors)
	
	Part&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tag&nbsp;&nbsp;&nbsp; Flag&nbsp;&nbsp;&nbsp;&nbsp; First Sector&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last Sector
	&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; root&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 34&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 128.00MB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 262177
	&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; swap&nbsp;&nbsp;&nbsp; wu&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 262178&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 128.00MB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 524321
	&nbsp; 2 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 3 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 4 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 5 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 524322&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1.03TB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2201993181
	&nbsp; 8&nbsp;&nbsp; reserved&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2201993182&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8.00MB&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2202009565
	&nbsp;
I believe this is the reason why vxvm won't reattach the disk, but I have been unable to fix the disk's label.&nbsp; I also find very strage that the partition "prints differently" from a healthy disk:
partition&gt; pr
	Current partition table (original):
	Total disk cylinders available: 9803 + 2 (reserved cylinders)
	
	Part&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tag&nbsp;&nbsp;&nbsp; Flag&nbsp;&nbsp;&nbsp;&nbsp; Cylinders&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Size&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Blocks
	&nbsp; 0 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 1 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp; backup&nbsp;&nbsp;&nbsp; wu&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 - 9802&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 899.88GB&nbsp;&nbsp;&nbsp; (9803/0/0) 1887195136
	&nbsp; 3 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 4 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 5 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 6 unassigned&nbsp;&nbsp;&nbsp; wm&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (0/0/0)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
	&nbsp; 7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; wu&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 - 9802&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 899.88GB&nbsp;&nbsp;&nbsp; (9803/0/0) 1887195136
	&nbsp;
The bad disk prints out First Sector, Size and Last Sector; while the good disk prints out Cylinders, Size and Blocks.
Does anyone have any ideas?&nbsp; All help would be highly appreciated.
I've attached detailed logs and server config.
Kind Regards,
Juancarlos Chacon
	jchacon@gmail.com
	skype: juanca_chacon
&nbsp;
&nbsp;

rsharma1 · Answer

Hi Juancarlos,
&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; The difference in partition o/p could be because the errored disk is formatted with EFI label but the healthy disk has a&nbsp; SMI label.&nbsp; LUNs greater than 1TB&nbsp;with Extensible Firmware Interface (EFI) disk label does not work in Veritas Volume Manager (VxVM 5.0) on Solaris 9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http://www.symantec.com/business/support/index?page=content&amp;id=TECH194766

stinsong · Answer

Juancarlos,
&nbsp;
First of all, it's really strange that the DMP node be enabled and disabled when DMP module was up and configured. Maybe there is something change on the FC link or LUN profile.
But after all, you format the disk with new label which is EFI label changed it could not be recognized by VxVM. For a EFI label, there are 9 partitions with the partition 8 reserved for EFI area. For a&nbsp;SMI label 8 slices; numbered 0-7 with slice 2 being the whole disk. So from the output of your text we could confirm you format it into a EFI disk, which could be confirmed with&nbsp;Cylinders, Size and Blocks information, too.
So you need to change the EFI label into SMI label:
partition&gt; label
[0] SMI Label
	[1] EFI Label
	Specify Label type[1]: 0
	Warning: This disk has an EFI label. Changing to SMI label will erase all
	current partitions.
	Continue? y
	Auto configuration via format.dat[no]?
	Auto configuration via generic SCSI-2[no]?
	partition&gt; q
Then you should be able to use it in VxVM. But I'm not sure if the volume structure and data could be available still...

g_lee · Answer

Juancarlos,
Are you sure c9t0d99 is the same disk that was presented to the system / has not changed since the failure?
The fact the disk was showing as unlabelled / you had to relabel suggests this wasn't the same disk that was presented earlier. Even if it was (and if you were using Solaris 10/configuration that supported EFI labels - see below), the fact that you've relabelled the disk would mean that you've removed/overwritten the vxvm partition (s3 for sliced, s7 for cds) so it would no longer see the dg details, which is why it would show in error.
The format output shows c9t0d99 is 1.03TB (&gt;1TB) with an EFI label (after you relabelled the disk); the example "healthy"/working disk is 899.88GB (&lt;1TB) with SMI label.
Disks &gt;1TB need EFI labels on Solaris 9 &amp; 10 - as rsharma1 pointed out earlier/above, EFI labels are only supported on Solaris 10 per the following technote:
LUNs greater than 1TB size with EFI label not supported in VxVM on Solaris 9
	http://www.symantec.com/business/support/index?page=content&amp;id=TECH194766
Can you check that c9t0d99 is definitely the same disk - if it is, do you have a prtvtoc of c9t0d99 prior to the failure for comparison / to try to restore the same configuration?
If it is not the same disk, is it possible to re-present the correct disk to the system, then rescan and see if it can see the dg information so you can try to reattach the disk.

Forum Discussion

Troubleshooting a "failed" disk

Related Content

Windows postgresql backup failing with error "Failed to load the PostgreSQL library: 126"

Postgresql restore fails with the error message"Failed to begin the transaction - 3"

"failed, status 6" error after increasing datastore (LUN) capacity

Re: Error requesting media, TpErrno = Robot operation failed

DLO 9.5 trial install fail: "SQL Express installation failed. Installation will Terminate"

Recent Discussions

DataDomain To StoreOnce Migration

VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

vxprivutil

URGENT disk oublic region recover

super block corrupt