[ID 107833 kern.warning] ... /scsi_vhci/....

Hi there,
Have noticed these errors in dmesg log and seems like during this period of errors we had our systems have a very low transfer rate.
I have 3 sets of erros to dig into.
[1] I did some search and found a similar error and had a patch for the specific device ...(reference http://sunsolve.sun.com/search/document.do?assetkey=1-26-101771-1). Errors are attached below
[2] SAM-FS critical device error. Not sure on if this is critical, and how to go about finding the source of the problem.
[3] output of iostat -En ....showing 2 hard errors. is this the source of all problems above ???
Thanks for any help you can provide!!!
~a2@sunsolve
[1] =============================================
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
[2] ===================================================
Nov 23 04:13:10 suseme genu-50[2704]: [ID 559880 local7.crit] crit Device 53: State set to DOWN by SAM-FS. Check device log.
Nov 23 04:13:10 suseme genu-50[2704]: [ID 694869 local7.alert] Volume (50:8) is in drive 53 that is off or down.
[3] ==================================================
iostat -En | more
c0t0d0 Soft Errors: 2 Hard Errors: 0 Transport Errors: 0
Vendor: TOSHIBA Product: DVD-ROM SD-M1712 Revision: 1004 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 2 Predictive Failure Analysis: 0
c1t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1TJ
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c1t4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1601 Serial No: 0509Q0K1T7
Size: 73.40GB <73400057856 bytes>
==============================================

can you help me how to fix scsi warnning ?
ov 23 01:00:13 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f0b4290b53e (ssd21):
Nov 23 01:00:13 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Requested Block: 302073600 Error Block: 302073600
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:13 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80001732a600002f084290b04e (ssd51):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 418872392 Error Block: 418872392
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac0000026714290b04b (ssd50):
Nov 23 01:00:25 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Requested Block: 304059616 Error Block: 304059616
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:25 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac00000267442913027 (ssd20):
Nov 23 01:00:33 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Requested Block: 4 Error Block: 4
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:00:33 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b8000178ac000002676429130a7 (ssd46):
Nov 23 01:01:53 suseme Error for Command: write(10) Error Level: Retryable
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Requested Block: 8715 Error Block: 8715
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Vendor: SUN Serial Number:
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] Sense Key: Unit Attention
Nov 23 01:01:53 suseme scsi: [ID 107833 kern.notice] ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
[2] ===================================================

