View Issue Details

IDProjectCategoryView StatusLast Update
0018360CentOS-8lvm2public2022-02-03 22:12
Reporterenrico.tagliavini Assigned To 
Status resolvedResolutionfixed 
Summary0018360: CentOS 8 Stream doesn't boot any longer after update, LVM volumes are not activated at boot (only root and swap volumes are)
DescriptionDisclaimer: I'm not entirely sure what package is responsible for this issue. It could be lvm2 or one of the device-mapper. I think the most likely is lvm2, so this is what I selected, but if it's from another package, please move as appropriate.

After updating one of my CentOS 8 Stream systems on Monday I found out the boot process was failing, hanging waiting for devices for /var/ /tmp/ /opt and others to appear, giving up after a few minutes.

This system is updated every Monday morning, so the change must have happened in the week before, so between the 15th and the 21st of November. I also have the list of the updated packages in the last update run (see below).

I found the following workaround to make the system boot again: remove all references to any* from the kernel command line in grub. This made the system boot again.
Steps To ReproduceInstall CentOS 8 stream with some additional system folder on separate LV volumes (e.g. /var, /opt, /tmp). Apply the update and restart the system, boot should fail.
Additional InformationIt would look like that after the update the system will only activate the volumes listed on the kernel command line, ignoring fstab or lvm config files. I left the LVM config file and the kernel command line as set by the installation, I never changed them. The installation adds the root and swap LVs to the kernel command line, but not all others, even if created during the installation.

If LVM devices are listed in fstab I think those should also be activated by default, regardless or not they were specified in the kernel command line. This was also the previous behavior and this update broke all installation with additional LVM volumes.

This is the full list of packages update in the last update before the issue as reported by DNF automatic:

 kernel x86_64 4.18.0-348.2.1.el8_5 baseos 7.0 M
 kernel-core x86_64 4.18.0-348.2.1.el8_5 baseos 38 M
 kernel-devel x86_64 4.18.0-348.2.1.el8_5 baseos 20 M
 kernel-modules x86_64 4.18.0-348.2.1.el8_5 baseos 30 M
 bpftool x86_64 4.18.0-348.2.1.el8_5 baseos 7.7 M
 clamav x86_64 0.103.4-1.el8 epel 2.7 M
 clamav-filesystem noarch 0.103.4-1.el8 epel 46 k
 clamav-lib x86_64 0.103.4-1.el8 epel 862 k
 clamav-update x86_64 0.103.4-1.el8 epel 129 k
 clamd x86_64 0.103.4-1.el8 epel 124 k
 device-mapper x86_64 8:1.02.181-1.el8 baseos 377 k
 device-mapper-event x86_64 8:1.02.181-1.el8 baseos 271 k
 device-mapper-event-libs x86_64 8:1.02.181-1.el8 baseos 270 k
 device-mapper-libs x86_64 8:1.02.181-1.el8 baseos 409 k
 device-mapper-multipath x86_64 0.8.4-19.el8 baseos 198 k
 device-mapper-multipath-libs x86_64 0.8.4-19.el8 baseos 323 k
 fedpkg noarch 1.41-2.el8 epel 113 k
                                 x86_64 1: appstream 36 M
 java-1.8.0-openjdk-slowdebug x86_64 1: appstream 345 k
 kernel-headers x86_64 4.18.0-348.2.1.el8_5 baseos 8.3 M
 kernel-tools x86_64 4.18.0-348.2.1.el8_5 baseos 7.2 M
 kernel-tools-libs x86_64 4.18.0-348.2.1.el8_5 baseos 7.0 M
 kpartx x86_64 0.8.4-19.el8 baseos 113 k
 libstoragemgmt x86_64 1.9.1-3.el8 baseos 246 k
 lvm2 x86_64 8:2.03.14-1.el8 baseos 1.7 M
 lvm2-libs x86_64 8:2.03.14-1.el8 baseos 1.2 M
 python3-libstoragemgmt x86_64 1.9.1-3.el8 baseos 176 k
 python3-perf x86_64 4.18.0-348.2.1.el8_5 baseos 7.1 M
 rsyslog x86_64 8.2102.0-6.el8 appstream 752 k
 rsyslog-gnutls x86_64 8.2102.0-6.el8 appstream 32 k
 rsyslog-gssapi x86_64 8.2102.0-6.el8 appstream 34 k
 rsyslog-relp x86_64 8.2102.0-6.el8 appstream 33 k
 kernel x86_64 4.18.0-331.el8 @baseos 0
 kernel-core x86_64 4.18.0-331.el8 @baseos 68 M
 kernel-devel x86_64 4.18.0-331.el8 @baseos 49 M
 kernel-modules x86_64 4.18.0-331.el8 @baseos 22 M

Transaction Summary
Install 4 Packages
Upgrade 28 Packages
Remove 4 Packages

TagsNo tags attached.




2021-11-25 16:57

manager   ~0038752

Stream-related bugs need to be reported to Red Hat. For details, please see:


2021-11-26 09:05

reporter   ~0038753

Understood, I opened a bug on the red hat bugzilla. Thank you.


2022-01-08 19:05

manager   ~0038788

Looks like the problem has been resolved upstream, thanks to your report.

Issue History

Date Modified Username Field Change
2021-11-25 09:59 enrico.tagliavini New Issue
2021-11-25 16:57 toracat Note Added: 0038752
2021-11-26 09:05 enrico.tagliavini Note Added: 0038753
2022-01-08 19:05 toracat Note Added: 0038788
2022-02-03 22:12 toracat Status new => resolved
2022-02-03 22:12 toracat Resolution open => fixed