Victor, I'm more familiar with lsluns. The scsi 0:0:0:49409 probably indicates "scan LUNS" tries to bring lun0 online, that fails, so then it brings online the wlun ( eg. scsi 0:0:0:49409: Attached scsi generic sg12 ) but the 2145 is an IBM SAN Volume Controller (SVC) and with a SVC, the sg_luns using 49409 will fail with a "Report Luns command has bad field in cdb".
This appears to indicate that lun0 isn't available. I don't know of a
reason that bringing lun0 online will fail other than lun masking is used
on the Storage Array or another Guest is using it ( however in this case
you would see something like "LUN 0x0 on port 0x5005076801100f82 is already
in use by CSS0, MIF Image ID 1" ).
Mike O'Reilly
IBM Linux Change Team
Victor Echavarry
Diaz
<vechavarry@evert To
ecinc.com> LINUX-390@vm.marist.edu,
Sent by: Linux on cc
390 Port
<linux-...@vm.mar Subject
ist.edu> Re: LUN error on SLES 11SP3
04/11/2014 07:23
AM
Please respond to
Linux on 390 Port
<linux-...@vm.mar
ist.edu>
This is the error when you do scan LUNS from YAST ZFCP get LUNS option.
Apr 11 10:14:18 l221t login[3859]: PAM unable to dlopen
(/lib/security/pam_limits.so): /lib/security/pam_limits.so: wrong ELF
class: ELFCLASS32
Apr 11 10:14:18 l221t login[3859]: PAM adding faulty
module: /lib/security/pam_limits.so
Apr 11 10:14:48 l221t sshd[24806]: Accepted keyboard-interactive/pam for
root from 10.1.49.120 port 2573 ssh2
Apr 11 10:18:34 l221t sshd[24926]: Accepted keyboard-interactive/pam for
root from 10.1.49.120 port 2617 ssh2
Apr 11 10:19:13 l221t kernel: scsi 0:0:0:49409: Direct-Access IBM
2145 0000 PQ: 1 ANSI: 6
Apr 11 10:19:13 l221t kernel: scsi 0:0:0:49409: alua: disable for WLUN
Apr 11 10:19:13 l221t kernel: scsi 0:0:0:49409: alua: not attached
Apr 11 10:19:13 l221t kernel: scsi 0:0:0:49409: Attached scsi generic sg12
type 0
Apr 11 10:19:15 l221t kernel: alua: release port group 0
Apr 11 10:19:15 l221t kernel: sd 0:0:0:0: alua: Detached
Regards,
Victor Echavarry
System Programmer, EVERTEC LLC
-----Original Message-----
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark
Post
Sent: Thursday, April 10, 2014 4:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LUN error on SLES 11SP3
>>> On 4/10/2014 at 03:32 PM, Victor Echavarry Diaz
<vechava...@evertecinc.com>
wrote:
> One of our Unix administrator send to me the following e-mail:
>
>
> Hi Victor;
>
> When I add a SAN disk I get the messages " Unable to activate LUN 0" from
de
> yast.
>
> The server is SUSE Linux Enterprise Server 11 SP3 with the last updates.
>
> It accessing a IBM 7000 storage model. We have other Z/Linux server
attached
> to this SAN, is working ok but is SLES 11 SP2. Do anyone know about it?
This can happen when using NPIV and enabling automatic LUN scanning in the
kernel (the allow_lun_scan parameter). If you have this enabled, there is
a fix available for it that was originally created for SLES12, but could
probably be used for SLES11 SP3.
Mark Post
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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/
WARNING: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please delete it
immediately.
Please note that any views or opinions presented in this email are solely
those
of the author and do not necessarily represent those of EVERTEC, Inc. or
its
affiliates. Finally, the integrity and security of this message cannot be
guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates
accept
no liability for any damage caused by any virus transmitted by this email.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
<<inline: ecblank.gif>>
<<inline: graycol.gif>>
<<inline: pic57646.gif>>
