public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Dell PowerEdge T140, megaraid, BIOS Boot...
Date: Fri, 2 May 2025 17:21:05 +0200	[thread overview]
Message-ID: <vf4fel-i3o2.ln1@leia.lilliput.linux.it> (raw)


I've just upgraded to PVE8 a little cluster built with an PowerEdge T340
(boot in UEFI mode) and an T140 (boot in BIOS mode).

T340 works like a charme; T140 after rebooting panicked because cannot find
root filesystem; looking carefully at kernel log revealed that disks get not
recognized, and going deeper lead me to:

 gaio@leia:~$ grep megaraid T140_boot_log.txt
 [   31.952470] megaraid_sas 0000:01:00.0: FW now in Ready state
 [   31.952472] megaraid_sas 0000:01:00.0: 63 bit DMA mask and 32 bit consistent mask
 [   31.952624] megaraid_sas 0000:01:00.0: firmware supports msix        : (96)
 [   31.952750] megaraid_sas 0000:01:00.0: requested/available msix 5/5 poll_queue 0
 [   31.952752] megaraid_sas 0000:01:00.0: current msix/online cpus      : (5/4)
 [   31.952753] megaraid_sas 0000:01:00.0: RDPQ mode     : (disabled)
 [   31.952758] megaraid_sas 0000:01:00.0: Current firmware supports maximum commands: 928        LDIO threshold: 237
 [   31.954076] megaraid_sas 0000:01:00.0: Performance mode :Latency (latency index = 1)
 [   31.954078] megaraid_sas 0000:01:00.0: FW supports sync cache        : No
 [   31.954080] megaraid_sas 0000:01:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
 [   32.362294] megaraid_sas 0000:01:00.0: Ignore DCMD timeout: megasas_get_ctrl_info 5382
 [   32.665126] megaraid_sas 0000:01:00.0: Could not get controller info. Fail from megasas_init_adapter_fusion 1907
 [   32.908139] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6539

googling a bit lead me to some forum and pages; after some test i've added
to kernel boot parameters:

	iommu=pt

and now server boot flawlessy.


The two servers have different hardware but share the same BIOS, so this
lead to me to the hypotesis that the new megaraid_sas kernel driver depend
on UEFI initialization to work, or something like this.

Also, i've understood that 'pt' mean 'PassThrought', but i've not clear what
overral consequences (performance, stability, ...) have this options.


I'm seeking feedback. Thanks.

-- 



_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user


             reply	other threads:[~2025-05-02 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 15:21 Marco Gaiarin [this message]
2025-05-02 17:03 ` RolandK via pve-user
     [not found] ` <b7165214-1db9-46a8-8d9d-2e8cb5cd1c6c@web.de>
2025-05-14 20:38   ` Marco Gaiarin
2025-05-14 20:46     ` Arjen via pve-user
2025-05-16 13:43       ` Marco Gaiarin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vf4fel-i3o2.ln1@leia.lilliput.linux.it \
    --to=gaio@lilliput.linux.it \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal