Yes, EMC.  I know nothing about the storage side.  According to them, 
everything is "ok" on their side.  Some days the storage guys remind me of the 
phrase "secret squirrel".  I'm trying to get more info...


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Raymond 
Higgs
Sent: Monday, August 29, 2011 11:06 AM
To: [email protected]
Subject: Re: SLES10 SP4 Linux and zFCP disk

I agree that the problem is probably outside of your z10.  I think there
is something wrong with your storage array.  What is it?  One of those
little EMC arrays?

> Configuring FCP disk 5006916030603a65:0000000000000000
>   Vendor: DGC       Model: RAID 5            Rev: 0226
>   Type:   Direct-Access                      ANSI SCSI revision: 04

It is not a zoning issue.  There wouldn't be messages about sense data if
the channel couldn't talk to the storage array.

Ray Higgs
System z FCP Firmware Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
[email protected]

Linux on 390 Port <[email protected]> wrote on 08/29/2011 10:37:43
AM:

> From: Pedro Principeza <[email protected]>
> To: [email protected]
> Date: 08/29/2011 10:45 AM
> Subject: Re: SLES10 SP4  Linux and zFCP disk
> Sent by: Linux on 390 Port <[email protected]>
>
> Greetings.
>
> The "Device Not Ready" errors (as shown on the logs you've mentioned)
are
> commonly originated from issues outside the Linux guest.
> LUN mapping, SAN Zoning and Host Type definitions come to my mind, in
> these cases.  Look for the SAN/Storage side.
>
> HTH,
> Pedro Principeza
>
>
>
> From:   "Ayers, Jennifer D" <[email protected]>
> To:     [email protected]
> Date:   29/08/2011 11:33
> Subject:        SLES10 SP4  Linux and zFCP disk
> Sent by:        Linux on 390 Port <[email protected]>
>
>
>
> We are attempting (unsuccessfully) to connect to a SAN disk via zFCP.
Port
> type is "NPort (fabric via point-to-point)".  The operating system in
our
> test instance is SUSE 10 SP4.
>
> We cannot partition or format the disk.  These are some the errors we
see
> when our instance is rebooted:
> Activating zfcp host 0.0.5000
> Configuring device 0.0.5000
> scsi0 : zfcp
> zfcp: The adapter 0.0.5000 reported the following characteristics:
> WWNN 0x5005976400c36e16, WWPN 0xc05976eba2000000, S_ID 0x000b1701,
> adapter version 0x5, LIC version 0x302
> zfcp: Switched fabric fibrechannel network detected at adapter 0.0.5000.
> Activating zfcp disk 0.0.5000:0x5006916030603a65:0x0000000000000000
> No configuration file for adapter 0.0.5000
> Configuring FCP disk 5006916030603a65:0000000000000000
>   Vendor: DGC       Model: RAID 5            Rev: 0226
>   Type:   Direct-Access                      ANSI SCSI revision: 04
> SCSI device sda: 41943040 512-byte hdwr sectors (21475 MB)
> sda: test WP failed, assume Write Enabled
> sda: asking for cache data failed
> sda: assuming drive cache: write through
> SCSI device sda: 41943040 512-byte hdwr sectors (21475 MB)
> sda: test WP failed, assume Write Enabled
> sda: asking for cache data failed
> sda: assuming drive cache: write through
>  sda:<6>sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
>  unable to read partition table
> sd 0:0:0:0: Attached scsi disk sda
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 41942912
> Buffer I/O error on device sda, logical block 5242864
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
> Buffer I/O error on device sda, logical block 0
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 41943032
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 41943032
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 41943032
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>     Additional sense: Logical unit not ready, manual intervention
required
> end_request: I/O error, dev sda, sector 41943032
> sd 0:0:0:0: Device not ready: <6>: Current: sense key: Not Ready
>
> I had to manually add a LUN 0 in order to see anything at all.  Also,
one
> day the disk appears as a /dev/sda and then another it may appear as
> /dev/sg0, or worse -- /dev/.tmp.
>
> Configuration and setup of zFCP is new to us.  Any light you can shed as
> to why we are encountering these errors would be appreciated.
>
> Jennifer Ayers
> State of West Virginia
> Office of Technology
> 304-957-8294
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>
>
>
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO LINUX-390 or
visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> ----------------------------------------------------------------------
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Reply via email to