I'm missing an NVME partition

Ask Fedora
,
1

While attempting to upgrade from 42 > 44 (I’m getting an RPM transaction failed error), I think I found my main partition nvme0n1p3 isn’t mounted. I’ve done several commands to figure out what’s going on. I want to double check to make sure there’s something I’m missing.
Edit: To clarify, the upgrade wasn’t successful and I’m still on 42.

$ sudo lsblk -f
NAME                   FSTYPE      FSVER    LABEL       UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                           
└─sda1                 ext4        1.0                  7ccb7726-01bd-4dc0-846c-fcd1fb49a61b      1.2T    25% /media/ssd2
sdb                                                                                                           
└─sdb1                 ntfs                 Media Drive 8ED6E826D6E80FEF                                      
zram0                  swap        1        zram0       5cb00920-6dbe-4385-b95e-e774c80b8ccc                  [SWAP]
nvme0n1                                                                                                       
├─nvme0n1p1            vfat        FAT32                9D06-03B0                               591.3M     1% /boot/efi
├─nvme0n1p2            xfs                              fb07fcea-fced-4114-b598-a70557f51e7e    640.6M    37% /boot
└─nvme0n1p3            LVM2_member LVM2 001             hI2SGy-YJKB-FkRm-hhzJ-Lqoy-iMqw-ctBDab                
  └─fedora_fedora-root xfs

$ df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/fedora_fedora-root   15G   15G  524M  97% /
devtmpfs                        7.7G     0  7.7G   0% /dev
tmpfs                           7.8G  4.0K  7.8G   1% /dev/shm
efivarfs                        192K   46K  142K  25% /sys/firmware/efi/efivars
tmpfs                           3.1G  1.6M  3.1G   1% /run
tmpfs                           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs                           7.8G  4.0K  7.8G   1% /tmp
/dev/nvme0n1p2                 1014M  374M  641M  37% /boot
/dev/nvme0n1p1                  599M  7.5M  592M   2% /boot/efi
tmpfs                           1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs                           1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                           1.6G   12K  1.6G   1% /run/user/1000
/dev/sda1                       1.8T  465G  1.3T  27% /media/ssd2


$ sudo fdisk -l

Disk /dev/nvme0n1: 238.47 GiB, 256060514304 bytes, 500118192 sectors
Disk model: WDC PC SN530 SDBPNPZ-256G-1006          
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: FD7C4FF0-B65C-4F14-AEFE-31CE33637835

Device           Start       End   Sectors   Size Type
/dev/nvme0n1p1    2048   1230847   1228800   600M EFI System
/dev/nvme0n1p2 1230848   3327999   2097152     1G Linux filesystem
/dev/nvme0n1p3 3328000 500117503 496789504 236.9G Linux LVM


Disk /dev/mapper/fedora_fedora-root: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
2

This is what my ‘/etc/fstab’ looks like. I’m looking into this right now.

$ sudo cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Tue May 24 13:12:50 2022
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/fedora_fedora-root /                       xfs     defaults        0 0
UUID=fb07fcea-fced-4114-b598-a70557f51e7e /boot                   xfs     defaults        0 0
UUID=9D06-03B0          /boot/efi               vfat    umask=0077,shortname=winnt 0 2

#/dev/sdb1 /media/ssd2 ext4 defaults 0 2


$ sudo blkid
/dev/nvme0n1p3: UUID="hI2SGy-YJKB-FkRm-hhzJ-Lqoy-iMqw-ctBDab" TYPE="LVM2_member" PARTUUID="4e2489a1-7168-4132-90d8-dbb02df9aed5"
/dev/nvme0n1p1: UUID="9D06-03B0" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="94b41c19-c947-4c5f-991c-4fd72c1594ed"
/dev/nvme0n1p2: UUID="fb07fcea-fced-4114-b598-a70557f51e7e" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="9c82aa94-fa41-4af2-8973-def8689ec0e9"
/dev/sdb1: LABEL="Media Drive" BLOCK_SIZE="512" UUID="8ED6E826D6E80FEF" TYPE="ntfs" PARTUUID="e327e7b3-01"
/dev/mapper/fedora_fedora-root: UUID="fcc67c19-d09b-47ad-a5c0-1f4a55ac2b0a" BLOCK_SIZE="512" TYPE="xfs"
/dev/sda1: UUID="7ccb7726-01bd-4dc0-846c-fcd1fb49a61b" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="ext2tb" PARTUUID="1704bf7c-631d-43c4-8430-7bcdfe74cde3"
/dev/zram0: LABEL="zram0" UUID="5cb00920-6dbe-4385-b95e-e774c80b8ccc" TYPE="swap"
3

Isn’t that what’s normal for LVM? i.e. df shows you the mapper, not the underlying block device?

What did df -h show on Fedora 42?

4 
$df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/fedora_fedora-root   15G   15G  524M  97% /
devtmpfs                        7.7G     0  7.7G   0% /dev
tmpfs                           7.8G  4.0K  7.8G   1% /dev/shm
efivarfs                        192K   46K  142K  25% /sys/firmware/efi/efivars
tmpfs                           3.1G  1.6M  3.1G   1% /run
tmpfs                           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs                           7.8G  4.0K  7.8G   1% /tmp
/dev/nvme0n1p2                 1014M  374M  641M  37% /boot
/dev/nvme0n1p1                  599M  7.5M  592M   2% /boot/efi
tmpfs                           1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs                           1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs                           1.6G   12K  1.6G   1% /run/user/1000
/dev/sda1                       1.8T  465G  1.3T  27% /media/ssd2
5

Oh, I see. You never got to F44 so all of this is on F42.

As I say, seeing /dev/mapper/.... rather than the underlying partition mounted looks normal.

But the logical volume has only 15GiB of space and is almost full, so likely you need to expand that logical volume within its physical volume.

7

Should’ve clarified the upgrade wasn’t successful and I’m still on 42. I’ll try extending the partition and see what happens.

8

No worries, I should have paid more attention to “RPM transaction failed” :slightly_smiling_face:

9

Your root file system is 97% full and cannot be upgraded to f44 with that miniscule amount of free space.
Since the root file system is LVM and is on a partition with 238G of space while the LV only has 15G allocated, what is wrong with expanding it?

Your root file system also contains /home with the way you have that configured. I suggest adding an additional LV for /home so your personal data is not at risk in the same way as it is when contained in the root file system.

You also are using xfs for the root file system which adds additional problems with changing the file system size. I do not use xfs so cannot assist in expanding it.

It seems you would need to first extend the LV size, then this link gives some info about extending the xfs file system.

10

This could be Fedora Server variant where the /boot file system is also xfs.

According to gparted features gparted can handel xfs and seems also be capable to handle logical volumes.

11

I don’t know which variant is in use, but clearly /boot is also xfs as shown by his posts above with the fstab content.

12

That is also not important. Important is that the root file system is full, so either grow the root file system or remove a some big files, for example cache files, log files or temporary files.