Cannot boot after upgrade to F31

erich · December 11, 2019, 6:57pm

After upgrading from Fedora 30, I’m unable to boot my system.

The boot process gets stuck in Reached target Basic System and never (I let the machine about a day) goes further.

I tried to boot with the following boot params but without luck.

debug rd.debug rd.udev.debug systemd.log_level=debug systemd.debug-shell=1

However, If I boot with F30 kernel I can get a working system.

How can I get more useful information from my system?

Thanks!

alciregi · December 11, 2019, 11:14pm

On the running system, open a terminal and issue these commands:
lsusb
lspci
sudo dmidecode |grep -A 9 "System Information"

Which kernel version works? Which one doesn’t work?
Do you have an NVIDIA graphic card?

erich · December 12, 2019, 12:10am

Hi, thanks for the response. I don’t have a NVIDIA card.

These are the output of the commands :

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 04d9:0141 Holtek Semiconductor, Inc. USB Keyboard
Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics P630 (rev 04)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:16.1 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #2 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #10 (rev f1)
00:1d.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #11 (rev f1)
00:1d.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #12 (rev f1)
00:1f.0 ISA bridge: Intel Corporation C236 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)
01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

$ sudo dmidecode | grep -A 9 "System Information"
System Information
	Manufacturer: Intel Corporation
	Product Name: S1200SP
	Version: ....................
	Serial Number: ............
	UUID: 269b04e2-acdb-e711-ab21-a4bf012b341b
	Wake-up Type: Power Switch
	SKU Number: SKU Number
	Family: Family

This is the working kernel

$ uname -r
5.3.13-200.fc30.x86_64

And I can’t get to boot with any of the F31 kernel below

$ sudo grubby --info=ALL
index=0
kernel="/boot/vmlinuz-5.3.14-300.fc31.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.3.14-300.fc31.x86_64.img"
title="Fedora (5.3.14-300.fc31.x86_64) 31 (Thirty One)"
id="9014939f479b4911b420f8b8bf95e3f1-5.3.14-300.fc31.x86_64"
index=1
kernel="/boot/vmlinuz-5.3.13-300.fc31.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.3.13-300.fc31.x86_64.img"
title="Fedora (5.3.13-300.fc31.x86_64) 31 (Thirty One)"
id="9014939f479b4911b420f8b8bf95e3f1-5.3.13-300.fc31.x86_64"
index=2
kernel="/boot/vmlinuz-5.3.13-200.fc30.x86_64"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.3.13-200.fc30.x86_64.img"
title="Fedora (5.3.13-200.fc30.x86_64) 30 (Thirty)"
id="9014939f479b4911b420f8b8bf95e3f1-5.3.13-200.fc30.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-9014939f479b4911b420f8b8bf95e3f1"
args="ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.lvm.lv=fedora_localhost-live/swap rhgb quiet"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-0-rescue-9014939f479b4911b420f8b8bf95e3f1.img"
title="Fedora (0-rescue-9014939f479b4911b420f8b8bf95e3f1) 30 (Workstation Edition)"
id="9014939f479b4911b420f8b8bf95e3f1-0-rescue"

erich · December 12, 2019, 12:31am

I removed the resume cmdline argument and the result is the same.

xtym · December 12, 2019, 12:27pm

Did you try boot without both of this parameters or just only resume

resume=/dev/mapper/fedora_localhost--live-swap
rd.lvm.lv=fedora_localhost-live/swap

Maybe (I am not sure) disabling the swap LVM can you jump to the emergency console (and so have accesto a bit more information trough journalctl, in place of force emergency console) or if the system try load.

Can be possible that the swap partition had gone to an inactive state when trying run the kernel fc31?

I did look for a bit of information because i never face a similar problem, so I am just triging give one possible idea)

Some commands in that case would be:

sudo lvm lvscan

To check the active partitions

but in the first link there are also other interesting commands to check if the names given in config by device mapper is matching with the entry in fstab file.

Like you can see it is not a solution for your case it is only an idea to see if it does change something.

Regards

erich · December 13, 2019, 7:18pm

Thanks @xtym !

The second link helped me to allow the booting. However, I’m still unsure how to make it permanent. This is what I did.

