VxVM..anything to worry about in here..


 
Thread Tools Search this Thread
Operating Systems Solaris VxVM..anything to worry about in here..
# 1  
Old 12-13-2008
VxVM..anything to worry about in here..

DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced disk01 rootdg online
c2t0d0s2 sliced actsvr101 actsvr1dg online
c2t2d0s2 sliced actsvr102 actsvr1dg online
c2t3d0s2 sliced actsvr103 actsvr1dg online failing
c2t6d0s2 sliced actsvr107 actsvr1dg online spare
c2t16d0s2 sliced - - online
c2t19d0s2 sliced - - online
c2t20d0s2 sliced - - online
c2t22d0s2 sliced - - online
c3t32d0s2 sliced actsvr104 actsvr1dg online
c3t33d0s2 sliced - - error
c3t34d0s2 sliced actsvr105 actsvr1dg online
c3t35d0s2 sliced actsvr106 actsvr1dg online
c3t38d0s2 sliced - - online
c3t48d0s2 sliced - - online
c3t51d0s2 sliced - - online
c3t54d0s2 sliced - - online


AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN4.2G cyl 3880 alt 2 hd 16 sec 135>
/sbus@3,0/SUNW,fas@3,8800000/sd@0,0
1. c1t1d0 <SUN4.2G cyl 3880 alt 2 hd 16 sec 135>
/sbus@2,0/SUNW,fas@2,8800000/sd@1,0
2. c2t0d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0
3. c2t2d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0
4. c2t3d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0
5. c2t6d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169bb2,0
6. c2t16d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169dd4,0
7. c2t19d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169058,0
8. c2t20d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020370a2c20,0
9. c2t22d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371699df,0
10. c3t32d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w210000203713fd73,0
11. c3t33d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w210000203709c481,0
12. c3t34d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037162a85,0
13. c3t35d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w210000203716fd9e,0
14. c3t38d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037169979,0
15. c3t48d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037143dfd,0
16. c3t51d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w210000203716982d,0
17. c3t54d0 <SUN9.0G cyl 4924 alt 2 hd 27 sec 133>
/sbus@2,0/SUNW,socal@d,10000/sf@1,0/ssd@w2100002037169169,0

