similar to: 4.9 kernel fails to boot because it didn't have the mpt3sas module

On Wed, May 17, 2017 at 10:07 AM, Sarah Newman <srn at prgmr.com> wrote: > On 05/16/2017 09:04 PM, Jerry wrote: > <snip> > > > > Turns out dracut was unable to mount the root file system. So I went > back > > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in > > its initramfs file... and it wasn't: > > > > >

On 05/16/2017 09:04 PM, Jerry wrote: <snip> > > Turns out dracut was unable to mount the root file system. So I went back > into the 3.10 kernel again to see if the mpt2sas or mpt3sas driver was in > its initramfs file... and it wasn't: > > > $ sudo lsinitrd -k 4.9.25-27.el7.x86_64 | grep mpt > -rw-r--r-- 1 root root 0 May 16 12:39

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

Guys, I have a Packer build procedure, that works like a charm, when with CentOS 6.7. Exemplifying: 1- Packer (with virtio disk) + QEmu + CentOS 6.7 ISO; 2- Create a RAW image; 3- Convert the RAW image into QCOW2 for KVM hypervisors (okay); 4- Convert the RAW image into VMDK for ESXi hypervisors (okay). However, when doing the very same procedure, with CentOS 7.2 ISO, it does not boot

Hello, I've recently been given domain over a number of supermicro storage servers using Broadcom / LSI SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] (rev 03) to run a bunch of SSDs. I was attempting to do fresh installs of CentOS 8 and have come to find out that RedHat deprecated support for a number of HBAs for 8 including all running the SAS2004 chip. Does anyone know if there is a

Is there any problem moving to 4.9.31? This contains upstream commits f2e767bb5d6ee0d9 for mpt3sas and 69861e0a52f87333 for dom0 memory mappings. I am also trying to build a debuginfo package but it's not correct. Specifically I'm able to get vmlinux but the .debug files for modules are stripped, which isn't right. Does anyone know how to fix this? I'm also not sure how

CentOS Errata and Enhancement Advisory 2016:1930 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1930.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d14458a2bca348a99df8dcdf0b1ecceec16e7c5a85e3cd87fe2aa7b5b1df3a44 kmod-mpt3sas-13.100.00.00-1.el7_2.x86_64.rpm Source:

CentOS Errata and Enhancement Advisory 2017:0458 Upstream details at : https://rhn.redhat.com/errata/RHEA-2017-0458.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 5d5fd5d8ca7d36045da7cf51014ef923cf0e7ff482f99fa745d5b81babd54d86 kmod-redhat-mpt3sas-14.101.00.00-1.el7_3.x86_64.rpm Source:

I have a handful of new systems where I've seen unexpectedly low disk performance on an Avago SAS controller, when using CentOS 7. It looked like a regression, so I installed CentOS 6 on one of them and reloaded CentOS 7 on the other. Immediately after install, a difference is apparent in the RAID rebuild speed. The CentOS 6 system is initializing its software RAID5 array at somewhere

On 05/17/2017 01:30 PM, Jerry wrote: > For some reason each of the 5, 6 & 7 releases have issues with the mpt2sas > driver (there isn't enough swiotlb allocated by default for the driver to > work properly, and the units for that parameter changed between 5 and 6). > It's like this driver has bad luck or something. To my best knowledge they shouldn't use swiotlb if

On 20/09/2020 04:16, Akemi Yagi wrote: > On Sat, Sep 19, 2020 at 8:04 PM William Markuske <wmarkuske at gmail.com> wrote: >> >> Hello, >> >> I've recently been given domain over a number of supermicro storage >> servers using Broadcom / LSI SAS2004 PCI-Express Fusion-MPT SAS-2 >> [Spitfire] (rev 03) to run a bunch of SSDs. I was attempting to do

On 10/2/19 9:47 PM, Jonathan Billings wrote: > On Oct 2, 2019, at 3:39 PM, Ljubomir Ljubojevic <centos at plnet.rs> wrote: >> Richard on CentOS-devel mailing list has similar problem but suggests it >> might be issue only with CentOS, he says he had to add the kernel line >> to make it work. >> Name of the tread is: >> [CentOS-devel] Booting CentOS 8 in a VM

NOTE: this is happening on Centos 6 x86_64, 2.6.32-504.3.3.el6.x86_64 not Centos 5 Dell PowerEdge 2970, Seagate SATA drive, non-raid. I have this server which has been dying randomly, with no logs. I had a tail -f over ssh for a week, when this just happened. Feb 8 00:10:21 thirteen-230 kernel: mptscsih: ioc0: attempting task abort! (sc=ffff880057a0a080) Feb 8 00:10:21 thirteen-230 kernel:

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are

Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]

On 11/05/2016 06:40 AM, Steven Tardy wrote: > What firmware is/are on the cards? In the dmesg output I included: mpt3sas0: LSISAS3008: FWVersion(10.00.00.00), ChipRevision(0x02), BiosVersion(08.25.00.00) > The driver version difference between C6 and C7 could interact badly with old firmware. I suspected that was the case, and tried running elrepo's "kmod-mpt3sas" from

Hi Everyone, I have a server that I recently applied all updates to to bring it to 1804. After rebooting the server, it would no longer boot and is instead dropping into a dracut shell. Here's a snippet of the output printed to the console (lines will likely wrap): [ 184.163787] dracut-initqueue[256]: Warning: dracut-initqueue timeout - starting timeout scripts [ 184.672525]

I migrated a CentOS7 VM (the fedrtc.org site) from an XCP environment to a libvirt/KVM environment. This involved using qemu-img to convert the image from VHD to qcow2 and then using virt-install --import to define the VM in libvirt. Three problems occurred during boot: a) on the first boot, the BIOS screen and grub screen don't appear at all, the screen is blank for a couple of seconds and

Hi, When I build a mpt3sas rpm package, I found something interesting: 1. package name is prefixed with kmod- automatically 2. so many requirements are added automatically, most of them are kabi So my question is rpmbuild how to know he is building kernel module package? Based on which condition? Here is mpt3sas.spec: Name: mpt3sas Version: 26.00.00.00 Release: 1 Summary: RHEL

On Thu, Oct 10, 2019 at 9:04 AM Nux! <nux at li.nux.ro> wrote: > There was a recent thread about Redhat's removal of drivers from LSI > SAS2, it's probably the problem you are facing. > It can be worked around with the help of Elrepo repo. > > > https://lists.centos.org/pipermail/centos/2019-October/173682.html > > >