Add the rd.break=initqueue parameter to the kernel to get a shell
Run lvm lvscan and I noticed that all my lvm were inactive
I activate them with lvm lvchange -y a fedora_localhost-live/root, the same for swap and home.
Exit from this shell and the boot continued.

However, in the next boot the volumes were inactive again. I don’t see a lvm2-activation service running, also I’m not sure what is the process in F31.

Thanks a lot! this was a good progress

xtym · December 13, 2019, 8:03pm

Hi @erich

Try repeat the process again, after than you did initiate in your last kernel check again than all your volumen and swap is on like you did activate. After try regenerate your initramfs image so that you save the changes in the next reboot, to do it you need use dracut, you can read about dracut with man dracut or here

Do first a backup of your old initramfs image

sudo mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-old.img

Now create a new initramfs for the current kernel version

sudo dracut /boot/initramfs-$(uname -r).img $(uname -r)

And

reboot

Interesting links about dracut:

https://fedoraproject.org/wiki/Dracut#Getting_started

I think it should do the changes permanent.

Regards.

erich · December 17, 2019, 12:17am

Hi @xtym

I tried dracut to generate the initramfs, but that didn’t made any effect in the activation of lvm. Not sure if this is something that should be enabled through a systemd service or something else.

xtym · December 17, 2019, 5:09am

Hi @erich

Ok try save the active situation through the utility Disk what is included with gnome by default. And for every partition pick in the gear to edit montage options and you need see than the option mount at system startup is active.

Look this pictures (sorry for Swedish language)

And after you can check your fstab file. the one mine looks like it (the sda disk is a disk that i did select to mount in the start but that is not related with the system to avoid confusion)

[jorge@f31 ~]$ sudo cat /etc/fstab
[sudo] lösenord för jorge: 

#
# /etc/fstab
# Created by anaconda on Tue Nov 26 15:22:09 2019
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/fedora_localhost--live-root /                       ext4    defaults        1 1
UUID=eb889234-bb74-4cdc-a4f2-5e9e077b1e18 /boot                   ext4    defaults        1 2
UUID=3632-7517          /boot/efi               vfat    umask=0077,shortname=winnt 0 2
/dev/mapper/fedora_localhost--live-home /home                   ext4    defaults        1 2
/dev/mapper/fedora_localhost--live-swap none                    swap    defaults        0 0
/dev/disk/by-uuid/2f2f56a3-c161-4004-91b6-fb9f6c40022f /mnt/2f2f56a3-c161-4004-91b6-fb9f6c40022f auto nosuid,nodev,nofail,x-gvfs-show 0 0
[jorge@f31 ~]$ lsblk
NAME                            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                               8:0    0 223,6G  0 disk 
└─sda1                            8:1    0 223,6G  0 part /mnt/2f2f56a3-c161-4004-91b6-fb9f6c40022f
sdb                               8:16   0 232,9G  0 disk 
├─sdb1                            8:17   0   600M  0 part /boot/efi
├─sdb2                            8:18   0     1G  0 part /boot
└─sdb3                            8:19   0 231,3G  0 part 
  ├─fedora_localhost--live-root 253:0    0    70G  0 lvm  /
  ├─fedora_localhost--live-swap 253:1    0   7,9G  0 lvm  [SWAP]
  └─fedora_localhost--live-home 253:2    0 153,4G  0 lvm  /home
sr0

more About how fstab work can be find with the command man fstab or here

Edit: If you did check and all is ok… look this link where another guy had a same issue with CentOS but the way should be similar.

Notes at the link above:

But to regenerate initramfs fedora use Dracut how you did before not (mkinitrd)
And to regenerate grub follow this link note that there are 2 different ways to BIOS or UEFI:

https://fedoraproject.org/wiki/GRUB_2

I hope it can help you… like said before : I never did test it by myself because never did run into the issue so always backup thing in case of doubt

Regards.

Topic		Replies	Views
Fedora failing to boot: dracut-initqueue timeout Ask Fedora f31	8	14421	February 2, 2020
Upgrade from 30 to 31 results in lvm inactive on boot Ask Fedora	5	2332	January 17, 2020
Problem to mount lvm partition at boot Ask Fedora	2	790	July 23, 2020
Lvm2 not starting at boot Ask Fedora	0	466	May 21, 2020
LVM direct activation of logical volumes Ask Fedora	1	514	July 12, 2020

Cannot boot after upgrade to F31

Related topics