Similar Messages

  • Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000

    Hi,
    I need help regarding below kernel warning message :
    Jul 30 15:01:23 server scsi: [ID 107833 kern.warning] WARNING: /pci@1e,6000
    I am new to solaris, and am unable to understand this.I want to know,
    1) What this warning exactly means.
    2) Is this warning important or can be negated.
    3) what causes this warning to generate again and again.
    Please let me know if you want any further information regarding this.
    Thanks & Regards,
    Girish

    That error message is something to do with a storage device. But its cut off, /pci indicates a pci card, and 1e,6000 is a partial address to the card. You need to post the next few lines as well.
    .7/M.

  • Scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):

    ug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
    Aug 12 14:00:36 gtcerp1      Connected command timeout for Target 6.0
    Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
    Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: Connected command timeout for Target 6.0
    Aug 12 14:00:36 gtcerp1 glm: [ID 280919 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6017]
    Aug 12 14:00:36 gtcerp1 scsi: [ID 107833 kern.warning] WARNING: /pci@8,700000/scsi@1 (glm0):
    Aug 12 14:00:36 gtcerp1      got SCSI bus reset
    Aug 12 14:00:36 gtcerp1 genunix: [ID 408822 kern.info] NOTICE: glm0: fault detected in device; service still available
    Aug 12 14:00:36 gtcerp1 genunix: [ID 611667 kern.info] NOTICE: glm0: got SCSI bus reset
    Aug 12 14:02:47 gtcerp1 scsi: [ID 365881 kern.info] /pci@8,700000/scsi@1 (glm0):
    we are geting this errror since from last two week, can anyone suggest us how to remove this error. we have tried by removing scsi card and rebooted, intially the error is removed but now its again come on console.

    Hi.
    Unfortunetly you not write what server you have.
    */pci@8,700000/scsi@1* look like Internal SCSI controller in Sun Fire V880.
    For this server Target 6.0 is CD-ROM (DVD-ROM).
    So it's look like problem with device.
    For check you can use:
    ls -la /dev/rdsk/*s2 | grep "/pci@8,700000/scsi@1"
    iostat -EnCheck internal cable to CD-ROM. Replace or disconnect CDROM.
    Regards.

  • [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st ack for

    Hi All,
    I have two Sunfire V880 server with Solaris 5.9 , in solaris cluster 3.1. Oracle 10g Database installed in both srver with RAC. last day i got the following error Swap error from one of the cluster node. In both server 14GB device swap and 14GB file system swap also.. please see the log and give me a solution.. Thanks in advance for all
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21901 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21998 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21391 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21901 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21387 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 5155 (oracle)
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20732 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 5155 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20930 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 19016 (oracle)
    Jul 24 17:04:28 server last message repeated 3 times
    Jul 24 17:04:28 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20015 (oracle)
    Jul 24 17:04:28 server last message repeated 1 time
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 22143 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20817 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 21884 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 19990 (oracle)
    Jul 24 17:04:29 server last message repeated 3 times
    Jul 24 17:04:30 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 20107 (oracle)
    Jul 24 17:04:30 server last message repeated 3 times
    Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10365 (oracle)
    Jul 24 17:48:29 server last message repeated 3 times
    Jul 24 17:48:29 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10258 (oracle)
    Jul 24 17:48:29 server last message repeated 3 times
    Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 15862 (oracle)
    Jul 24 17:53:32 server last message repeated 3 times
    Jul 24 17:53:32 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10335 (oracle)
    Jul 24 17:53:32 server last message repeated 3 times
    Jul 24 18:45:13 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 9847 (oracle)
    Jul 24 18:45:13 server last message repeated 3 times
    Jul 24 18:46:57 server genunix: [ID 470503 kern.warning] WARNING: Sorry, no swap space to grow st
    ack for pid 10883 (oracle)
    Jul 24 18:46:57 server last message repeated 6 times
    Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
    Jul 24 18:47:21 server root: [ID 702911 user.error] Duplicate clsomon found. Restarting.
    Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
    Jul 24 18:47:23 server root: [ID 702911 user.error] Oracle clsomon shutdown successful.
    Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 111=>fp(2)::GPN_ID for D_ID=20600
    failed
    Jul 25 00:41:19 server fctl: [ID 517869 kern.warning] WARNING: 112=>fp(2)::N_x Port with D_ID=206
    00, PWWN=100000e0022201be disappeared from fabric
    Jul 25 00:41:36 server fctl: [ID 517869 kern.warning] WARNING: 126=>fp(2)::N_x Port with D_ID=206
    00, PWWN=100000e0022201be reappeared in fabric
    bash-2.05$

    Note: This thread was originally posted in the [Servers - General Discussion|http://forums.sun.com/forum.jspa?forumID=830] forum, but moved to this forum for closer topic alignment.

  • ID 893081 kern.warning

    I cannot find any info regarding this message
    from /var/adm/messages
    ufs: [ID 893081 kern.warning] WARNING: ufs_readir: bad dir, inumber = 3, fs = /u1
    FYI inode 3 was the lost+found directory.
    This message is the only indication of a possible failure, The system this happened on had a strange occurence. the /u1 /u2 file,systems were on the same disk. About 4:00PM Friday 1/16/04 I get a call from a user that it appears data is missing. almost like someone had loaded a backup. Users that had not logged out could see their data, upon logging out, the data was never written to disk. The applications on /u1 was DCPA and /u2 was informix.
    Any clues as to how this may have happened. The data was migrated to a new disk and is now mirrored and message has not reappeared.

    If you think that you may have other affected systems then I would boot into single user mode and do a full fsck "fsck -o f /dev/rdsk/.." of each filesystem, and that will give you confidence that they are good.

  • ID 518458 kern.warning /tmp File system Full

    ID 518458 kern.warning /tmp File system Full swap spce limit exceeded. Sorry no space to grow stack for PID(in.rshd)
    The system is a Netra with 1gb memory and is having 1gb partition for swap and another swap file for 500mb is added still it is going to run out. The system has apache web server running and other java applications.
    Any suggestions are welcome
    Thanks

    thanks for your reply.
    d1: Mirror
    Submirror 0: d11
    State: Okay
    Submirror 1: d21
    State: Okay
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 30721626 blocks ( 15GB )
    System clock frequency: 150 MHz
    Memory size: 12288 Megabytes
    ========================= CPUs ===============================================
    Port Run E$ CPU CPU
    FRU Name ID MHz MB Impl. Mask
    /N0/SB3/P0 12 900 8.0 US-III+ 2.2
    /N0/SB3/P1 13 900 8.0 US-III+ 2.2
    /N0/SB3/P2 14 900 8.0 US-III+ 2.2
    /N0/SB3/P3 15 900 8.0 US-III+ 2.2
    /N0/SB5/P0 20 900 8.0 US-III+ 2.3
    /N0/SB5/P1 21 900 8.0 US-III+ 2.3
    /N0/SB5/P2 22 900 8.0 US-III+ 2.3
    /N0/SB5/P3 23 900 8.0 US-III+ 2.3
    d1 size is 15GB. and CPU is 8 ea. Memory size is 12GB.
    I think that swap device was enough.
    thanks in advance,

  • Sun Trunking 1.& kern Warning Hardware address trying to be our IP addresse

    Using Sun Trunking 1.3 on a solaris 10 11/06 V490 server.
    setenv local-mac-address? is set to true
    Obviously server Aggregate MAC address corresponds to first NIC local MAC address. Second NIC has its specific MAC address.
    Aggregate seams OK (traffic continues undisrupted when unplugging a card)
    but :
    1) Should I worry kernel is logging from toime to time messages such as :
    WARNING: IP: Hardware address '00:14:4f:3b:60:f4' trying to be our address IP_address !
    2) There is no load balancing between the 2 NIC interfaces as reported by nettr -stats 0 interval=2
    Traffic always flows using NIC 2.
    Appreciated,
    Lor.

    That depends on the switch.
    SunTrunking 1.3 is compatible with Cisco EtherChannel for example. I believe there's a manual configuration on the switch to say that these two ports are participating in an etherchannel linkage. SunTrunking is an 802.11ad protocol. If they haven't done that, then the switch is just assuming the two ports are normal and have separate hosts behind them.
    If instead of SunTrunking you were using Solaris 10 Link Aggregation, then you'd ask the networking guys to turn on LACP, which sets up a communication so the devices can describe their trunk/network setup. SunTrunking doesn't let you do that.
    What interfaces do you have on the Solaris box?
    Darren

  • 'offline or reservation conflict' WARNING'

    I have a fairly new Solaris 10 server connected to SAN SToragetek 6140. I noticed when I rebooted yesterday the following in /var/adm/messages:
    Dec 5 09:51:18 ariel scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b800029ba4e000005ae47534d9c (ssd19):
    Dec 5 09:51:18 ariel      offline or reservation conflict
    ssd19 is set up as a snapshot volume and would have been inactive at the time of the reboot - does this explain the error message?
    Thanks
    Diana

    When the node boots, you will always see the offline messages until the node joins the cluster and is given the keys to access the shared disks.
    Just to cover the basics:
    1) The hosts are setup as solaris mpxio (explicit failover)
    2) Each host has a connection to each controller (i.e., there are no cabling issues where one host goes to one controller and the other host goes to the other controller.)
    You should see (via luxadm) one primary and one secondary path, only 1 of which is active like this:
    root[alinghi:/root]# luxadm display /dev/rdsk/c6t600A0B800029A2780000077446CC68BCd0s2
    DEVICE PROPERTIES for disk: /dev/rdsk/c6t600A0B800029A2780000077446CC68BCd0s2
    Vendor: SUN
    Product ID: CSM200_R
    Revision: 0619
    Serial Num: SG11111111
    Unformatted capacity: 204800.000 MBytes
    Write Cache: Enabled
    Read Cache: Enabled
    Minimum prefetch: 0x300
    Maximum prefetch: 0x300
    Device Type: Disk device
    Path(s):
    /dev/rdsk/c6t600A0B800029A2780000077446CC68BCd0s2
    /devices/scsi_vhci/disk@g600a0b800029a2780000077446cc68bc:c,raw
    Controller /dev/cfg/c4
    Device Address 201600a0b829a278,1
    Host controller port WWN 210000e08b85ce7c
    Class primary
    State ONLINE
    Controller /dev/cfg/c5
    Device Address 202700a0b829a278,1
    Host controller port WWN 210100e08ba5ce7c
    Class secondary
    State STANDBY
    Having two online paths would be a bad thing in your case and result in the issues you are seeing.
    You will also want to verify that the 2nd node is up. At that point the system will have 2 out of 3 votes and thus operational quorum.
    Of course, if the cables are correct and both nodes running, then somebody with better troubleshooting skills than me will have to step in :-)

  • Retryable warning msg

    i have 4 Sun StorageTek 2540 connected via fiber to Sun Fire X4600
    the below warning appear many times since one month, 15 days ago all the zpool was degraded and i lose part of my data
    could any one have solution for such error
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,9 (sd44):
    Nov  4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 348696594                 Error Block: 348696594
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,0 (sd53):
    Nov  4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 434132201                 Error Block: 434132201
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.warning] WARNING: /pci@7a,0/pci10de,5d@d/pci1077,143@0/fp@0,0/disk@w202400a0b85a33bc,7 (sd46):
    Nov  4 01:58:41 wteniq1         Error for Command: write(10)               Error Level: Retryable
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Requested Block: 382881665                 Error Block: 382881665
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Vendor: SUN                                Serial Number:
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   Sense Key: Unit Attention
    Nov  4 01:58:41 wteniq1 scsi: [ID 107833 kern.notice]   ASC: 0xc (write error), ASCQ: 0x0, FRU: 0x0
    many thanks

    thank  Pascal
    i all ready check it before, where was no alarm  except
    A controller cache backup battery has failed Tray.85.Battery.A
    i read in one blog in the internet the below
    The vendor unique ASC/ASCQ code 0xc0/0x00 within the Solaris host; it indicates that there is an internal timeout on the array because of too much load
    do you think is it right
    regards

  • Warning in messages on nonexistence disk

    Hi,
    We received the following on our Sparc V890 in the /var/log/messages everytime we boot up the system:
    Feb 21 07:04:57 [server] scsi: [ID 107833 kern.warning] WARNING: /pci@9,600000/pci@2/SUNW,qlc@5/fp@0,0/ssd@w21000011c6b8fd4a,0 (ssd31):
    Feb 21 07:04:57 [server] Corrupt label; wrong magic number
    I have traced the address and found we do not have a disk inserted in the listed address. The message will only appear once after boot up until the next bootup. I have tried probe-scsi-all & reboot -- -r without been able to remove the message.
    Any ideas why the message is so persistent & how to stop it from appearing?
    Thanks.
    Edited by: user12187090 on Feb 20, 2011 11:46 PM

    Well, you can in theory remove it with cfgadm (use cfgadm -al to list all devices).
    However, if it reappears after a reconfigure boot, and complains on each boot, it seems like the drive is still there, if it wasn't you shouldn't see it at every boot.
    Given the path; /pci@9,600000/pci@2/SUNW,*qlc*@5/*fp*@0,0/ssd@w21000011c6b8fd4a,0, it seems to be a SAN/FCP connected LUN, if thats any help.
    You could also try the cleanup-flag to devfsadm:
    devfsadm -C
    . . but i don't think it helps, you should be able to list the device with luxadm though..
    .7/M.

  • Asm weird errors

    we have 2 SUN FIRE 6900 with cluster ware 10.1.0.4..2 asm and database
    the node 1 runs forms reports services for solaris 10
    the node 2 runs application server
    node 1 and node 2 are running different databases node 1 spdb and node 2 turbodb
    recently we have the following sequence of errors in the files following loss of service of reports server and eventually we have to reboot machine 1
    ASM ALERT FILE
    Wed Mar 17 09:51:12 2010
    Errors in file /opt/orabase/asmhome/admin/+ASM/udump/+asm1_ora_5759.trc:
    ORA-07445: exception encountered: core dump [__lwp_kill()+8] [SIGIOT] [unknown code] [0x167F00000000] [] []
    Wed Mar 17 09:51:12 2010
    Trace dumping is performing id=[cdmp_20100317095112]
    DB ALERT
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_12196.trc.
    Wed Mar 17 09:51:12 2010
    Thread 1 advanced to log sequence 41853
    Current log# 2 seq# 41853 mem# 0: +DATA/spisdb/onlinelog/group_22
    Current log# 2 seq# 41853 mem# 1: +DATA/spisdb/onlinelog/group_2
    Wed Mar 17 09:51:21 2010
    Errors in file /opt/orabase/dbhome/admin/SPISDB/bdump/spisdb_arc3_6847.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+DATA/spisdb/onlinelog/group_11'
    ORA-17503: ksfdopn:2 Failed to open file +DATA/spisdb/onlinelog/group_11
    ORA-03113: end-of-file on communication channel
    Wed Mar 17 09:56:40 2010
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_4820.trc.
    Wed Mar 17 09:56:41 2010
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_18667.trc.
    Wed Mar 17 10:01:49 2010
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_1200.trc.
    Wed Mar 17 10:17:31 2010
    Thread 1 advanced to log sequence 41854
    Current log# 3 seq# 41854 mem# 0: +DATA/spisdb/onlinelog/group_33
    Current log# 3 seq# 41854 mem# 1: +DATA/spisdb/onlinelog/group_3
    Wed Mar 17 10:22:14 2010
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_25503.trc.
    Wed Mar 17 10:24:29 2010
    ORA-00060: Deadlock detected. More info in file /opt/orabase/dbhome/admin/SPISDB/udump/spisdb_ora_11719.trc.
    dmesg is full of these lines ....
    Mar 17 10:23:03 e6900ap3 scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):
    Mar 17 10:23:03 e6900ap3 /scsi_vhci/ssd@g600a0b80002624f4000034224b11ee2f (ssd73): Command Timeout on path /ssm@0,0/pci@1b,700000/SUNW,qlc@2/fp@0,0 (fp2)
    Mar 17 10:23:03 e6900ap3 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80002624f4000034224b11ee2f (ssd73):
    Mar 17 10:23:03 e6900ap3 SCSI transport failed: reason 'timeout': retrying command
    Mar 17 10:26:36 e6900ap3 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600a0b80002624f4000034224b11ee2f (ssd73):
    Mar 17 10:26:36 e6900ap3 SCSI transport failed: reason 'tran_err': retrying command
    -bash-3.00$ cat /opt/orabase/asmhome/admin/+ASM/udump/+asm1_ora_5759.trc
    /opt/orabase/asmhome/admin/+ASM/udump/+asm1_ora_5759.trc
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP and Data Mining options
    ORACLE_HOME = /opt/orabase/asmhome
    System name: SunOS
    Node name: e6900ap3
    Release: 5.10
    Version: Generic_118833-20
    Machine: sun4u
    Instance name: +ASM1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 0
    Unix process pid: 5759, image: oracle@e6900ap3
    Exception signal: 6 (SIGIOT), code: -1 (unknown code), addr: 0x167f00000000, exception issued by pid: 5759, uid: 200, PC: [0xffffffff7aace500, __lwp_kill()+8]
    *** 2010-03-17 09:51:12.165
    ksedmp: internal or fatal error
    ORA-07445: exception encountered: core dump [__lwp_kill()+8] [SIGIOT] [unknown code] [0x167F00000000] [] []
    Current SQL information unavailable - no session.
    ----- Call Stack Trace -----
    calling call entry argument values in hex
    location type point (? means dubious value)
    ksedmp()+744 CALL ksedst() 000000840 ?
    FFFFFFFF7FFF517C ?
    000000000 ?
    FFFFFFFF7FFF1C70 ?
    FFFFFFFF7FFF09D8 ?
    FFFFFFFF7FFF13D8 ?
    ssexhd()+1000 CALL ksedmp() 000106000 ? 106323304 ?
    106323000 ? 000106323 ?
    000106000 ? 106323304 ?
    __sighndlr()+12 PTR_CALL 0000000000000000 000380007 ?
    FFFFFFFF7FFF8EF0 ?
    000000067 ? 000380000 ?
    000000006 ? 106323300 ?
    call_user_handler() CALL __sighndlr() 000000006 ?
    +992 FFFFFFFF7FFF8EF0 ?
    FFFFFFFF7FFF8C10 ?
    10032D860 ? 000000000 ?
    000000005 ?
    raise()+16 CALL pthread_kill() FFFFFFFF7AC02000 ?
    has anyone of you guys seen something like this
    personally i manage the machine from 2000 miles away so there is no chance for a physical look

    It doesn't seem to be an error of starting up the instance;
    Startup Fails with ORA-7445 [__lwp_kill()+8] on Sun V440 Machines [ID 330082.1]
    Bug 4422028: ORA-7445 [__LWP_KILL] DURING STARTUP NOMOUNT OF ASM INSTANCE
    The instance is already running ages ago!!!
    also Bug 4422028 refers to configuring and creating an ASM instnce and we don't fall in to this case.
    regarding the sequence of errors
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+DATA/spisdb/onlinelog/group_11'
    ORA-17503: ksfdopn:2 Failed to open file +DATA/spisdb/onlinelog/group_11
    ORA-03113: end-of-file on communication channel
    can you advice please!
    Edited by: user11995938 on 18 Μαρ 2010 7:25 πμ

  • Reg Soft error on SATA SSD with smartctl command

    Hi, When we run smarcli on SSD disk , we are seeing the below message from dmesg    (command :- ./smartctl -a -d sat /dev/rdsk/c0t500A0751093F1E6Fd0)
    SATA SSD disk is connected to system via SAS backplane
    dmesg
    ====================
    Nov 18 06:52:41 mondopodN61 scsi: [ID 107833 kern.notice]       Requested Block: 0                         Error Block: 0
    Nov 18 06:52:41 mondopodN61 scsi: [ID 107833 kern.notice]       Vendor: ATA                                Serial Number: BTTV3194030W
    Nov 18 06:52:41 mondopodN61 scsi: [ID 107833 kern.notice]       Sense Key: Soft_Error
    Nov 18 06:52:41 mondopodN61 scsi: [ID 107833 kern.notice]       ASC: 0x0 (<vendor unique code 0x0>), ASCQ: 0x1d, FRU: 0x0
    Nov 18 06:53:55 mondopodN61 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g500a0751093f1e6f (sd23):
    Nov 18 06:53:55 mondopodN61     Error for Command: <undecoded cmd 0x85>    Error Level: Recovered
    Nov 18 06:53:55 mondopodN61 scsi: [ID 107833 kern.notice]       Requested Block: 0                         Error Block: 0
    Nov 18 06:53:55 mondopodN61 scsi: [ID 107833 kern.notice]       Vendor: ATA                                Serial Number:         1324
    Nov 18 06:53:55 mondopodN61 scsi: [ID 107833 kern.notice]       Sense Key: Soft_Error
    Nov 18 06:53:55 mondopodN61 scsi: [ID 107833 kern.notice]       ASC: 0x0 (<vendor unique code 0x0>), ASCQ: 0x1d, FRU: 0x0
    Nov 18 06:54:15 mondopodN61 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g500a0751093f1e6f (sd23):
    Nov 18 06:54:15 mondopodN61     Error for Command: <undecoded cmd 0x85>    Error Level: Recovered
    Nov 18 06:54:15 mondopodN61 scsi: [ID 107833 kern.notice]       Requested Block: 0                         Error Block: 0
    Nov 18 06:54:15 mondopodN61 scsi: [ID 107833 kern.notice]       Vendor: ATA                                Serial Number:         1324
    Nov 18 06:54:15 mondopodN61 scsi: [ID 107833 kern.notice]       Sense Key: Soft_Error
    Nov 18 06:54:15 mondopodN61 scsi: [ID 107833 kern.notice]       ASC: 0x0 (<vendor unique code 0x0>), ASCQ: 0x1d, FRU: 0x0
    Nov 18 06:54:21 mondopodN61 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/disk@g500a0751093f1e6f (sd23):
    Nov 18 06:54:21 mondopodN61     Error for Command: <undecoded cmd 0x85>    Error Level: Recovered
    Nov 18 06:54:21 mondopodN61 scsi: [ID 107833 kern.notice]       Requested Block: 0                         Error Block: 0
    Nov 18 06:54:21 mondopodN61 scsi: [ID 107833 kern.notice]       Vendor: ATA                                Serial Number:         1324
    Nov 18 06:54:21 mondopodN61 scsi: [ID 107833 kern.notice]       Sense Key: Soft_Error
    Nov 18 06:54:21 mondopodN61 scsi: [ID 107833 kern.notice]       ASC: 0x0 (<vendor unique code 0x0>), ASCQ: 0x1d, FRU: 0x0
    ===
    Also softerror count is getting increased whenever we run smarcli command.
    ====================
    #iostat -Exni c0t500A0751093F1E6Fd0
                        extended device statistics
        r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
        1.3    2.4    4.7  271.9  0.0  0.0    0.0    1.2   0   0 c0t500A0751093F1E6Fd0
    c0t500A0751093F1E6Fd0 Soft Errors: 89 Hard Errors: 0 Transport Errors: 0
    Vendor: ATA      Product: Crucial_CT480M50 Revision: MU03 Device Id: id1,sd@n500a0751093f1e6f
    Size: 480.10GB <480103981056 bytes>
    Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 89
    Illegal Request: 0 Predictive Failure Analysis: 0
    ====================
    My query is after certain softerror count, will SSD go offline? Will this give any issue after some time?

    If this is the case, then this is on disk side or on driver side.
    Regarding the errors, please check this discussion in smartmontools forum :
    SourceForge.net: S.M.A.R.T. Monitoring Tools: smartmontools-support

  • Logs Error

    Dear All,
    Please check the logs
    Jan 13 13:17:25 aai-cms-app1 Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource cmscluster status
    msg on node aai-cms-app1 change to <LogicalHostname online.>
    Jan 13 13:19:50 aai-cms-app1 scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600c0ff00000000
    0098afd3426216600 (ssd1):
    Jan 13 13:19:50 aai-cms-app1 transport rejected fatal error
    Jan 13 13:19:50 aai-cms-app1 Cluster.scdpmd: [ID 977412 daemon.notice] The state of the path to devi
    ce: /dev/did/rdsk/d9s0 has changed to FAILED
    Jan 13 13:20:31 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 13:25:35 aai-cms-app1 last message repeated 2 times
    Jan 13 13:30:39 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 13:35:43 aai-cms-app1 last message repeated 1 time
    Jan 13 13:40:47 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 13:45:51 aai-cms-app1 last message repeated 2 times
    Jan 13 13:50:55 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 13:55:59 aai-cms-app1 last message repeated 1 time
    Jan 13 14:01:03 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:06:07 aai-cms-app1 last message repeated 2 times
    Jan 13 14:06:46 aai-cms-app1 md_stripe: [ID 641072 kern.warning] WARNING: md: appset/d200: write err
    or on /dev/did/dsk/d9s0
    Jan 13 14:07:12 aai-cms-app1 last message repeated 15 times
    Jan 13 14:07:12 aai-cms-app1 ufs: [ID 702911 kern.warning] WARNING: Error writing master during ufs
    log roll
    Jan 13 14:07:12 aai-cms-app1 ufs: [ID 127457 kern.warning] WARNING: ufs log for /volume1 changed sta
    te to Error
    Jan 13 14:07:12 aai-cms-app1 ufs: [ID 616219 kern.warning] WARNING: Please umount(1M) /volume1 and r
    un fsck(1M)
    Jan 13 14:10:34 aai-cms-app1 rsh[14764]: [ID 521673 daemon.notice] connection from 172.16.5.107 (172
    .16.5.107) - bad port
    Jan 13 14:10:34 aai-cms-app1 rlogind[14763]: [ID 776819 daemon.error] failed to receive protocol zer
    o byte
    Jan 13 14:10:35 aai-cms-app1 rlogind[14767]: [ID 776819 daemon.error] failed to receive protocol zer
    o byte
    Jan 13 14:10:35 aai-cms-app1 rsh[14768]: [ID 521673 daemon.notice] connection from 172.16.5.107 (172
    .16.5.107) - bad port
    Jan 13 14:10:37 aai-cms-app1 rlogind[14771]: [ID 776819 daemon.error] failed to receive protocol zer
    o byte
    Jan 13 14:10:37 aai-cms-app1 rsh[14772]: [ID 521673 daemon.notice] connection from 172.16.5.107 (172
    .16.5.107) - bad port
    Jan 13 14:10:37 aai-cms-app1 rlogind[14775]: [ID 776819 daemon.error] failed to receive protocol zer
    o byte
    Jan 13 14:10:37 aai-cms-app1 rsh[14776]: [ID 521673 daemon.notice] connection from 172.16.5.107 (172
    .16.5.107) - bad port
    Jan 13 14:10:40 aai-cms-app1 rlogind[14789]: [ID 521673 daemon.notice] connection from 172.16.5.107
    (172.16.5.107) - bad port
    Jan 13 14:10:40 aai-cms-app1 rsh[14790]: [ID 521673 daemon.notice] connection from 172.16.5.107 (172
    .16.5.107) - bad port
    Jan 13 14:10:40 aai-cms-app1 bsd-gw[14791]: [ID 937800 lpr.error] request to default (unknown printe
    r) from ::ffff:172.16.5.107
    Jan 13 14:11:11 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:16:15 aai-cms-app1 last message repeated 1 time
    Jan 13 14:21:19 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:26:23 aai-cms-app1 last message repeated 2 times
    Jan 13 14:31:27 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:36:31 aai-cms-app1 last message repeated 1 time
    Jan 13 14:41:35 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:46:39 aai-cms-app1 last message repeated 2 times
    Jan 13 14:51:43 aai-cms-app1 ntpdate[316]: [ID 398266 daemon.notice] waiting 300 seconds before tryi
    ng again
    Jan 13 14:56:47 aai-cms-app1 last message repeated 1 time
    root@aai-cms-app1 #

    You had similar post here:
    [http://forums.sun.com/thread.jspa?threadID=5422834]
    and here:
    [http://forums.sun.com/thread.jspa?threadID=5422836]
    Did you follow through?

  • Command timed out error shown frequently on SunFire v890 Server

    I've 3* SunFire v890 System with two Qlogic FC HBA each.
    Running Solaris 10 SPARC operating system
    These systems are running with Sun Cluster 3.2 and have many resources configured as Failover services.
    All these three systems are connected to a Sun StorageTek 3510 with multipathing enabled. For path redundancy, these servers are connected to storage through SAN Switch (Cisco MDS9000 series).
    Intermittently, each servers are getting the following messages logged in /var/adm/messages.
    +scsi: [ID 243001 kern.warning] WARNING: /scsi_vhci (scsi_vhci0):+
    scsi_vhci/ssd@g600c0ff0000000000b5e0d7f805d2c01 (ssd24): Command Timeout on path /pci@9,700000/SUNW,qlc@2/fp@0,0 (fp2)
    +scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g600c0ff0000000000b5e0d7f805d2c01 (ssd24):+
    SCSI transport failed: reason 'timeout': retrying command
    We are sure that the error comes from one of the FC Path to mapped storage volume. If we remove the FC link to the storage, the error stops. But the multipathing is getting degraded mode. When we enable both these path online, the error starts logged. Since these timedout errors are more, i also feel some small performance degradation if both these paths are online.
    To confirm this problem, I've tried replacing the Qlogic FC-HBA, interchanging the path to another FC Switch, changing of FC cables etc.,
    No improvement. Please suggest the best solution.
    Thanks
    Edited by: jbaluram on 2 Feb, 2010 3:54 PM

    Are these messages appears on only one node or all the three nodes connected to 3510 ?
    If it is coming from only one node, you may need to check if the SAN patches are updated or get the latest SFK (San Foundation Kit) installed on this node and check...
    How many LUNs are coming from this storage ? Also need to see if this errors are coming from only one LUN or from all (if more then one LUN ). What is the frequency of this message ?
    If patching can't be done due to any reason, its a good idea to log a service call with Sun.
    HTH

  • I am getting following errors "errors were retryable:

    I have out putted the following but have no idea what to do. I am thinking it might be a hba, fiber cable or hhd on storage.
    root@xxxxxzner01p-gz[~]# dmesg
    Monday, May 7, 2012 2:14:38 PM EDT
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1587374867 Error Block: 1587374867
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1587374867 Error Block: 1587374867
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f00000a00 (ssd33):
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f00000a00 (ssd33):
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1809006156 Error Block: 1809006156
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1809006156 Error Block: 1809006156
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F0A00
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F0A00
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1589392402 Error Block: 1589392402
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1589392402 Error Block: 1589392402
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:14:35 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:17:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:17:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1580228200 Error Block: 1580228200
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1580228200 Error Block: 1580228200
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:17:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:21:03 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:21:03 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1584839052 Error Block: 1584839052
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1584839052 Error Block: 1584839052
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:21:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000070e (ssd89):
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000070e (ssd89):
    May 7 13:22:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:22:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 443306111 Error Block: 443306111
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 443306111 Error Block: 443306111
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F070E
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F070E
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:22:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:24:03 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:24:03 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1587910407 Error Block: 1587910407
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1587910407 Error Block: 1587910407
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:24:03 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:29:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:29:33 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 837188597 Error Block: 837188597
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 837188597 Error Block: 837188597
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:29:33 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:32:19 xxxxxzner01p-gz scsi: [ID 243001 kern.info] /scsi_vhci (scsi_vhci0):
    May 7 13:32:19 xxxxxzner01p-gz /scsi_vhci/ssd@g60060e8005632f000000632f00001010 (ssd78): Command failed to complete (3) on path fp0/ssd@w50060e8005632f31,52
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:33:19 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:33:19 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 834850503 Error Block: 834850503
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 834850503 Error Block: 834850503
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:33:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:33:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:33:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 836551349 Error Block: 836551349
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 836551349 Error Block: 836551349
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:33:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f00000a00 (ssd33):
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f00000a00 (ssd33):
    May 7 13:43:50 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:43:50 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1810038035 Error Block: 1810038035
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1810038035 Error Block: 1810038035
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F0A00
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F0A00
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:43:50 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:48:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:48:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 836209124 Error Block: 836209124
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 836209124 Error Block: 836209124
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:48:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:49:19 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:49:19 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 830384056 Error Block: 830384056
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 830384056 Error Block: 830384056
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:49:19 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000210f (ssd35):
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000210f (ssd35):
    May 7 13:52:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:52:49 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1732780778 Error Block: 1732780778
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 1732780778 Error Block: 1732780778
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F210F
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F210F
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:52:49 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:59:21 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:59:21 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 330926295 Error Block: 330926295
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 330926295 Error Block: 330926295
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:59:21 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.warning] WARNING: /scsi_vhci/ssd@g60060e8005632f000000632f0000200f (ssd37):
    May 7 13:59:22 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:59:22 xxxxxzner01p-gz Error for Command: write(10) Error Level: Retryable
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 331846913 Error Block: 331846913
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Requested Block: 331846913 Error Block: 331846913
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Vendor: HITACHI Serial Number: 50 0632F200F
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] Sense Key: Aborted Command
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    May 7 13:59:22 xxxxxzner01p-gz scsi: [ID 107833 kern.notice] ASC: 0xc0 (<vendor unique code 0xc0>), ASCQ: 0x0, FRU: 0x0
    root@xxxxxzner01p-gz[~]# fcinfo hba-port
    HBA Port WWN: 21000024ff003071
    OS Device Name: /dev/cfg/c3
    Manufacturer: QLogic Corp.
    Model: 375-3355-02
    Firmware Version: 05.04.03
    FCode/BIOS Version: BIOS: 2.02; fcode: 2.01; EFI: 2.00;
    Serial Number: 0402H00-1010769293
    Driver Name: qlc
    Driver Version: 20110321-3.05
    Type: N-port
    State: online
    Supported Speeds: 1Gb 2Gb 4Gb
    Current Speed: 1Gb
    Node WWN: 20000024ff003071
    HBA Port WWN: 21000024ff002f05
    OS Device Name: /dev/cfg/c2
    Manufacturer: QLogic Corp.
    Model: 375-3355-02
    Firmware Version: 05.04.03
    FCode/BIOS Version: BIOS: 2.02; fcode: 2.01; EFI: 2.00;
    Serial Number: 0402H00-1010769378
    Driver Name: qlc
    Driver Version: 20110321-3.05
    Type: N-port
    State: online
    Supported Speeds: 1Gb 2Gb 4Gb
    Current Speed: 2Gb
    Node WWN: 20000024ff002f05
    root@xxxxxzner01p-gz[~]# fcinfo remote-port -slp 21000024ff002f05
    Remote Port WWN: 50060e8005632f21
    Active FC4 Types: SCSI
    SCSI Target: yes
    Node WWN: 50060e8005632f21
    Link Error Statistics:
    Link Failure Count: 0
    Loss of Sync Count: 0
    Loss of Signal Count: 0
    Primitive Seq Protocol Error Count: 0
    Invalid Tx Word Count: 0
    Invalid CRC Count: 0
    root@xxxxxzner01p-gz[~]# fcinfo remote-port -slp 21000024ff003071
    Remote Port WWN: 50060e8005632f31
    Active FC4 Types: SCSI
    SCSI Target: yes
    Node WWN: 50060e8005632f31
    Link Error Statistics:
    Link Failure Count: 261
    Loss of Sync Count: 55337
    Loss of Signal Count: 60
    Primitive Seq Protocol Error Count: 0
    Invalid Tx Word Count: 4294967295
    Invalid CRC Count: 0
    root@xxxxxzner01p-gz[~]# fcinfo hba-port -l 21000024ff002f05
    HBA Port WWN: 21000024ff002f05
    OS Device Name: /dev/cfg/c2
    Manufacturer: QLogic Corp.
    Model: 375-3355-02
    Firmware Version: 05.04.03
    FCode/BIOS Version: BIOS: 2.02; fcode: 2.01; EFI: 2.00;
    Serial Number: 0402H00-1010769378
    Driver Name: qlc
    Driver Version: 20110321-3.05
    Type: N-port
    State: online
    Supported Speeds: 1Gb 2Gb 4Gb
    Current Speed: 2Gb
    Node WWN: 20000024ff002f05
    Link Error Statistics:
    Link Failure Count: 1
    Loss of Sync Count: 0
    Loss of Signal Count: 0
    Primitive Seq Protocol Error Count: 0
    Invalid Tx Word Count: 0
    Invalid CRC Count: 0
    root@xxxxxzner01p-gz[~]# fcinfo hba-port -l 21000024ff003071
    HBA Port WWN: 21000024ff003071
    OS Device Name: /dev/cfg/c3
    Manufacturer: QLogic Corp.
    Model: 375-3355-02
    Firmware Version: 05.04.03
    FCode/BIOS Version: BIOS: 2.02; fcode: 2.01; EFI: 2.00;
    Serial Number: 0402H00-1010769293
    Driver Name: qlc
    Driver Version: 20110321-3.05
    Type: N-port
    State: online
    Supported Speeds: 1Gb 2Gb 4Gb
    Current Speed: 1Gb
    Node WWN: 20000024ff003071
    Link Error Statistics:
    Link Failure Count: 1
    Loss of Sync Count: 0
    Loss of Signal Count: 0
    Primitive Seq Protocol Error Count: 0
    Invalid Tx Word Count: 0
    Invalid CRC Count: 0
    Need help thanks,
    Mauricio

    Need help thanks,
    MauricioYou have error entries in your logs for bad blocks on four disk drives.
    ssd33
    ssd35
    ssd37
    ssd89
    Just a guess but they're all probably part of a RAID and one of them is the actual culprit with the other three are victims that are mirroring the bad read/writes.
    What to do?
    You need to use your service contract and log a support request (SR) with Oracle. They will ask for copies of your logs and will be able to walk you through all the steps in isolating the root issue. That's why you have a support contract on a beast such as your Hitachi array.
    It could be as simple as guiding you through various procedusres to mark the offending blocks bad and then rebuilding the RAID. If it's not simple, you may need to replace the questionable disk (which requires a service engineer).
    All that is too complex for an online discussion forum.

Maybe you are looking for

  • My iPod Touch 4th Gen isn't receiving messages,

    but only from certain people. And it is sending them fine. My friend is responding on a texting app I have, because iMessage is being so weird. Anyone else have this problem? Know how to fix it? I tried logging out and then back on to my iMessage, th

  • Help transferring to new intel iMac

    Hello, I will be getting a new intel iMac in the next week or two, to replace my failing revision A iMac G5. My problem is that the old machine will not be here anymore when the new machine arrives, and I want to make the transition as smooth as poss

  • How to test if file is  empty???

    I have written a program that reads from a text file. How do i check that the file is empty,stop reading and display an error message? Here is the code i have. try       { FileReader in = new FileReader(fileName);         BufferedReader reading= new

  • Does Verizon have an e-mail notification alert icon to go in the notification area of the taskbar?

    I'd like to be notified when I receive e-mail in my Verizon "In Box" . Does Verizon have such a notification? I'm referring to an icon in the notification area of the taskbar that says "You have mail" or something to that effect.

  • ADF Mobile runtime architecture

    In the developers guide is a note on page 1-4 saying that "ADF Model includes the local database". This is not only confusing in my opinion, but also wrong. The model should be indicated as the interface (or glue) between the UI and Business Logic. P