'lsluns' command not working as expected on a system running RHEL on IBM System Z mainframe under the z/VM hypervisor.
Issue
- Recently on a small number of RHEL guests we added some new LUNs (SCSI ID 9 and 10) and removed some old LUNs (SCSI ID 0,1,3,4,5,6,7,8). The LUN with SCSI ID 2 was left. All went well apart from that now the lsluns command fails with an error "Unable to send the REPORT_LUNS command to LUN" as follows:
lsluns
Scanning for LUNs on adapter 0.0.a000
at port 0x50050768023059a7:
Unable to send the REPORT_LUNS command to LUN.
at port 0x50050768024059a6:
Unable to send the REPORT_LUNS command to LUN.
Scanning for LUNs on adapter 0.0.b000
at port 0x50050768023059a6:
Unable to send the REPORT_LUNS command to LUN.
at port 0x50050768024059a7:
Unable to send the REPORT_LUNS command to LUN.
The lsluns command is part of the s390utils-base RPM. It usually works like this:
Scanning for LUNs on adapter 0.0.a000
at port 0x50050768021059a7:
0x0000000000000000
0x0001000000000000
0x0002000000000000
at port 0x50050768022059a6:
0x0000000000000000
0x0001000000000000
0x0002000000000000
Scanning for LUNs on adapter 0.0.b000
at port 0x50050768021059a6:
0x0000000000000000
0x0001000000000000
0x0002000000000000
at port 0x50050768022059a7:
0x0000000000000000
0x0001000000000000
0x0002000000000000
Environment
- Red Hat Enterprise Linux
- IBM System Z mainframe under the z/VM hypervisor, i.e. the s390x architecture
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.