<output truncated>
Dec 12 17:12:46 actsvr1 unix:
Dec 12 17:12:46 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 17:12:46 actsvr1 unix: SCSI transport failed: reason 'tran_err': retrying command
Dec 12 17:12:46 actsvr1 unix:
Dec 12 17:12:46 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 12 17:12:46 actsvr1 unix: SCSI transport failed: reason 'tran_err': retrying command
Dec 12 17:12:46 actsvr1 unix:
Dec 12 17:12:46 actsvr1 unix: sf0: Target 0x0 Reset failed.Abort Failed
Dec 12 17:12:46 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 17:12:46 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:12:46 actsvr1 unix:
Dec 12 17:12:48 actsvr1 unix: ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is ONLINE
Dec 12 17:23:06 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 17:23:06 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:23:06 actsvr1 unix:
Dec 12 17:24:41 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 17:24:41 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:24:41 actsvr1 unix:
Dec 12 17:25:19 actsvr1 unix: ID[SUNWssa.socal.link.5010] socal0: port 0: Fibre Channel is OFFLINE
Dec 12 17:25:19 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 17:25:19 actsvr1 unix: SCSI transport failed: reason 'tran_err': retrying command
Dec 12 17:25:19 actsvr1 unix:
Dec 12 17:25:19 actsvr1 unix: ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is ONLINE
Dec 12 17:25:20 actsvr1 unix: sf0: ELS 0x0 to target 0x1d retrying
Dec 12 17:25:28 actsvr1 sm_egd[479]: Got an error: <AIL error in /opt/SUNWsymon/sbin/sm_egd: Connection failed for ConfigReader (RPC=1073879826) on actsvr1 (130.1.11.1)>
Dec 12 17:25:29 actsvr1 sm_configd[736]: unidentified board type 1
Dec 12 17:26:26 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 17:26:26 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:26:26 actsvr1 unix:
Dec 12 17:31:26 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 12 17:31:26 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:31:26 actsvr1 unix:
Dec 12 17:32:36 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 17:32:36 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 17:32:36 actsvr1 unix:
Dec 12 17:36:03 actsvr1 unix: ID[SUNWssa.socal.link.5010] socal0: port 0: Fibre Channel is OFFLINE
Dec 12 17:36:03 actsvr1 unix: ID[SUNWssa.socal.link.6010] socal0: port 0: Fibre Channel Loop is ONLINE
Dec 12 17:36:04 actsvr1 unix: sf0: ELS 0x0 to target 0x1d retrying
Dec 12 18:10:07 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 18:10:07 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 12 18:10:07 actsvr1 unix: Requested Block: 6029596 Error Block: 6029596
Dec 12 18:10:07 actsvr1 unix: Vendor: SEAGATE Serial Number: 9848X66445
Dec 12 18:10:07 actsvr1 unix: Sense Key: Aborted Command
Dec 12 18:10:07 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 12 18:11:21 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 12 18:11:21 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 18:11:21 actsvr1 unix:
Dec 12 19:11:24 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 19:11:24 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 19:11:24 actsvr1 unix:
Dec 12 19:12:24 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 19:12:24 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 19:12:24 actsvr1 unix:
Dec 12 19:12:24 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 12 19:12:24 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 12 19:12:24 actsvr1 unix: Requested Block: 410999 Error Block: 410999
Dec 12 19:12:24 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X51203
Dec 12 19:12:24 actsvr1 unix: Sense Key: Aborted Command
Dec 12 19:12:24 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 12 19:14:59 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 19:14:59 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 19:14:59 actsvr1 unix:
Dec 12 19:28:39 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w21000020371661db,0 (ssd1):
Dec 12 19:28:39 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 19:28:39 actsvr1 unix:
Dec 12 20:10:03 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 20:10:04 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 12 20:10:04 actsvr1 unix: Requested Block: 2154730 Error Block: 2154730
Dec 12 20:10:04 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X44338
Dec 12 20:10:04 actsvr1 unix: Sense Key: Aborted Command
Dec 12 20:10:04 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 12 20:10:04 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 12 20:10:04 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 12 20:10:04 actsvr1 unix: Requested Block: 2154714 Error Block: 2154714
Dec 12 20:10:04 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X51203
Dec 12 20:10:04 actsvr1 unix: Sense Key: Aborted Command
Dec 12 20:10:04 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 12 20:10:05 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169bb2,0 (ssd5):
Dec 12 20:10:05 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 12 20:10:05 actsvr1 unix: Requested Block: 13239 Error Block: 13191
Dec 12 20:10:05 actsvr1 unix: Vendor: SEAGATE Serial Number: 9848X81990
Dec 12 20:10:05 actsvr1 unix: Sense Key: Aborted Command
Dec 12 20:10:05 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 12 22:56:41 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 12 22:56:41 actsvr1 unix: SCSI transport failed: reason 'timeout': retrying command
Dec 12 22:56:41 actsvr1 unix:
Dec 13 00:05:02 actsvr1 sm_configd[1066]: unidentified board type 1
Dec 13 00:10:03 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169bb2,0 (ssd5):
Dec 13 00:10:03 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 00:10:03 actsvr1 unix: Requested Block: 7399 Error Block: 7399
Dec 13 00:10:03 actsvr1 unix: Vendor: SEAGATE Serial Number: 9848X81990
Dec 13 00:10:03 actsvr1 unix: Sense Key: Aborted Command
Dec 13 00:10:03 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 13 00:10:04 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 13 00:10:04 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 00:10:04 actsvr1 unix: Requested Block: 2205162 Error Block: 2205162
Dec 13 00:10:04 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X51203
Dec 13 00:10:04 actsvr1 unix: Sense Key: Aborted Command
Dec 13 00:10:04 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 13 00:10:12 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162e14,0 (ssd2):
Dec 13 00:10:12 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 00:10:12 actsvr1 unix: Requested Block: 2205466 Error Block: 2205466
Dec 13 00:10:12 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X51203
Dec 13 00:10:12 actsvr1 unix: Sense Key: Aborted Command
Dec 13 00:10:12 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 13 02:10:02 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 13 02:10:02 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 02:10:02 actsvr1 unix: Requested Block: 2151514 Error Block: 2151514
Dec 13 02:10:02 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X44338
Dec 13 02:10:02 actsvr1 unix: Sense Key: Aborted Command
Dec 13 02:10:02 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 13 02:10:03 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037169bb2,0 (ssd5):
Dec 13 02:10:03 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 02:10:03 actsvr1 unix: Requested Block: 7815 Error Block: 7815
Dec 13 02:10:03 actsvr1 unix: Vendor: SEAGATE Serial Number: 9848X81990
Dec 13 02:10:03 actsvr1 unix: Sense Key: Aborted Command
Dec 13 02:10:03 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
Dec 13 03:43:21 actsvr1 unix: WARNING: /sbus@2,0/SUNW,socal@d,10000/sf@0,0/ssd@w2100002037162f1a,0 (ssd4):
Dec 13 03:43:21 actsvr1 unix: Error for Command: write(10) Error Level: Retryable
Dec 13 03:43:22 actsvr1 unix: Requested Block: 741395 Error Block: 741395
Dec 13 03:43:22 actsvr1 unix: Vendor: SEAGATE Serial Number: 9844X44338
Dec 13 03:43:22 actsvr1 unix: Sense Key: Aborted Command
Dec 13 03:43:22 actsvr1 unix: ASC: 0x47 (scsi parity error), ASCQ: 0x0, FRU: 0x3
# 2  
Old 12-13-2008
It looks from the vxdisk list like actsvr103 is failing, but it is hard to tell from this if the cause of the problem is the fibre loop or the disk itself. Given that it appear to be affecting multiple disks would lean towards suspecting the fibre loop sbus controller or array controller ( if you have an array configured as JBOD ) or possibly just a failing port/transceiver since they all the disks appear to be on one fibre transceiver.
# 3  
Old 12-13-2008
How can we conclude what's the problem?
I have the explorer from the system. So whatever outputs you want, I can provide the information. Kindly assist me out. Im stuck.
# 4  
Old 12-13-2008
What can you do in terms of availability? Is it ok to bring the machine down or is it in production? I don't want to suggest anything that will cause you "manager problems".

