Version 4.1 on Perc X10 controller in IT mode doesn't detect drives
Obelisk
3 Posts
March 10, 2026, 12:47 pmQuote from Obelisk on March 10, 2026, 12:47 pmAll,
Comparing installations of version 4.1.0 to the previous 4.0.0, we have identified that on 4.1 drives connected to the Dell Perc H310 controller in SAS9211-8i IT mode firmware are not visible.
In version 4.0.0, all drives are visible.
Based on the test results, it appears that a newer version is missing a driver or requires additional configuration.
Please advise.
Thank you All.
All,
Comparing installations of version 4.1.0 to the previous 4.0.0, we have identified that on 4.1 drives connected to the Dell Perc H310 controller in SAS9211-8i IT mode firmware are not visible.
In version 4.0.0, all drives are visible.
Based on the test results, it appears that a newer version is missing a driver or requires additional configuration.
Please advise.
Thank you All.
admin
3,073 Posts
March 10, 2026, 9:50 pmQuote from admin on March 10, 2026, 9:50 pmThanks for the feedback.
Can you please post output of
dmesg | grep firmware
Thanks for the feedback.
Can you please post output of
dmesg | grep firmware
Obelisk
3 Posts
March 12, 2026, 9:15 amQuote from Obelisk on March 12, 2026, 9:15 amThnak you,
dmesg | grep firmware
1.013632] GHES: APEI firmuare first mode is enabled by APEI bit and WHEA _OSC
This is the output from the running version 4.0
Tried to temporarily exit into a shell during the installation to capture the data, but that seems to be locked out.
Thnak you,
dmesg | grep firmware
1.013632] GHES: APEI firmuare first mode is enabled by APEI bit and WHEA _OSC
This is the output from the running version 4.0
Tried to temporarily exit into a shell during the installation to capture the data, but that seems to be locked out.
Last edited on March 12, 2026, 9:17 am by Obelisk · #3
admin
3,073 Posts
March 12, 2026, 12:54 pmQuote from admin on March 12, 2026, 12:54 pmCan you check on running PtaSAN 4.0
lspci -k
and check if the mpt2sas is in use by the controller?
PetaSAN 4.1 kernel is based on latest RHEL 10.1 (dec 2025) 6.12 kernel.
It uses newer mpt3sas driver instead of older mpt2sas, but some older devices are not supported.
From Google:
Based on the provided search results and the official lifecycle of RHEL, the mpt2sas driver is likely obsolete or requires third-party support in RHEL 10.
Removal of Older Drivers: RHEL 8 and RHEL 9 deprecated many older SAS-2 controller drivers, with ELRepo often acting as the source for kmod-mptsas or mpt3sas for newer kernels.
Can you check on running PtaSAN 4.0
lspci -k
and check if the mpt2sas is in use by the controller?
PetaSAN 4.1 kernel is based on latest RHEL 10.1 (dec 2025) 6.12 kernel.
It uses newer mpt3sas driver instead of older mpt2sas, but some older devices are not supported.
From Google:
Based on the provided search results and the official lifecycle of RHEL, the mpt2sas driver is likely obsolete or requires third-party support in RHEL 10.
Removal of Older Drivers: RHEL 8 and RHEL 9 deprecated many older SAS-2 controller drivers, with ELRepo often acting as the source for kmod-mptsas or mpt3sas for newer kernels.
Last edited on March 12, 2026, 12:56 pm by admin · #4
Obelisk
3 Posts
May 14, 2026, 8:55 amQuote from Obelisk on May 14, 2026, 8:55 amThank you,
Our final solution was to replace the controller with H710/H710P, which naturally supports MPT3SAS.
The Old H310 are out
Thank you,
Our final solution was to replace the controller with H710/H710P, which naturally supports MPT3SAS.
The Old H310 are out
ghbiz
81 Posts
May 21, 2026, 4:14 pmQuote from ghbiz on May 21, 2026, 4:14 pmWe have cluster in production that is running older Dell H300 as well.
since upgrade to 4.1.0 from 3.x, we have to manually boot an older 5.X Kernel for the nodes to fully boot and not get stuck in initramfs.
What is the Petasan Preferred method to let the system boot from the 5.x kernel and not the 6.x ?
We have cluster in production that is running older Dell H300 as well.
since upgrade to 4.1.0 from 3.x, we have to manually boot an older 5.X Kernel for the nodes to fully boot and not get stuck in initramfs.
What is the Petasan Preferred method to let the system boot from the 5.x kernel and not the 6.x ?
Version 4.1 on Perc X10 controller in IT mode doesn't detect drives
Obelisk
3 Posts
Quote from Obelisk on March 10, 2026, 12:47 pmAll,
Comparing installations of version 4.1.0 to the previous 4.0.0, we have identified that on 4.1 drives connected to the Dell Perc H310 controller in SAS9211-8i IT mode firmware are not visible.
In version 4.0.0, all drives are visible.
Based on the test results, it appears that a newer version is missing a driver or requires additional configuration.
Please advise.
Thank you All.
All,
Comparing installations of version 4.1.0 to the previous 4.0.0, we have identified that on 4.1 drives connected to the Dell Perc H310 controller in SAS9211-8i IT mode firmware are not visible.
In version 4.0.0, all drives are visible.
Based on the test results, it appears that a newer version is missing a driver or requires additional configuration.
Please advise.
Thank you All.
admin
3,073 Posts
Quote from admin on March 10, 2026, 9:50 pmThanks for the feedback.
Can you please post output of
dmesg | grep firmware
Thanks for the feedback.
Can you please post output of
dmesg | grep firmware
Obelisk
3 Posts
Quote from Obelisk on March 12, 2026, 9:15 amThnak you,
dmesg | grep firmware
1.013632] GHES: APEI firmuare first mode is enabled by APEI bit and WHEA _OSCThis is the output from the running version 4.0
Tried to temporarily exit into a shell during the installation to capture the data, but that seems to be locked out.
Thnak you,
dmesg | grep firmware
1.013632] GHES: APEI firmuare first mode is enabled by APEI bit and WHEA _OSC
This is the output from the running version 4.0
Tried to temporarily exit into a shell during the installation to capture the data, but that seems to be locked out.
admin
3,073 Posts
Quote from admin on March 12, 2026, 12:54 pmCan you check on running PtaSAN 4.0
lspci -k
and check if the mpt2sas is in use by the controller?PetaSAN 4.1 kernel is based on latest RHEL 10.1 (dec 2025) 6.12 kernel.
It uses newer mpt3sas driver instead of older mpt2sas, but some older devices are not supported.From Google:
Based on the provided search results and the official lifecycle of RHEL, the mpt2sas driver is likely obsolete or requires third-party support in RHEL 10.
Removal of Older Drivers: RHEL 8 and RHEL 9 deprecated many older SAS-2 controller drivers, with ELRepo often acting as the source for kmod-mptsas or mpt3sas for newer kernels.
Can you check on running PtaSAN 4.0
lspci -k
and check if the mpt2sas is in use by the controller?
PetaSAN 4.1 kernel is based on latest RHEL 10.1 (dec 2025) 6.12 kernel.
It uses newer mpt3sas driver instead of older mpt2sas, but some older devices are not supported.
From Google:
Based on the provided search results and the official lifecycle of RHEL, the mpt2sas driver is likely obsolete or requires third-party support in RHEL 10.
Removal of Older Drivers: RHEL 8 and RHEL 9 deprecated many older SAS-2 controller drivers, with ELRepo often acting as the source for kmod-mptsas or mpt3sas for newer kernels.
Obelisk
3 Posts
Quote from Obelisk on May 14, 2026, 8:55 amThank you, Our final solution was to replace the controller with H710/H710P, which naturally supports MPT3SAS. The Old H310 are out
Thank you, Our final solution was to replace the controller with H710/H710P, which naturally supports MPT3SAS. The Old H310 are out
ghbiz
81 Posts
Quote from ghbiz on May 21, 2026, 4:14 pmWe have cluster in production that is running older Dell H300 as well.
since upgrade to 4.1.0 from 3.x, we have to manually boot an older 5.X Kernel for the nodes to fully boot and not get stuck in initramfs.
What is the Petasan Preferred method to let the system boot from the 5.x kernel and not the 6.x ?
We have cluster in production that is running older Dell H300 as well.
since upgrade to 4.1.0 from 3.x, we have to manually boot an older 5.X Kernel for the nodes to fully boot and not get stuck in initramfs.
What is the Petasan Preferred method to let the system boot from the 5.x kernel and not the 6.x ?