New F22 Kernels Can Not See LVs

asked 2015-11-24 00:12:49 -0600

pnelsonsr gravatar image

updated 2015-11-27 08:37:20 -0600

mether gravatar image

Have a F22 server and I have not been able to boot off the last 2 kernel installs. The last upgrade 4.2.5 I took a chance that it was the kernel packages and just booted off the last good kernel which is:

kernel-4.2.3-200.fc22

So today I tried to upgrade to the latest:

kernel-4.2.6-200.fc22

And I get the same problem as I did the last kernel upgrade I tried which was:

kernel-4.2.5-201.fc22

So here is what I have and the results:

kernel-4.2.3-200.fc22 -> boots fine
kernel-4.2.5-201.fc22 -> does not boot
kernel-4.2.6-200.fc22 -> does not boot

After upgrading the kernel and rebooting and then selecting 4.2.5 or 4.2.6 kernels, the boot screen displays the following:

         Mounting Configuration File System...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Show Plymounth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
----> then after about 5 minutes of nothing
[  186.210570] dracut-initqueue[354]: Warning: Could not boot.
         Mounting Configuration File System...
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Show Plymounth Boot Screen.
[  OK  ] Reached target Paths.
[  OK  ] Reached target Basic System.
[  186.210570] dracut-initqueue[354]: Warning: Could not boot.
[  186.212836] dracut-initqueue[354]: Warning: /dev/fedora_ssv021/root does not exist 
[  186.213073] dracut-initqueue[354]: Warning: /dev/fedora_ssv021/swap does not exist
[  186.213287] dracut-initqueue[354]: Warning: /dev/mapper/fedora_ssv021-root does not exist
         Starting Dracut Emergency Shell...
Warning: /dev/fedora_ssv021/root does not exist
Warning: /dev/fedora_ssv021/swap does not exist
Warning: /dev/mapper/fedora_ssv021-root does not exist

Generating "/run/initramfs/rdsosreport.txt"

Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save /run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report

dracut:/#

Does anyone know what is happening? We have many other systems that the upgrade works just fine on. Just not this system.

edit retag flag offensive close merge delete

Comments

Still no success...

Compared grub.cfg entries sizes of boot img files and everything looks OK.

Does kernel install create or run something that configures the boot img files? I just can not figure out what is failing to allow the boot process to see the lvm volumes.

pnelsonsr gravatar imagepnelsonsr ( 2015-11-27 13:51:48 -0600 )edit

new kernel (kernel-4.2.6-201.fc22) does not boot

Might this be initramfs? If so how would I create a new one?

pnelsonsr gravatar imagepnelsonsr ( 2015-12-06 14:25:07 -0600 )edit