Also what is the exact setup and what parts of the setup do you (currently) have replacement parts for? It look like an old enterprise machine with A1000/A5000 series arrays.
# 5  
Old 12-13-2008
Quote:
Originally Posted by reborg
Also what is the exact setup and what parts of the setup do you (currently) have replacement parts for? It look like an old enterprise machine with A1000/A5000 series arrays.
looks like an a5200 array. there are 16x9gb disks and two controllers. so it looks like an split bus setup. and it's rather old cause the machine has socal and not fcal adapters... on the other hand it can be a a1000 with mapped volumes... the target numbers maybe an indicator for volumes from a hardware raid system...

Last edited by DukeNuke2; 12-13-2008 at 03:39 PM..
# 6  
Old 12-13-2008
Quote:
Originally Posted by DukeNuke2
looks like an a5200 array. there are 16x9gb disks and two controllers. so it looks like an split bus setup. and it's rather old cause the mashine has socal and not fcal adapters... on the other hand it can be a a1000 with mapped volumes... the target numbers maybe an indicator for volumes from a hardware raid system...
I agree. Your analysis is pretty much the same as mine.
# 7  
Old 12-14-2008
Its a Production system, connected to a D1000 Array.
No worries about the availibility of parts. We will want a resolution so that we can follow up on that as soon.
And if there should be a downtime required, let me know with the action plan so that we can proceed.

Last edited by incredible; 12-14-2008 at 01:50 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies

2. Solaris

No of volumes in vxvm

Anyone knows that how many volumes can be created in a Diskgroup? Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies

3. Filesystems, Disks and Memory

VxVM and MPxIO

:confused: Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO. If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies

4. Solaris

Reg. VXVM

Hi Guys, I have a doubt either to Reboot the server after Replacing the disk0. I have two disks under vxvm root mirrored and i had a problem with primary disk so i replace the disk0 failed primary disk and then mirrored. After mirroring is it reboot required ? (7 Replies)
Discussion started by: kurva
7 Replies

5. Solaris

VxVM on Solaris.

Hi, Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies

6. Filesystems, Disks and Memory

vmstat -d with VxVM

I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed. The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies

7. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies
Login or Register to Ask a Question