Created attachment 1081760 [details]
rdsosreport.txt after failed boot
Description of problem:
After updating the system with `dnf -y update` cannot boot with the new kernel. Must choose old kernel 4.1.7 to successfully boot the system.
Version-Release number of selected component (if applicable):
kernel version 4.1.10
Steps to Reproduce:
1. Turn on computer
2. Choose kernel version 4.1.10 in grub menu
I'm thrown into the dracut shell.
See attached rdsosreport.txt file rescued from the dracut shell after failure.
For some reason your command line is telling dracut to use root=/dev/mapper/fedora_dhcppc7-root , however that device doesn't exist. LVM finds /dev/myvg/root though:
[ 125.682383] grower dracut-initqueue: Scanning devices sda2 for LVM logical volumes myvg/swap myvg/root
[ 125.693719] grower dracut-initqueue: ACTIVE '/dev/myvg/swap' [10.76 GiB] inherit
[ 125.694017] grower dracut-initqueue: inactive '/dev/myvg/home' [200.00 GiB] inherit
[ 125.694290] grower dracut-initqueue: ACTIVE '/dev/myvg/root' [50.00 GiB] inherit
[ 125.694475] grower dracut-initqueue: inactive '/dev/myvg/space' [1.56 TiB] inherit
[ 125.698550] grower dracut-initqueue: PARTIAL MODE. Incomplete logical volumes will be processed.
[ 125.709128] grower dracut-initqueue: PARTIAL MODE. Incomplete logical volumes will be processed.
[ 186.166662] grower dracut-initqueue: Warning: Could not boot.
[ 186.185091] grower systemd: Received SIGRTMIN+20 from PID 282 (plymouthd).
[ 186.190531] grower dracut-initqueue: Warning: /dev/mapper/fedora_dhcppc7-root does not exist
What does your kernel command line for 4.1.7 look like? When you boot into that, can you show the output of the 'mount' command, and 'lvm pvdisplay, lvm vgdisplay, lvm lvdisplay'?
I found the problem. I had (as you can see) renamed the lvm volumes from fedora_dhcppc7-* to myvg-* and had updated the grub boot line accordingly. But when I installed a new kernel (trhough dnf update) a new grub boot line was automatically installed (by what unit?) and that line still referenced the original convention. After manually fixing the grub boot line for the new kernel, everything worked as it should. So what remains for me is to figure to do this fix permenantly.