Problems with connecting redhat 3 ES server to eva

Tobias Speckbacher TSpeckbacher at quova.com
Mon Apr 3 17:26:15 UTC 2006



> -----Original Message-----
> From: redhat-list-bounces at redhat.com [mailto:redhat-list-
> bounces at redhat.com] On Behalf Of Bliss, Aaron
> Sent: Monday, April 03, 2006 9:31 AM
> To: General Red Hat Linux discussion list
> Subject: Problems with connecting redhat 3 ES server to eva
> 
> I'm having some problems with connecting redhat 3 ES server to eva;
Any
> ideas?
> When attempting to fdisk /dev/sda; fidsk reports Unable to read
/dev/sda
> The following shows up after unloading and re-loading the device
driver:

What host type is the linux host configured as on the EVA (check in
command view under hosts) ?

Which version of the Controller software are you running ? (check
hardware - rack 1 - controller enclosure - controller a or b in command
view)
It is listed as software version.

Run hp_rescan on the host and send the output.

How many vdisks are presented to the host, what are their assigned luns
?

What does dmesg |grep sd return ?

I have a hunch but would like to confirm it with the data above.

-Tobias

> 
> /var/log/messsages after loading the qla driver:
> Apr  3 12:22:51 ms-lnx-s20 kernel: Attached scsi generic sg0 at scsi0,
> channel 0, id 0, lun 0,  type 12
> Apr  3 12:22:51 ms-lnx-s20 kernel: Attached scsi disk sda at scsi0,
> channel 0, id 0, lun 1
> Apr  3 12:22:51 ms-lnx-s20 kernel: resize_dma_pool: unknown device
type
> 12
> Apr  3 12:22:51 ms-lnx-s20 kernel: SCSI device sda: 293601280 512-byte
> hdwr sectors (150324 MB)
> Apr  3 12:22:51 ms-lnx-s20 kernel: sda:<6>Device 08:00 not ready.
> Apr  3 12:22:51 ms-lnx-s20 kernel: I/O error: dev 08:00, sector 0
> Apr  3 12:22:51 ms-lnx-s20 kernel: Device 08:00 not ready.
> Apr  3 12:22:51 ms-lnx-s20 kernel: I/O error: dev 08:00, sector 0
> Apr  3 12:22:51 ms-lnx-s20 kernel: unable to read partition table
> Apr  3 12:23:11 ms-lnx-s20 kernel: Device 08:00 not ready.
> Apr  3 12:23:11 ms-lnx-s20 kernel: I/O error: dev 08:00, sector 0
> 
> The folowing shows up in /proc/scsi/qla2300/0
> /proc/scsi/qla2300/0:
> QLogic PCI to Fibre Channel Host Adapter for QLA2340         :
>         Firmware version:  3.03.11, Driver version 7.05.00p8
> Entry address = f8843060
> HBA: QLA2312 , Serial# S02722
> Request Queue = 0x37710000, Response Queue = 0x1b0e0000
> Request Queue count= 512, Response Queue count= 512
> Total number of active commands = 0
> Total number of interrupts = 8
> Total number of IOCBs (used/max) = (0/600)
> Total number of queued commands = 0
>     Device queue depth = 0x20
> Number of free request entries = 500
> Number of mailbox timeouts = 0
> Number of ISP aborts = 0
> Number of loop resyncs = 0
> Number of retries for empty slots = 0
> Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
> Host adapter:loop state= <READY>, flags= 0x860813
> Dpc flags = 0x0
> MBX flags = 0x0
> SRB Free Count = 4096
> Link down Timeout = 008
> Port down retry = 030
> Login retry count = 030
> Commands retried with dropped frame(s) = 0
> Configured characteristic impedence: 50 ohms
> Configured data rate: 1-2 Gb/sec auto-negotiate
> 
> 
> SCSI Device Information:
> scsi-qla0-adapter-node=200000e08b1be281;
> scsi-qla0-adapter-port=210000e08b1be281;
> scsi-qla0-target-0=50001fe150047c68;
> 
> SCSI LUN Information:
> (Id:Lun)  * - indicates lun is not registered with the OS.
> ( 0: 0): Total reqs 1, Pending reqs 0, flags 0x0, 0:0:81,
> ( 0: 1): Total reqs 7, Pending reqs 0, flags 0x0, 0:0:81,
> 
> www.preferredcare.org
> "An Outstanding Member Experience," Preferred Care HMO Plans -- J. D.
> Power and Associates
> 
> Confidentiality Notice:
> The information contained in this electronic message is intended for
the
> exclusive use of the individual or entity named above and may contain
> privileged or confidential information.  If the reader of this message
is
> not the intended recipient or the employee or agent responsible to
deliver
> it to the intended recipient, you are hereby notified that
dissemination,
> distribution or copying of this information is prohibited.  If you
have
> received this communication in error, please notify the sender
immediately
> by telephone and destroy the copies you received.
> 
> 
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list




More information about the redhat-list mailing list