Bug 2021353
| Summary: | RHEL 9 beta installer creates unbootable system without separate /home partition. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | kkeane | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 9.0 | CC: | jstodola, vtrefny | ||||
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| 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 09:47:21 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: |
|
||||||
|
Description
kkeane
2021-11-08 23:43:27 UTC
Update: upon reviewing the documentation for autopart, it appears that this problem will only occur on relatively small drives. The documentation for autopart (for RHEL 7) says: "On large enough drives (50 GB and larger), this also creates a /home partition." Workaround: Using "autopart --nohome" instead of just autopart will generate a correct fstab. Upon further investigation, the actual problem is that autopart "forgets" to create the /home partition when it should create it. Scenario: 80 GB disk. Kickstart contains "autopart" without any options. Actual result: Disk will be partitioned as follows (sorry, I was not able to copy the output from lsblk, so values are approximate): /dev/sda1 - /boot /dev/sda2 - LVM, approximately 78 GB. /dev/mapper/rhel9beta_root - approximately 48 GB. /dev/mapper/rhel9beta_swap - a few GB Remaining part of /dev/sda2 remains unused. Expected result: Disk should be partitioned as follows: /dev/sda1 - /boot /dev/sda2 - LVM, approximately 78 GB. /dev/mapper/rhel9beta_root - approximately 48 GB. /dev/mapper/rhel9beta_home - approximately 28 GB. /dev/mapper/rhel9beta_swap - a few GB Thank you for the bug report. Can you please attach the installation logs? You can find them in /var/log/anaconda on the installed system (or in /tmp during the installation). Created attachment 1842207 [details]
Requested log files, plus a few more that may be useful
I cannot see anything suspicious in the logs, the LV with /home was created and formatted during the installation: INFO:program:Running... mkfs.xfs -f /dev/mapper/rhel_vagrant--rhel9beta-home INFO:program:stdout: INFO:program:meta-data=/dev/mapper/rhel_vagrant--rhel9beta-home isize=512 agcount=4, agsize=1573120 blks INFO:program: = sectsz=512 attr=2, projid32bit=1 INFO:program: = crc=1 finobt=1, sparse=1, rmapbt=0 INFO:program: = reflink=1 bigtime=1 inobtcount=1 INFO:program:data = bsize=4096 blocks=6292480, imaxpct=25 INFO:program: = sunit=0 swidth=0 blks INFO:program:naming =version 2 bsize=4096 ascii-ci=0, ftype=1 INFO:program:log =internal log bsize=4096 blocks=3072, version=2 INFO:program: = sectsz=512 sunit=0 blks, lazy-count=1 INFO:program:realtime =none extsz=4096 blocks=0, rtextents=0 DEBUG:program:Return code: 0 I was not able to reproduce the problem locally. Vojto, do you have any idea what could be the problem? I notice a few entries in lvm.log that say "Skipping unusable device". I'm not enough of an LVM expert to understand if this may be transient and harmless, or related. There are entries both regarding the home and the swap partitions (but not for the root partition), so this may not be relevant. The swap partition does show up in lsblk, the home partition doesn't. A similar bug 2037905 was reported. It might be the same problem as descrideb here. Could you please provide the content of /etc/lvm/devices/system.devices ? Does the system boots successfully with /home mounted if you remove the file? Unfortunately, I can't. This was a transient experimental system that has long since been scrubbed. OK. My assumption here is that this is the same problem with generating /etc/lvm/devices/system.devices during the installation as we see in bug 2037905 and also in bug 2024100. The problem should be fixed in lvm2-2.03.14-3.el9. I'm closing this bug, but feel free to re-open if you can still reproduce it with lvm2-2.03.14-3.el9 or later. |