My Oracle Support Banner

OLVM: Not able to add new disk and it is showing locked (Doc ID 2920662.1)

Last updated on JUNE 12, 2024

Applies to:

Linux OS - Version Oracle Linux 7.9 with Unbreakable Enterprise Kernel [5.4.17] and later
Information in this document applies to any platform.

Symptoms

On Oracle Linux Virtualization Manager (OLVM), the system is not able to add new disk and it is showing locked. Please refer to the detailed error messages below.

ERROR
-----------------------
--dmidecode
System Information
Manufacturer: <Hardware Vendor Nane>
Product Name: <Hardware Vendor Product/Brand>
BIOS Information
Vendor: <Hardware Vendor BIOS Information>
Version: 57040400
Release Date: 12/21/2020

--lspci
11:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
11:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
11:00.2 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
11:00.3 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
45:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
45:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
45:00.2 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
45:00.3 Ethernet controller [0200]: Intel Corporation Ethernet Controller X710/X557-AT 10GBASE-T [8086:1589] (rev 02)
4b:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GBASE-T [8086:37d2] (rev 09)
4b:00.1 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GBASE-T [8086:37d2] (rev 09)
4b:00.2 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GBASE-T [8086:37d2] (rev 09)
4b:00.3 Ethernet controller [0200]: Intel Corporation Ethernet Connection X722 for 10GBASE-T [8086:37d2] (rev 09)
85:00.0 Fibre Channel [0c04]: QLogic Corp. ISP2722-based 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) <= (1) This Fiber Channel Card has a Firmware Bug. Please refer to the Firmware Bug on HW PCI Address “0000:85:00.0: [Firmware Bug]: “ from the Firmware Status below…!!!!
85:00.1 Fibre Channel [0c04]: QLogic Corp. ISP2722-based 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) <= (2) This Fiber Channel Card has a Firmware Bug. Please refer to the Firmware Bug on HW PCI Address “0000:85:00.1: [Firmware Bug]: “ from the Firmware Status below…!!!!
c5:00.0 Fibre Channel [0c04]: QLogic Corp. ISP2722-based 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) <= (3) This Fiber Channel Card has a Firmware Bug. Please refer to the Firmware Bug on HW PCI Address “0000:c5:00.0: [Firmware Bug]: “ from the Firmware Status below…!!!!
c5:00.1 Fibre Channel [0c04]: QLogic Corp. ISP2722-based 16/32Gb Fibre Channel to PCIe Adapter [1077:2261] (rev 01) <= (4) This Fiber Channel Card has a Firmware Bug. Please refer to the Firmware Bug on HW PCI Address “0000:c5:00.1: [Firmware Bug]: “ from the Firmware Status below…!!!!

—Checked Firmware Status
[ 2.067061] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.448830] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 2.703758] pci 0000:85:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) <=== (1)
[ 2.703761] pci 0000:85:00.1: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) <=== (2)
[ 2.703932] pci 0000:c5:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) <=== (3)
[ 2.703935] pci 0000:c5:00.1: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) <=== (4)

—Checked system messages
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:149: [sdfj] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:139: [sdez] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:150: [sdfk] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:144: [sdfe] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:143: [sdfd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:147: [sdfh] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:146: [sdfg] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:145: [sdff] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:142: [sdfc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:148: [sdfi] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:140: [sdfa] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:141: [sdfb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:138: [sdey] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:146: [sdfg] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:150: [sdfk] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:141: [sdfb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:142: [sdfc] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:139: [sdez] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:143: [sdfd] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:147: [sdfh] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:138: [sdey] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:149: [sdfj] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:145: [sdff] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:148: [sdfi] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:144: [sdfe] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jan 10 19:06:35 kvm-host kernel: sd 4:0:0:140: [sdfa] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE

NOTE: This resulted the KVM host OS (Operating System) failed to “Read the Storage Capacity” due to the Firmware Bugs in the affected Fiber Channel HBA Cards/Interfaces.

Changes

N/A

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.