The problem happens only when Boot option is set to BIOS. With UEFI boot, kernel 5.10.0 detects disks properly. Kernel 4.19 detects disks in both cases.

Hi,

On Sat, Sep 04, 2021 at 11:23:59AM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=214311
> 
>             Bug ID: 214311
>            Summary: megaraid_sas - no disks detected
>            Product: IO/Storage
>            Version: 2.5
>     Kernel Version: 5.10.0
>           Hardware: Intel
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: blocking
>           Priority: P1
>          Component: SCSI
>           Assignee: linux-scsi@vger.kernel.org
>           Reporter: jarek@poczta.srv.pl
>         Regression: No
> 
> Dell R340 with PERC H330 - disks not detected.
> 
> lspci:
> 
> 02:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 3008
> [Fury] (rev 02)
> 
> dmesg:
> 
> megaraid_sas 0000:02:00.0: Performance mode :Latency
> megaraid_sas 0000:02:00.0: FW supports sync cache: No
> megaraid_sas 0000:02:00.0: megasas_disable_intr_fusion is called
> outband_intr_mask:0x40000009
> megaraid_sas 0000:02:00.0: Ignore DCMD timeout: megasas_get_ctrl_info 5274
> megaraid_sas 0000:02:00.0: Could not get controller info. Fail from
> megasas_init_adapter_fusion 1865
> megaraid_sas 0000:02:00.0: Failed from megasas_init_fw 6406
> 
> This machine works OK with kernel 4.19.0. Debian 11, Clonezilla 2.7.3-19 does
> not detect disks.

This sounds very similar to one bug report which was reported
downstream in Debian at https://bugs.debian.org/992304

Followup to the bugzilla bug 214311
(https://bugzilla.kernel.org/show_bug.cgi?id=214311) suggests that it
works when booting with BIOS, not with UEFI boot.

Regards,
Salvatore

Hi,

I reported the bug in the Debian bug tracker.

I confirm that in (Legacy) BIOS mode the disk array is not visible and in UEFI mode is visible.

Kind regards,
Nikolay

Hi,

In fact this bug is blocker for us with respect to bug tracker https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992304 , is there any workaround available for this or an early fix is anticipated? 

Regards,
Jaikumar

Driver fails to get controller information from controller firmware which leads to the driver load failure and disks don't get exposed to OS.
It may be the controller firmware problem. Please ensure the latest controller firmware is flashed. If the issue persists with the latest controller firmware, please contact Broadcom support channel.

But surprisingly, Debian 10 has no issues in terms of disk detection and installation of OS in headless mode but on Debian 11 it fails?
Debian 10 has 4.19.x kernel and Debian 11 has 5.10.x kernel (which is exposing this behavior)? Just out of curiosity, what leads to this failure?
So, 5.10 kernel interaction with same RAID controller firmware is suspiciously broken?
More clarity on this would lead to issues detection and fixes.
Thanks!

Same problem with the Dell PowerEdge T140 with LSI MegaRAID SAS-3 3008 
[Fury] (rev 02) and linux-image-5.10.0-19-amd64 (NO UEFI)

No problem booting with the old 4.19.0-22-amd64 kernel

(In reply to Gabriel Rolland from comment #7)
> Same problem with the Dell PowerEdge T140 with LSI MegaRAID SAS-3 3008 
> [Fury] (rev 02) and linux-image-5.10.0-19-amd64 (NO UEFI)
> 
> No problem booting with the old 4.19.0-22-amd64 kernel


The problem is still present with linux-image-5.19.11 :-(

I had the same problem with Dell Poweredge R340 and RAID0. I could not verify with UEFI because If UEFI is enable it does not detect the VirtualDisk.

My fix for linux-image-5.10.0-26-amd64 was adding to grub CMDLINE "intel_iommu=on iommu=pt"