Bug 2037905
| Summary: | RHEL 9 beta installer creates unbootable system when custom partitioning is used. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Jeff Putsch <jdputsch> | ||||
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> | ||||
| lvm2 sub component: | Activating existing Logical Volumes | QA Contact: | cluster-qe <cluster-qe> | ||||
| Status: | CLOSED DUPLICATE | Docs Contact: | |||||
| Severity: | unspecified | ||||||
| Priority: | unspecified | CC: | agk, heinzm, jbrassow, jstodola, msnitzer, prajnoha, teigland, zkabelac | ||||
| Version: | 9.0 | Flags: | pm-rhel:
mirror+
|
||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | aarch64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-01-10 15:18:43 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
(In reply to Jeff Putsch from comment #0) > NOTEs: > > 1. There is no /var/log/anaconda directory after the reboot. > 2. "rpm -qa" after reboot lists no packages. I assume these problems are caused by /var not being mounted during boot. From journalctl: ... Jan 06 11:32:24 localhost systemd[1]: dev-mapper-rhel_rhel\x2d\x2d9beta\x2d\x2daarch64\x2dhome.device: Job dev-mapper-rhel_rhel\x2d\x2d9beta\x2d\x2daarch64\x2dhome.device/start timed out. Jan 06 11:32:24 localhost systemd[1]: Timed out waiting for device /dev/mapper/rhel_rhel--9beta--aarch64-home. ░░ Subject: A start job for unit dev-mapper-rhel_rhel\x2d\x2d9beta\x2d\x2daarch64\x2dhome.device has failed ░░ Defined-By: systemd ░░ Support: https://access.redhat.com/support ░░ ░░ A start job for unit dev-mapper-rhel_rhel\x2d\x2d9beta\x2d\x2daarch64\x2dhome.device has finished with a failure. ░░ ░░ The job identifier is 173 and the job result is timeout. Jan 06 11:32:24 localhost systemd[1]: Dependency failed for /home. ... This looks like the LV block devices were not created. I'm reassigning this bug to lvm2 for further review. I tried to reproduce this problem on RHEL-9.0-Beta, but I was not successful, the system booted fine. Also, this bug reminds me bug 2021353, where LV with /home was not created during boot. Jan 06 11:30:55 localhost lvm[685]: /dev/sda3 excluded by filters: device is not in devices file. The device needed for the LVs is not included in the lvm devices file, so lvm ignores it. I don't know how this version of anaconda is setting up the devices file, the most recent design is to add all visible PVs to the devices file. Jeff, is the file /etc/lvm/devices/system.devices present on the installed system? What is the content of the file? Would the system boot correctly if you (re)move the file? Answer questions: 1. The file /etc/lvm/devices/system.devices IS present. 2. The content of the file: # LVM uses devices listed in this file. # Created by LVM command vgimportdevices pid 45507 at Thu Jan 6 11:24:43 2022 VERSION=1.1.1 IDTYPE=sys_wwid IDNAME=t10.ATA rhel-9beta-aarch64-0 SSD QZ8CSQE08TN4FFMGFBY2 DEVNAME=/dev/sda3 PVID=sgPsILPY8ppc5s4z6YGABslwh8vm62cm PART=3 3. Does the system boot correctly if I remove the file? YES! All partitions specified during setup are there, properly sized and appear to have correct contents. Jeff. David, IDNAME in comment 4 doesn't look correct and it might be the same problem as reported in bug 2024100. Reassigning back to lvm2. (In reply to Jan Stodola from comment #5) > IDNAME in comment 4 doesn't look correct and it might be the same problem as Thanks for finding that... IDNAME=t10.ATA rhel-9beta-aarch64-0 SSD QZ8CSQE08TN4FFMGFBY2 That's a dubious WWID, any idea where that's created (i.e. was it set by a user or some automation?) > reported in bug 2024100. Reassigning back to lvm2. Yes, it's the same problem and same fix as bug 2024100, so I'll close this as a duplicate. *** This bug has been marked as a duplicate of bug 2024100 *** |
Created attachment 1849337 [details] Tarball with debug files described in Initial description. Description of problem: On RHEL 9 beta, anaconda generates an invalid unbootable system configuration when used with the graphical installer and custom disk partitioning. In this case, the installer inserts lines referencing a the partitions into fstab but the system fails to initialize the /dev/mapper/* entries for those partitions on bootup. In addition no /var/log/anaconda directory exists on the booted system. How reproducible: Every time. Steps to Reproduce: 1. Boot system using the rhel-baseos-9.0-beta-0-aarch64-dvd.iso image 2. Select Custom Partitioning 3. Select "Click here to create them" to create initial partions. 4. Adjust /home to 1 GiB 5. Adjust / to 10 GiB 6. Leave /boot, /boot/efi, and swap alone 7. Add /var (3 GiB), /var/tmp/ (1 GiB), /var/log/audit (512 MiB), /var/log (1 GiB), and /tmp (1 Gib) partitions. 8. Proceed with installation. Actual results: System drops into emergency shell. Expected results: System boots normally. Additional info: I've attached a tarball with containing the following files: 1. rhel-9-beta-install-logs.tar.gz - tarball of the log files in /tmp immediately before reboot. 2. anaconda-ks.cfg - "/root/anaconda-ks.cfg" file after reboot. 3. journalctl-xb.log - output of "journalctl -xb" from the emergency shell. NOTEs: 1. There is no /var/log/anaconda directory after the reboot. 2. "rpm -qa" after reboot lists no packages.