The mount command is now overwhelmed with stuff that has nothing to do with physical disks. The "df" command is more informative:
[tom@trona tom]$ df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 4096 0 4096 0% /dev tmpfs 16409500 36348 16373152 1% /dev/shm tmpfs 6563804 1732 6562072 1% /run tmpfs 4096 0 4096 0% /sys/fs/cgroup /dev/mapper/fedora-root 51421664 38774008 10009832 80% / /dev/sda1 996780 253760 674208 28% /boot tmpfs 16409504 8396 16401108 1% /tmp /dev/mapper/fedora-home 57935892 24 54967088 1% /home /dev/sdb3 3829075716 2570131120 1064363420 71% /u1 /dev/sdc3 3827989484 2873761216 759702328 80% /u2 tmpfs 3281900 120 3281780 1% /run/user/1004And knowing what is in fstab is also useful:
/dev/mapper/fedora-root / ext4 defaults 1 1 UUID=7e22b711-b5cb-4771-909d-cdd9c7eb8e3d /boot ext4 defaults 1 2 /dev/mapper/fedora-home /home ext4 defaults 1 2 /dev/mapper/fedora-swap swap swap defaults 0 0 # On 4-25-2022 I switched from my Gigabyte to an Ebay ASUS motherboard # After this: # sda is my SSD # sdb is my WD4000 drive (/u1) # sdb is my second WD4000 drive (/u2) # sdc was my WD2003 drive (now retired) # sdd was my WD2002 drive (now retired) /dev/sdb2 swap swap defaults 0 0 /dev/sdb3 /u1 ext4 defaults 1 2 /dev/sdc2 swap swap defaults 0 0 /dev/sdc3 /u2 ext4 defaults 1 2I let Fedora automatically partition my SSD during install, which may have been a mistake, as I end up with these inscrutable fedora volume things. Maybe they are useful and flexible if you know how to play the game, but they just annoy me.
I set up sdb and sdc myself with normal partitions. As near as I can tell sda1 is /boot and via some fedora magic we get 3 partitions ( root, /home, and swap ) out of sda2 via the Fedora LVM scheme.
The "fdisk" command is to traditional tool to monkey with partitions.
[tom@trona tom]$ su Password: [root@trona tom]# fdisk -l /dev/sda Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors Disk model: Samsung SSD 850 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: dos Disk identifier: 0x5aed8c73 Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 2099199 2097152 1G 83 Linux /dev/sda2 2099200 250068991 247969792 118.2G 8e Linux LVM [root@trona tom]# fdisk -l /dev/sdb Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4000FYYZ-0 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: 1606BC22-85B0-415B-ACED-40F2983B38BC Device Start End Sectors Size Type /dev/sdb1 2048 98303 96256 47M Linux filesystem /dev/sdb2 98304 31445312 31347009 14.9G Linux swap /dev/sdb3 31445313 7814037134 7782591822 3.6T Linux filesystem [root@trona tom]# fdisk -l /dev/sdc Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD4000FYYZ-0 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: 82DCD6EE-4041-2A4B-B1B0-A660744DC70B Device Start End Sectors Size Type /dev/sdc1 2048 100351 98304 48M Linux filesystem /dev/sdc2 100352 33654783 33554432 16G Linux swap /dev/sdc3 33654784 7814037134 7780382351 3.6T Linux filesystem
Adventures in Computing / [email protected]