HSG60 SCSI write abort on unit, not disk

From: Akkermans, Maurice (maurice.akkermans_at_tellabs.com)
Date: 09/21/05

  • Next message: Shaun.Racine_at_intier.com: "Can xemacs be removed?"
    Date: Wed, 21 Sep 2005 20:14:50 +0200
    To: tru64-unix-managers@ornl.gov
    
    

    Hi,

    I have a HSG60 controller with mirror sets on it. I get often, several
    times a day, the below error message. In this case the unit number 27 is
    a disk defined on a mirror set. I do not understand what produces the
    error, because the Device ID and Device Serial Number are empty.
    Occasionaly I have disk errors on my trucluster, because of this.
    I have just updated firmware on some of my disks, so now all my disks
    have the latest firmware, if that should have made a difference.
    I have also included the description of the Instance and the SCSI
    Command Opcode.

    Does anybody have an idea?

    Regards,
    Maurice

    %EVL--HSG60 InT Clu>--21-SEP-2005 19:36:39-- Instance Code: 0258000A
     Template: 81.(51)
     Occurred on 21-SEP-2005 at 19:36:39
     Power On Time: 4. Years, 274. Days, 1. Hours, 33. Minutes, 19. Seconds
     Controller Model: HSG60
     Serial Number: ZG01800722 Hardware Version: E11(29)
     Software Version: V87L-4(BB)
     Informational Report
     Unit Number: 27.(001B)
     Unit Software Version: 1.(01) Unit Hardware Version: 55.(37)
     Retry Level: 1. Retries: 1.
     Port: 255. Target: 255. LUN: 255.
     SCSI Device Type: 0.(00)
     Device ID: "" Device Serial Number: ""
     Device Software Revision Level: ""
     SCSI Command Opcode: 42.(2A)
     Sense Data Qualifiers: 64.(40)
     SCSI Sense Data:
      Error Code: 112.(70) {current command execution}
      Information field is valid
      Segment: 0.(00)
      Sense Key: 11.(0B) ABORTED COMMAND
      ILI: 0 EOM: 0 FM: 0
      Information: 021E8426
      Additional Sense Length: 10.(0A)
      Command-Specific Information: 00000000
      ASC: 0.(00) ASCQ: 6.(06)
      FRU: 0.(00) Sense-Key Specific: 000000
     Instance Code: 0258000A

    FMU> desc inst 0258000A
     Instance Code: 0258000A Description:
      This command was aborted prior to completion. The Information field of
    the
      Device Sense Data contains the block number of the first block in
    error.
     Reporting Component: 2.(02) Description:
      Value Added Services
     Reporting component's event number: 88.(58)
     Event Threshold: 10.(0A) Classification:
      SOFT. An unexpected condition detected by a controller software
    component
      (e.g., protocol violations, host buffer access errors, internal
      inconsistencies, uninterpreted device errors, etc.) or an intentional
      restart or shutdown of controller operation is indicated.

    FMU> desc scsi 2a 0
     SCSI Command Opcode: 42.(2A) Description:
       WRITE (10 byte)
     SCSI Device Type: 0.(00) Description:
      Direct-Access Devices (e.g., magnetic disk).
    ============================================================
    The information contained in this message may be privileged
    and confidential and protected from disclosure. If the reader
    of this message is not the intended recipient, or an employee
    or agent responsible for delivering this message to the
    intended recipient, you are hereby notified that any reproduction,
    dissemination or distribution of this communication is strictly
    prohibited. If you have received this communication in error,
    please notify us immediately by replying to the message and
    deleting it from your computer. Thank you. Tellabs
    ============================================================


  • Next message: Shaun.Racine_at_intier.com: "Can xemacs be removed?"

    Relevant Pages

    • bug in solaris 9/10 libsmedia.so, when using the uscsi request sense extension
      ... A scsi command failing with a "check status" runs an automatic scsi ... REQUEST SENSE command, and returns a valid uscsi_rqstatus and a valid ... but the request sense data returned from the scsi ...
      (comp.unix.solaris)
    • Drive errors on HSZ50 controller
      ... When connecting to one of HSZ50 controllers, ... SCSI Command Opcode: 40. ... Sense Data Qualifiers: 128. ... Error Code: 112.{current command execution} ...
      (comp.sys.dec)
    • Re: SATA HD & DMA ?
      ... You need GnuPG to verify this message ... > other* hdparm options fail on SCSI drives. ... recognizes the device (scsi0: 3ware Storage Controller) through ... Type help <command> to get more details about a particular ...
      (comp.os.linux.hardware)
    • Re: UC07 with BA350/RZ28 disk spinup problem
      ... VMS did not have SCSI drivers (or its SCSI ... command to a SCSI "spin up" command. ... to the controller configuration, at which point you can issue SCSI ... as far as the DSA/RA series disks, ...
      (comp.os.vms)
    • PC8477 Demo Program
      ... The PC8477 Demo Program is designed to allow access to all software commands and registers of National Semiconductor's PC8477 Advanced Floppy Disk Controller. ... The left center indicates the number of bytes transferred during the last command issued. ...
      (comp.sys.ibm.ps2.hardware)