-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-10.0.beta
-
None
-
libblockdev-3.1.0-4.el10
-
None
-
None
-
sst_storage_management
-
ssg_filesystems_storage_and_HA
-
15
-
17
-
2
-
False
-
-
None
-
None
-
None
What were you trying to do that didn't work?
Run a kickstart installation with the following partitioning:
bootloader --location=mbr zerombr clearpart --all --initlabel reqpart --add-boot part / --size 1024 --grow part swap --recommended part /ext2 --size=1024 --fstype ext2 part /ext3 --size=1024 --fstype ext3 part /ext4 --size=1024 --fstype ext4
The installed system doesn't have the /ext2 and /ext3 mount points created and mounted:
[root@localhost ~]# mount | grep ext /dev/vda6 on /ext4 type ext4 (rw,relatime,seclabel) [root@localhost ~]# ls / afs bin boot dev etc ext4 home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var [root@localhost ~]#
Also, when doing a manual installation, it is not possible to select the ext2 and ext3 file systems on the custom partitioning spoke. It could be related?
Please provide the package NVR for which bug is seen:
RHEL-10.0-20240519.53
anaconda-40.22.3.2-1.el10
python-blivet-3.10.0-2.el10
libblockdev-3.1.0-3.el10
How reproducible:
Always
Steps to reproduce
- See above
Expected results
All defined mount points created and mounted when the installed system starts.
Actual results
ext2 and ext3 filesystems created, but not mounted when the system starts.
- links to
-
RHBA-2024:132121 libblockdev bug fix and enhancement update