Unable to Mount /home Partition in RHEL 9.5 (Dual Boot with Windows 11) - Red Hat Customer Portal (original) (raw)

I encountered an issue with my RHEL 9.5 system where the /home partition failed to mount during boot. At the time of the issue:

The /home directory was part of an LVM logical volume located on nvme0n1p8.
Despite the failure to mount during boot, the partition was accessible via a live USB session.
The system was configured as a dual-boot with Windows 11.

Steps Taken to Resolve
Booted the system using a live USB to access the /home partition on nvme0n1p8.
Created a tar archive of the /home data and moved it to a new partition (nvme0n1p2).
Updated the /etc/fstab file to point to the new location of /home on nvme0n1p2.
Rebooted the system, and it worked fine.
Although this workaround resolved the issue, I would like to understand the root cause and how to avoid such issues in the future.

Command Outputs
df -h (Current Setup After Workaround)
Filesystem Size Used Avail Use% Mounted on
devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs 7.6G 75M 7.5G 1% /dev/shm
tmpfs 3.1G 21M 3.0G 1% /run
efivarfs 268K 201K 63K 77% /sys/firmware/efi/efivars
/dev/mapper/rhel-root 70G 48G 23G 68% /
/dev/nvme0n1p6 960M 559M 402M 59% /boot
/dev/nvme0n1p2 150G 54G 96G 36% /home
/dev/nvme0n1p1 508M 34M 475M 7% /boot/efi
tmpfs 1.6G 128K 1.6G 1% /run/user/1000

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 150G 0 part /home
├─nvme0n1p3 259:3 0 16M 0 part
├─nvme0n1p4 259:4 0 70.6G 0 part
├─nvme0n1p5 259:5 0 642M 0 part
├─nvme0n1p6 259:6 0 1G 0 part /boot
├─nvme0n1p7 259:7 0 45.2G 0 part
└─nvme0n1p8 259:8 0 170.9G 0 part
├─rhel-root 253:0 0 70G 0 lvm /
└─rhel-swap 253:1 0 7.7G 0 lvm [SWAP]

pvscan
No matching physical volumes found

lvscan
(No output)

Updated /etc/fstab Entry for /home
UUID=c07824ac-ba38-4bf9-b353-3fb4b71b4d04 /home xfs defaults 0 0

blkid
/dev/mapper/rhel-swap: UUID="0d2d17a4-548f-403c-880e-575aebfe9f35" TYPE="swap"
/dev/nvme0n1p7: LABEL="Data" UUID="7218E74A18E70C43" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1d14089c-5765-4045-8994-97075fd178b5"
/dev/nvme0n1p5: UUID="22F46388F4635CD3" TYPE="ntfs" PARTUUID="0684bfa1-64c8-4ad9-a8e1-8f5b22e90329"
/dev/nvme0n1p3: PARTLABEL="Microsoft reserved partition" PARTUUID="af19e373-8ed6-4bf9-b9de-5c2b820eb21f"
/dev/nvme0n1p1: UUID="B258-BD72" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="2f8bc95c-4c57-440f-9c5a-d44b01a47278"
/dev/nvme0n1p8: UUID="kK7NFQ-NlE2-o1rk-t8sZ-9rAc-sw5I-Gp0sDy" TYPE="LVM2_member" PARTUUID="bd850b28-2924-4d3f-bbb3-e145c57fe009"
/dev/nvme0n1p6: UUID="5d37bb66-0f72-4361-b11d-d2487bba7ba7" TYPE="xfs" PARTUUID="2fd818b5-ed29-498a-a035-9f85f4a9efc9"
/dev/nvme0n1p4: UUID="CAD87983D8796E97" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7695a20b-f064-4898-bdb7-f3760e444dfd"
/dev/nvme0n1p2: LABEL="new-rhel-hom" UUID="c07824ac-ba38-4bf9-b353-3fb4b71b4d04" TYPE="xfs" PARTLABEL="Basic data partition" PARTUUID="2878434a-8d3b-4559-9d0d-d40d4fa978f8"
/dev/mapper/rhel-root: UUID="a7ffbf3e-ff79-49d2-bc59-c0687b069206" TYPE="xfs"

cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="9.5 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.5"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.5 (Plow)"

uname -r
5.14.0-503.15.1.el9_5.x86_64

Filesystem on /home Partition (Original): It was part of an LVM setup (rhel-home) on nvme0n1p8.
Filesystem on /home Partition (Current): It is now a standalone partition (nvme0n1p2) formatted as ext4.

What could cause the /home partition on LVM to fail to mount during boot, especially when it remains accessible via a live USB?
How can I check if the issue was due to LVM corruption, filesystem errors, or kernel/driver-related problems?
Any suggestions for future-proofing my /home configuration to avoid such issues?
Why RHEL is not recognizing the original /home partition.

Thank you for your assistance!