Public bug reported:

My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC
devices in general. I'm running with Ubuntu 20.04
kernel-5.4.0-9-generic.

There are the HBAs I'm running with:

root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name
QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k
QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k
QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k
QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k

lsscsi and multipath -ll don't seem to see my SCSI devices:

root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll
root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi
[0:0:0:0]    cd/dvd  KVM      vmDisk-CD        0.01  /dev/sr0
[1:0:0:0]    cd/dvd  HL-DT-ST DVDRAM GUD0N     PF02  /dev/sr1
[3:0:0:0]    disk    ATA      ST1000NX0313     SNA3  /dev/sda

It doesn't appear to be a configuration/hardware issue as installing
Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI
devices.

root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd
Description:    Ubuntu Focal Fossa (development branch)
Release:        20.04
root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 5.4.0.9.11
  Candidate: 5.4.0.9.11
  Version table:
 *** 5.4.0.9.11 500
        500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 
Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-generic 5.4.0.9.11
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116,  1 Jan 23 11:32 seq
 crw-rw---- 1 root audio 116, 33 Jan 23 11:32 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Thu Jan 23 15:04:42 2020
InstallationDate: Installed on 2020-01-23 (0 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200107)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: FUJITSU PRIMERGY RX2540 M4
PciMultimedia:
 
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 mgag200drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 
console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic  N/A
 linux-firmware                           1.184
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2019
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x
dmi.board.name: D3384-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3384-A13 WGS04 GS04
dmi.chassis.asset.tag: System Asset Tag
dmi.chassis.type: 23
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: RX2540M4R4
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4:
dmi.product.family: SERVER
dmi.product.name: PRIMERGY RX2540 M4
dmi.product.sku: S26361-K1567-Vxxx
dmi.sys.vendor: FUJITSU

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860724

Title:
  QLogic Direct-Connect host can't see SCSI-FC devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to