Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
We have a customer reporting that he repeatedly sees some of his file systems (/boot, /home) get mounted at boot, then unmounted automatically shortly after.
Troubleshooting showed that the corresponding devices were seen as "dead" for a short time, causing the systemd logic to unmount the file systems:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
$ egrep -w "(md124|Switching|/home)" sos_commands/logs/journalctl_--no-pager_--catalog_--boot
[...]
Jan 27 22:26:18 ... systemd[1]: dev-md124.device: Changed dead -> plugged
Jan 27 22:26:18 ... systemd[1]: sys-devices-virtual-block-md124.device: Changed dead -> plugged
Jan 27 22:26:19 ... systemd[1]: sys-devices-virtual-block-md124.device: Changed dead -> plugged
Jan 27 22:26:19 ... systemd[1]: dev-md124.device: Changed dead -> plugged
[...]
Jan 27 22:26:19 ... systemctl[1208]: Switching root - root: /sysroot; init: n/a
Jan 27 22:26:19 ... systemd[1]: Switching root.
[...]
Jan 27 22:26:21 ... systemd-tmpfiles[1254]: Entry "/home" does not match any include prefix, skipping.
Jan 27 22:26:22 ... systemd[1]: home.mount: About to execute /usr/bin/mount /dev/disk/by-label/role /home -t xfs
Jan 27 22:26:22 ... systemd[1]: Mounting /home...
Jan 27 22:26:22 ... systemd[1255]: home.mount: Executing: /usr/bin/mount /dev/disk/by-label/role /home -t xfs
Jan 27 22:26:22 ... kernel: XFS (md124): Mounting V5 Filesystem
Jan 27 22:26:22 ... kernel: XFS (md124): Ending clean mount
[...]
Jan 27 22:26:25 ... systemd[1]: Unit blockdev has alias blockdev@.target.
Jan 27 22:26:25 ... systemd[1]: sys-devices-virtual-block-md124.device: Changed dead -> plugged
Jan 27 22:26:25 ... systemd[1]: dev-md124.device: Changed dead -> plugged
Jan 27 22:26:25 ... systemd[1]: sys-devices-virtual-block-md124.device: Changed plugged -> dead
Jan 27 22:26:25 ... systemd[1]: dev-md124.device: Changed plugged -> dead
---> HERE IT'S DEAD, CAUSING THE UNMOUNT TO HAPPEN
Jan 27 22:26:25 ... systemd[1]: sys-devices-virtual-block-md124.device: Collecting.
Jan 27 22:26:25 ... systemd[1]: dev-md124.device: Changed dead -> plugged
Jan 27 22:26:25 ... systemd[1]: sys-devices-virtual-block-md124.device: Changed dead -> plugged
Jan 27 22:26:25 ... systemd[1]: home.mount: About to execute /usr/bin/umount /home -c
Jan 27 22:26:25 ... systemd[1]: Unmounting /home...
Jan 27 22:26:25 ... systemd[1702]: home.mount: Executing: /usr/bin/umount /home -c
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
We can even see in some cases a Partition "going away", which is unlikely to happen at all:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Jan 27 22:26:25 ... systemd[1]: Invoking unit catchup() handlers…
Jan 27 22:26:25 ... systemd[1]: dev-disk-by\x2did-ata\x2dDISK_ID\x2dpart7.device: Changed plugged -> dead
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
We found out that this issue was known Upstream (https://github.com/systemd/systemd/issues/26254) and was fixed by 3 commits:
75d7b59
cf1ac0c
4fc69e8
Version-Release number of selected component (if applicable):
systemd-250-12.el9_1.x86_64
How reproducible:
Regularly on customer systems when deploying nodes from a template, couldn't reproduce internally.
Additional info:
I delivered a test package to the customer with these 3 fixes and customer confirmed it solved the issue.
> We found out that this issue was known Upstream
> (https://github.com/systemd/systemd/issues/26254) and was fixed by 3 commits:
>
> 75d7b59
> cf1ac0c
> 4fc69e8
These commits are part of either systemd 251 or 252, hence this bug should be already fixed by rebase to 252.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (systemd bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2531