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.
Consequence:
Mount points in fstab which should be checked and also should be mounted in initramfs were not mounted at all.
Fix:
Fixed by rebase.
Result:
This should work now.
Created attachment 1058667[details]
journalctl -a with debug on the kernel cmdline
Description of problem:
If a mount defined in /etc/fstab has the x-initrd.mount option defined and passno=2, the filesystem does not get mounted after boot.
Version-Release number of selected component (if applicable):
systemd-208-20.el7_1.5
How reproducible:
always
Steps to Reproduce:
1. define a mount in /etc/fstab like this:
UUID=d73c79a6-6303-4aa3-842a-4b8756041935 /boot xfs x-initrd.mount 1 2
2. reboot
Actual results:
/boot is not mounted.
Expected results:
/boot is mounted.
Additional info:
systemd logs the following message after switching root:
systemd[1]: Unmounting /boot...
journalctl -a with debug on the kernel cmdline attached.
(In reply to Marcel Kolaja from comment #2)
> The issue does not occur with systemd-219-9.el7.centos.x86_64 from
> https://copr.fedoraproject.org/coprs/lnykryn/systemd/, which means that it
> has been fixed upstream already.
Also it means that it will be fixed in 7.2.
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, 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://rhn.redhat.com/errata/RHBA-2015-2092.html
Created attachment 1058667 [details] journalctl -a with debug on the kernel cmdline Description of problem: If a mount defined in /etc/fstab has the x-initrd.mount option defined and passno=2, the filesystem does not get mounted after boot. Version-Release number of selected component (if applicable): systemd-208-20.el7_1.5 How reproducible: always Steps to Reproduce: 1. define a mount in /etc/fstab like this: UUID=d73c79a6-6303-4aa3-842a-4b8756041935 /boot xfs x-initrd.mount 1 2 2. reboot Actual results: /boot is not mounted. Expected results: /boot is mounted. Additional info: systemd logs the following message after switching root: systemd[1]: Unmounting /boot... journalctl -a with debug on the kernel cmdline attached.