[SUMMARY] T3 Array - Veritas Volume Manage help!!!

Webpro aielloster at gmail.com
Thu Oct 26 12:50:51 EDT 2006


With one disk failed and one failing, I was unable to reconstruct the
failed disk.  So I replaced both faulty disks and issued a vol verify
v0 fix rate 8.  This finished (eventually) and all disks were OK.  I
then ran a fsck on the device.  the fsck ran all night .  There were
some recovered directories, but in the end, I just did a newfs on the
entire volume and restored from tape.

The volume is created by the T3 and all disks managed by the T3.
Volume Managers simply had a volume of the volume.  That does not make
sense to me.  It seems I could have just mounted the array directly? I
left it the way it was.  It already caused me enough grief.


---------- Forwarded message ----------
From: Webpro <aielloster at gmail.com>
Date: Oct 24, 2006 9:32 AM
Subject: T3 Array - Veritas Volume Manage help!!!
To: sunmanagers at sunmanagers.org


I have inherited supporting an T3 array with 9 disks (no spares)
Firmware 1.16 and Veritas Volume Manager (running on an Ultra 60).  Of
course this is mount as /home and affects 60 - 100 folks...

We apparently have two disk issues.  One failed and cannot
reconstruct, the other is stuck reading one block.  The same block,
over and over.. hundreds of messages...

I am trying to figure out how to check/repair the disk with the read
error.  I am pretty unfamiliar with the commands on Veritas and the
T3.  I see some potentially useful commands like vol verify fix, but
am not sure if I use that or some vx command.

Disk 4 is failed and cannot reconstruct according to the syslog
messages.  fru status simply indicates it is rebuilding but the LED
and syslog say it failed.  I don't believe I can rely on the fru
command.

 Disk 2 has these errors...  I don't believe I can reconstruct disk 3
until disk 2 is repaired...

I would appreciate any help/insight.

Here are some messages I am receiving...

Oct 24 09:26:59 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9DEC OP 2A) Terminated by system
Oct 24 09:26:59 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9DEC OP 2A) Terminated by system
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: N: u1d2 SVD_DONE:
Command Error = 0x3
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: N: u1d2 SVD_DONE:
Command Error = 0x3
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: N: u1d2 sid 527746 stype
815 disk error 3
Oct 24 09:27:01 t3array.sylantro.com ISR1[1]: N: u1d2 sid 527746 stype
815 disk error 3
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr no alternate
for this stripe id 527746
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr no alternate
for this stripe id 527746
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E28 OP 2A) Alternate Stripe Failed
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E28 OP 2A) Alternate Stripe Failed
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E28 OP 2A) Terminated by system
Oct 24 09:27:01 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E28 OP 2A) Terminated by system
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: N: u1d2 SVD_DONE:
Command Error = 0x3
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: N: u1d2 SVD_DONE:
Command Error = 0x3
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: N: u1d2 sid 527746 stype
815 disk error 3
Oct 24 09:27:03 t3array.sylantro.com ISR1[1]: N: u1d2 sid 527746 stype
815 disk error 3
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr no alternate
for this stripe id 527746
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr no alternate
for this stripe id 527746
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E34 OP 2A) Alternate Stripe Failed
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E34 OP 2A) Alternate Stripe Failed
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E34 OP 2A) Terminated by system
Oct 24 09:27:03 t3array.sylantro.com SX01[1]: N: u1ctr (ITL 7D 1 0 TT
20 TID 9E34 OP 2A) Terminated by system
Oct 24 09:27:03 t3array.sylantro.com FCC0[1]: N: Target Reset Received
Oct 24 09:27:03 t3array.sylantro.com FCC0[1]: N: Target Reset Received
Oct 24 09:27:03 t3array.sylantro.com FCC0[1]: N: u1ctr <<Target
Reset>> on port 0, abort 0
Oct 24 09:27:03 t3array.sylantro.com FCC0[1]: N: u1ctr <<Target
Reset>> on port 0, abort 0


Oct 24 09:26:57 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Requested
Block: 540412560                 Error Block: 540412560
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Sense Key:
Hardware Error
Oct 24 09:26:57 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Requested
Block: 540412560                 Error Block: 540412560
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Vendor: SUN
                            Serial Number: 0001090910
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   ASC: 0x80
(<vendor unique code 0x80>), ASCQ: 0xb, FRU: 0x0
Oct 24 09:26:59 t3array.sylantro.com ISR1[1]: W: u1d2 SCSI Disk Error
Occurred (path = 0x1)
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Vendor: SUN
                            Serial Number: 0001090910
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Sense Key:
Hardware Error
Oct 24 09:26:59 t3array.sylantro.com ISR1[1]: W: Sense Key = 0x3, Asc
= 0x11, Ascq = 0x0
 Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   Sense Key:
Hardware Error
Oct 24 09:26:59 t3array.sylantro.com ISR1[1]: W: Sense Data
Description = Unrecovered Read Error
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   ASC: 0x80
(<vendor unique code 0x80>), ASCQ: 0xb, FRU: 0x0
Oct 24 09:26:59 t3array.sylantro.com ISR1[1]: W: Valid Information = 0x40d069e
Oct 24 09:29:01 tabasco scsi: [ID 107833 kern.notice]   ASC: 0x80
(<vendor unique code 0x80>), ASCQ: 0xb, FRU: 0x0


-- 
"Despite the high cost of living, it still remains popular!"

-- 
"Despite the high cost of living, it still remains popular!"



More information about the sunmanagers mailing list