UNSOLVED

jheller2

updated

19 years ago

J

jheller2

5 Posts

0

781

April 15th, 2008 00:00

RHEL4 + Emulex scsi errors

Hardware:
EMC Clariion CX3-10
HP BL460c Blade Server with Emulex LPe1105 dual HBA

Software: RHEL4 U6 with included Emulex driver 8.0.16.34
PowerPath for Linux 5.1

It all appears to work OK, however there are regular SCSI errors logged.

SCSI error : <0 0 0 0> return code = 0x70000
and
SCSI error : <0 0 0 0> return code = 0x60000

We also have RHEL5 U1 systems on the same hardware, but there are no errors there.

Should I be concerned about these errors and is there a way to stop them?
  • xe2sdc

    6 Operator

    •

    2831 Posts

    195

    0

    Posted April 15th, 2008 10:00

    Jheller can you post the output of the following commands ??

    * syminq
    * cat /proc/scsi/scsi
    * find /proc/scsi

    ThX ..
  • SKT2

    2 Intern

    •

    1340 Posts

    195

    0

    Posted April 15th, 2008 10:00

    when did the system was updated to update 6

    After the update/kernel upgrade the third party drivers need to be reinstalled like power path.

    Also if the lpfc module is invloved then that need to be recompiled as the linux kernel dont have a built in driver . But with qlogic card there is no re-compile required unlike lpfc.
  • jheller2

    5 Posts

    195

    0

    Posted April 15th, 2008 22:00

    Stefano

    I don't have syminq. I gather its part of the Symetrix CLI. We have a Clariion and I can't find the Symetrix CLI on Powerlink.

    # cat /proc/scsi/scsi
    Attached devices:
    Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: DGC Model: RAID 5 Rev: 0326
    Type: Direct-Access ANSI SCSI revision: 04

    ]# find /proc/scsi
    /proc/scsi
    /proc/scsi/lpfc
    /proc/scsi/lpfc/1
    /proc/scsi/lpfc/0
    /proc/scsi/device_info
    /proc/scsi/scsi


    santhosh,
    RHEL4 U6 is the first installation. There has been no upgrade. It includes the lpfc driver. These are new systems, but we need to run RHEL4 to use PHP4.
  • jheller2

    5 Posts

    195

    0

    Posted April 28th, 2008 20:00

    This appears to be resolved by installing Emulex driver version 8.0.16.40, available from the Emulex web site.