sda is the internel hard drive, has the OS on it./0/100/1f.2/2.0.0 /dev/sda disk 118GB MegaSR
/0/100/1f.2/2.0.0/1 /dev/sda1 volume 1GiB Linux filesystem partition
/0/100/1f.2/2.0.0/2 /dev/sda2 volume 56GiB Linux LVM Physical Volume partition
Dracut Shell after kernel upgrade
-
- Posts: 15
- Joined: 2018/09/12 16:01:30
Re: Dracut Shell after kernel upgrade
Re: Dracut Shell after kernel upgrade
What do you have in /etc/modprobe.d ? Is there anything there that blacklists megaraid_sas for example?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 15
- Joined: 2018/09/12 16:01:30
Re: Dracut Shell after kernel upgrade
when i ran a ls on that directory i got the below results, non seem to mention anything about raid.
i noticed something else while digging, when i booted to the Centos iso disk, it cannot see the internal drives. the 2 118GB drives that the OS sits on. Most likely why i cannot get the new kernel to see the drives either, but not sure how to explain why the old kernel can see them.anaconda-blacklist.conf dccp-blacklist.conf firewalld-sysctls.conf tuned.conf V-38515-disable-sctp.conf V-38517-disable-tipc.conf
CIS.conf disable-bluetooth.conf lockd.conf
-
- Posts: 15
- Joined: 2018/09/12 16:01:30
Re: Dracut Shell after kernel upgrade
bump, anyone have anything else to try? still stuck with this issue and have a large amount of physical servers it would suck to re-image!
thanks.
thanks.
Re: Dracut Shell after kernel upgrade
Hello,
can't offer help yet, besides contributing a possible correlation?
Face exact same issues after having updated Centos 7 yesterday from
dmesg & journalctl, neither boot.log do keep any record from this failing attempt, or do i have to look somewhere else?
I know my system is special in this regard:
As OP i'm more interested in determining reason and remedies rather then just workarounding (clean reinstallation) this issue, as the installation will be a component of a production system.
Thus: could this and similar issues be linked to "odd" controllers?
Best
J
can't offer help yet, besides contributing a possible correlation?
Face exact same issues after having updated Centos 7 yesterday from
Can boot perfectly fine still from previous kernel, but new kernel causes dracut to fail, ending with3.10.0-862.14.4.el7.x86_64 => 3.10.0-957.1.3.el7.x86_64
A /run/initramfs/rdsosreport.txt is claimed to be written, but having booted into the previous kernel, i can't find it.dracut - initqueue 414 warning: not all disks could be found
dmesg & journalctl, neither boot.log do keep any record from this failing attempt, or do i have to look somewhere else?
I know my system is special in this regard:
but i managed to tinker the initial installation accordingly and had no issues ever since again, since:ProLiant DL180 G5
scsi0 storage Smart Array P400 Controller
I repeated all measures discussed here so far which seem to pertain to my situation (including reinstalling kernel from previous known good kernel), but still to no avail."CentOS Linux (3.10.0-693.el7.x86_64)
As OP i'm more interested in determining reason and remedies rather then just workarounding (clean reinstallation) this issue, as the installation will be a component of a production system.
Thus: could this and similar issues be linked to "odd" controllers?
Best
J
Re: Dracut Shell after kernel upgrade
/run is a tmpfs filesystem and thus transient. If you want its contents then you have to copy it before you reboot.A /run/initramfs/rdsosreport.txt is claimed to be written, but having booted into the previous kernel, i can't find it.
You're using an unsupported RAID controller. There are two methods to make that work - one is by adding an hpsa_allow_any parameter to the hpsa kernel module via a file in /etc/modprobe.d or by adding it to the kernel command line at boot time or the other alternative is by installing kmod-cciss from ELRepo in which case you almost certainly need an updated copy of that kmod from ELRepo to work with the new 7.6 kernel.
I don't think your problem is going to be the same or even similar to the OP's.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: Dracut Shell after kernel upgrade
Hello Trevor,
thank you for you help.
That's the weird thing: as i had to cope with the HP controller for the initial installation and solved it by one of your recommended methods, this config is still around, both kernel options have the exact same config:
Thus: is "hpsa.hpsa_allow_any=1" alone possibly not sufficient any longer, or may be there a problem somewhere else?
As for grabbing the /run/initramfs/rdsosreport.txt: i havn't been able to mount any drive from that state, as the system in that state then is extremely slow. I always had to hard reset the machine in order to make it operable again...
Do you think installing "kmod-cciss" would restore, what "hpsa.hpsa_allow_any=1" accomplished so far?
Or should i exclude the controller issue from further investigation?
Best
thank you for you help.
That's the weird thing: as i had to cope with the HP controller for the initial installation and solved it by one of your recommended methods, this config is still around, both kernel options have the exact same config:
And: this worked flawlessly for all the recent kernelupdates so far...menuentry 'CentOS Linux (3.10.0-957.1.3.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-693.el7.x86_64-advanced-7e1cb0b7-46e3-4dbd-ab64-ca5140387fac' {
[ ... ] linux16 /vmlinuz-3.10.0-957.1.3.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1 LANG=en_US.UTF-8
}
menuentry 'CentOS Linux (3.10.0-862.14.4.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.10.0-693.el7.x86_64-advanced-7e1cb0b7-46e3-4dbd-ab64-ca5140387fac' {
[ ... ]
linux16 /vmlinuz-3.10.0-862.14.4.el7.x86_64 root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet hpsa.hpsa_simple_mode=1 hpsa.hpsa_allow_any=1 LANG=en_US.UTF-8
}
Thus: is "hpsa.hpsa_allow_any=1" alone possibly not sufficient any longer, or may be there a problem somewhere else?
As for grabbing the /run/initramfs/rdsosreport.txt: i havn't been able to mount any drive from that state, as the system in that state then is extremely slow. I always had to hard reset the machine in order to make it operable again...
Do you think installing "kmod-cciss" would restore, what "hpsa.hpsa_allow_any=1" accomplished so far?
Or should i exclude the controller issue from further investigation?
Best
Re: Dracut Shell after kernel upgrade
The hpsa_allow_any parameter is really only a temporary workaround to get installed. The correct driver for a P400 is cciss and the only place you can get that for el7 is ELRepo.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
-
- Posts: 15
- Joined: 2018/09/12 16:01:30
Re: Dracut Shell after kernel upgrade
I am running into a new issue with some servers that previously worked. also coming from 3.10.0-862.14.4.el7.x86_64 -> 3.10.0-957.
this time it doesnt even make it to dracut or try and load the OS.
im getting the below errors, it never seems to complete anything either, it does not respond to any keys. if i reboot and select the prevoius 862 kernel it boots up normal.
this time it doesnt even make it to dracut or try and load the OS.
im getting the below errors, it never seems to complete anything either, it does not respond to any keys. if i reboot and select the prevoius 862 kernel it boots up normal.
Code: Select all
[ 0.00000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb000020 ( or later)
[ 2.520197] i8042: no controller found
[ 3.114328] megaraid_sas 0000:08:00.0: init cmd return status SUCCESS for SCS host 0
[ 5.312281] power_meter ACP1000D:00: Ignoring unsafe software power cap!
[5.413664] power_meter ACP1000D:00: Ignoring unsafe software power cap!
Re: Dracut Shell after kernel upgrade
Hello Trevor,
Best,
J
Thank you for pointing this out, i wasn't aware of that and will catch up with installing the driver!The hpsa_allow_any parameter is really only a temporary workaround
Best,
J