Fedora version: 42
Basic info:
My HP Omen laptop has the following specs:
256GB NVME SSD drive
2 TB SSD Hard drive (Sandisk)
Its a dual boot configuration: Fedora 42 and Windows 10
The laptop originally came with 1TB Mechanical SATA disk drive (2.5 inch internal HDD). I upgraded it to a Sandisk 2TB SSD (2.5 inch) Hard drive two years back.
For faster performance, both Fedora and Windows OS are installed in the NVME drive.
Fedora OS runs from /dev/mapper/fedora_rootvg-root which is created in a NVME partition /dev/nvme0n1p7 as shown below.
To store my personal data, I use the 2 TB SSD disk I mentioned above. Fedora assigned the name /dev/sda for this drive.
For my personal data, I created the LV /dev/mapper/fedora_homevg-home which is created from PV /dev/sda3 as shown below.
/dev/mapper/fedora_homevg-home was mounted on mount point /home . This filesystem is currently missing. Details below.
/dev/mapper/fedora_rootvg-root was created from /dev/nvme0n1p7 and is mounted on /. This is currently working fine.
Everything has been running fine for the last 2 years since the SSD upgrade.
Following is an lsblk and df outputs, which I had captured few months back.
BUT, currently, lsblk output looks slightly different. Under ‘MOUNTPOINTS’ column, I see only /
Posted the screenshot at the bottom of this post.
## Output captured few months back
[sysadmin@localhost:/home/sysadmin]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 398.8G 0 part
├─sda2 8:2 0 11.1G 0 part
└─sda3 8:3 0 1.3T 0 part
├─fedora_homevg-home 253:1 0 1.3T 0 lvm /home
└─fedora_homevg-tmp 253:2 0 8G 0 lvm /tmp
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 238.5G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 132.2G 0 part
├─nvme0n1p4 259:4 0 980M 0 part
├─nvme0n1p5 259:5 0 512M 0 part /boot/efi
├─nvme0n1p6 259:6 0 1G 0 part /boot
└─nvme0n1p7 259:7 0 102G 0 part
└─fedora_rootvg-root 253:0 0 102G 0 lvm /
[sysadmin@localhost:/home/sysadmin]$
[sysadmin@localhost:/home/sysadmin]$ df -Th
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev
tmpfs tmpfs 16G 7.7M 16G 1% /dev/shm
tmpfs tmpfs 6.3G 2.1M 6.3G 1% /run
/dev/mapper/fedora_rootvg-root ext4 100G 39G 57G 41% /
/dev/nvme0n1p6 ext4 974M 281M 626M 31% /boot
/dev/mapper/fedora_homevg-tmp ext4 7.8G 58M 7.4G 1% /tmp
/dev/nvme0n1p5 vfat 511M 18M 494M 4% /boot/efi
/dev/mapper/fedora_homevg-home ext4 1.3T 555G 688G 45% /home
tmpfs tmpfs 3.2G 3.8M 3.2G 1% /run/user/1000
[sysadmin@localhost:/home/sysadmin]$
One month back, I remember getting a notification of some kind of disk related warning from Fedora. But, I ignored it.
Last night, when I switched on my laptop, it won’t boot. It is stuck in the emergency mode and I get the following message.
You are in the emergency mode. After logging in, type “journalctl -xb” to view system logs, “systemctl reboot” to reboot, or “exit” to continue boot up.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press enter to continue.
Following is what I see when I try to login to rescue mode thing in Grub.
–
Later, I managed to log into bash terminal using the method used by this guy, i.e. by adding init=/bin/bash to grub
Although I get to login as root, I cannot edit /etc/fstab. I will come to this later.
After, I login, I can manually mount /boot and /boot/efi using the following. Don’t know why Fedora can’t do this during boot.
# mount /boot
# mount /boot/efi
and the following can be seen in df output
/dev/nvme0n1p6 ext4 974M 281M 626M 31% /boot
/dev/nvme0n1p5 vfat 511M 18M 494M 4% /boot/efi
The missing Volume group
I tried to mount /home (/dev/mapper/fedora_homevg-home). But, I noticed that logical volue fedora_homevg-home is missing in /dev/mapper location.
Then, from googling, I learnt that, it originally is located in a different path, which is /dev/fedora_homevg/home
So, I ran the following to activate the Volume groups
# vgscan ## scan for volume groups
# vgchange -a y ## activates the volume groups
Although vgchange output shows that volume group /dev/fedora_homevg has become ‘active’ now, I cannot see it in /dev path. See output below.
vgs also lists fedora_homevg . See the bottom of the above screenshot
Logical volume /dev/fedora_homevg/home (the real path, not the /dev/devmapper one) also seems to be displayed in lvdisplay. But, it is physically not present in /dev as the volume group /dev/fedora_homevg itself is not present.
Question1. Any idea what needs to be done to physically bring volume group fedora_homevg in /dev path ? And eventually in /dev/mapper
Question2. Is it my NVME drive that is broken or my SSD drive ?
Question3. Any idea why /boot and /boot/efi is not mounted during boot ?
Question4. Using the method I learnt from the youtube video mentioned above (using init=/bin/bash), I managed to login to bash as root.
But, I cannot edit /etc/fstab file. I have a created live USB of Fedora 42. Can the live USB help me in anyway here ?
Following is my /etc/fstab and current lsblk output. As you can see in lsblk output Under ‘MOUNTPOINTS’ column, only / is visible
