this post was submitted on 03 Dec 2023
9 points (90.9% liked)

Linux

5491 readers
789 users here now

A community for everything relating to the linux operating system

Also check out [email protected]

Original icon base courtesy of [email protected] and The GIMP

founded 2 years ago
MODERATORS
 

I made some changes to disk partitions. Now I'm seeing an issue with mounts. It's not a big problem but it's definitely confusing me.

[alex@rog-g15dk dev]$ sudo mount /home-temp
mount: /home-temp: can't find in /etc/fstab.
[alex@rog-g15dk dev]$ cat /etc/fstab
New                                         Partition    /home-temp   defaults            0 0 # /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
#                      
UUID=5E74-A00E                              /efi         vfat         noatime             0 2 
UUID=53a2c9bc-31dd-4e52-902f-633867253481   /            ext4         noatime             0 1 
tmpfs                                       /tmp         tmpfs        noatime,mode=1777   0 0 
/dev/nvme0n1p2                              /home        ext4         noatime             0 2 
/dev/nvme0n1p3                              /steam       ext4         noatime             0 2

Can anyone explain what 'mount -a' is trying to mount?

Here's the context on the changes I made. My desktop used to run windows. I recently installed linux as well (dual boot). A bit later I destroyed the windows partitions. This left the beginning 2/3 of the disk unused.

Today I decided to reclaim that disk space. I created 2 new partitions, copied some data to them, updated fstab accordingly, rebooted, and grew the steam partition to 700GiB. That process had a couple of small bumps, including a partition that was mounted to '/home-temp'. I destroyed that partition before using it all.

So this error is definitely caused by me. That's fine. I'm just trying to understand what's going on and how to clean up the little mess.

top 3 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 5 points 1 year ago (1 children)

Look at the first line of /etc/fstab.... Remove everything before the #

[โ€“] Lodra 5 points 1 year ago (1 children)

๐Ÿ˜ฏ

And that is why code reviews are useful. I just assumed it was a header row and moved on. Shame on me ๐Ÿคฃ

Thanks for the help!

[โ€“] [email protected] 6 points 1 year ago

Haha it happens to us all!