Missing mount point

As some of you know I plan to install Win 10 and Garuda for my roommate. Today under Manjaro he asked me to install and setup a new drive to replace a failing one. Normally a no brainer, just remove the old drive, add the new one, format it, and mount it. Today however I noticed that two of his mounts were messed up. The first one being the drive that got replaced /home/whacker/Whackers/TV Series was mounted to /home/whacker/Whackers/Music and the second one Music was mounted to /home/whacker/Whackers/TV Series. Now the issue is that I got the TV Series drive mounted correctly and showing in fstab, the Music drive / mount is not listed in fstab for some reason. I believe what happened is when I went to correct the mount point for Music I didn't unmount the TV Series thus not allowing for the mount point of Music to be changed from /home/whacker/Whackers/TV to /home/whacker/Whackers/Music. What I'd like to do is add the proper line in fsbtab to get the Music mount to properly mount. Normally I'd just use Gparted to simply recreate the partition and copy everything back to it from the Master Backup, but there's 2+ gigs to copy back from a USB 3.0 drive to a USB 3.0 drive. I believe it would be far faster to fix the current mounting than to copy the files back. Help with this would be greatly appreciated. Thanks

[[email protected] ~]$ inxi -Fxxxza
System:    Kernel: 5.9.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.9-x86_64 
           root=UUID=7d67e5ae-6534-4cf3-af7b-3ee5c52d402c rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Desktop: KDE Plasma 5.20.3 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x 
           serial: <filter> UEFI: American Megatrends v: 2202 date: 07/14/2020 
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard serial: <filter> 
           charge: 55% (should be ignored) rechargeable: yes status: Discharging 
CPU:       Info: 8-Core model: AMD Ryzen 7 1700X bits: 64 type: MT MCP arch: Zen 
           family: 17 (23) model-id: 1 stepping: 1 microcode: 8001138 L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
           bogomips: 108634 
           Speed: 3492 MHz min/max: 2200/3400 MHz boost: enabled Core speeds (MHz): 1: 3490 
           2: 1996 3: 1994 4: 1988 5: 2196 6: 2196 7: 2196 8: 2194 9: 1999 10: 1996 11: 2196 
           12: 2195 13: 2196 14: 2194 15: 3482 16: 1991 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 
           mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
           vendor: Gigabyte driver: amdgpu v: kernel bus ID: 06:00.0 chip ID: 1002:67df 
           Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: amdgpu,ati 
           unloaded: modesetting alternate: fbdev,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: HDMI-A-0 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
           diag: 598mm (23.5") 
           renderer: Radeon RX 580 Series (POLARIS10 DRM 3.39.0 5.9.10-1-MANJARO LLVM 11.0.0) 
           v: 4.6 Mesa 20.2.2 direct render: Yes 
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] 
           vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 06:00.1 
           chip ID: 1002:aaf0 
           Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 08:00.3 chip ID: 1022:1457 
           Device-3: Creative Live! Cam Sync HD [VF0770] type: USB 
           driver: snd-usb-audio,uvcvideo bus ID: 1-7.1.1:6 chip ID: 041e:4095 
           Sound Server: ALSA v: k5.9.10-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK 
           driver: r8169 v: kernel port: f000 bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 14.89 TiB used: 7.06 TiB (47.4%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/sda vendor: Seagate model: ST33000650NS size: 2.73 TiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: 0004 scheme: GPT 
           ID-2: /dev/sdb vendor: A-Data model: SU635 size: 223.57 GiB block size: 
           physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 1c87 
           scheme: GPT 
           ID-3: /dev/sdc vendor: Samsung model: MZNTY128HDHP-000L1 size: 119.24 GiB 
           block size: physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> 
           rev: 3L0Q scheme: GPT 
           ID-4: /dev/sdd type: USB vendor: Seagate model: ST330006 51NS size: 2.73 TiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 7101 
           scheme: GPT 
           ID-5: /dev/sde type: USB model: 51NS size: 2.73 TiB block size: physical: 4096 B 
           logical: 512 B serial: N/A rev: 7101 scheme: GPT 
           ID-6: /dev/sdf type: USB vendor: Seagate model: Expansion Desk size: 5.46 TiB 
           block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0915 
           scheme: GPT 
           ID-7: /dev/sdh type: USB vendor: Western Digital model: WD Elements 25A2 
           size: 931.48 GiB block size: physical: 512 B logical: 512 B serial: <filter> 
           rev: 1014 scheme: GPT 
Partition: ID-1: / raw size: 223.28 GiB size: 218.77 GiB (97.98%) used: 71.12 GiB (32.5%) 
           fs: ext4 dev: /dev/sdb2 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 29.5 C mobo: N/A gpu: amdgpu temp: 37.0 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 826 
Info:      Processes: 446 Uptime: 1h 12m Memory: 23.48 GiB used: 3.41 GiB (14.5%) 
           Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 11.0.0 Packages: 1605 
           pacman: 1582 lib: 432 flatpak: 23 Shell: Bash v: 5.0.18 running in: konsole 
           inxi: 3.1.08 
[[email protected] ~]$

Use lsblk -f to identify the partition and its UUID, then add a line to the /etc/fstab .

This isn't the Manjaro forum. :wink:


I know it's not the Manjaro forums. I posted here cause between tomorrow and Thrusday I'll be getting his new Win 10 and Garuda installed and once set up the Manjaro disk will be reset and removed from the system. I just didn't want to hit up the Manjaro forums for what would probably be the last question asked there for now.

Now that said you mean something like this?

`UUID=6dfbe343-3531-4452-89c0-e47824758ec8 auto /home/whacker/whackers/Music/ auto nosuid,nodev,nofail,x-gvfs-show

If so will that override and replace it trying to mount to TV Series?

The true shame is why couldn't the one drive hold out for another 3 days. I wouldn't of even had to create this thread then.

UUID=6dfbe343-3531-4452-89c0-e47824758ec8 auto /home/whacker/whackers/Music/ auto nosuid,nodev,nofail,x-gvfs-show

If I'm right that should be his.

You don't have to use a path if you have the UUID, you can use

UUID=6b808587-8a97-4ce9-85fa-77c285c304ab auto /mnt/Music/ nosuid,nodev,nofail,x-gvfs-show 0 0

OK so the below for his then.

UUID=6dfbe343-3531-4452-89c0-e47824758ec8 auto /home/whacker/whackers/Music/ auto nosuid,nodev,nofail,x-gvfs-show

Sure, use whatever UUID is correct for your system.

Also just check you have the correct options in the correct order, https://wiki.archlinux.org/index.php/fstab#Usage


Fixed my last post. Thanks @jonathon much appreciated.


@jonathon found a part of the problem. For some reason the system kept the UUID of the old TV Series drive. Posting this update in case it can help others.

1 Like

The system's memory on mounts is only the contents of fstab. mtab is reset after each reboot.

It seems like a user mistake.

I would like to mention that there is a mistake in all previous posts on possible or actual fstab entries, which may not be actual, just human memory errors :wink:
The auto flag (FS type) is entered twice, of which the 1st occurrence should not exist. It's an example of how an error may create a problem :man_shrugging:


I find fstab a very interesting Linux feature that volumes could be written about all its permutations for mounting. It's almost like black magic mastering all its combinations of options.

I enjoy using fstab, but I'm sure most users new to Linux dread having to edit fstab. Always be sure to make a copy before editing the original. Not quite as necessary with btrfs and timeshift, but still a good habit to get into all the same.

pacman -Q gnome-disk-utility
gnome-disk-utility 3.38.0-1

Start 'gnome-disks'


Using, "Disks" is just cheating. :smile:

But, seriously I feel that sometimes the options it selects are not the best. Also if you ever intend to do advanced stuff like mounting shares, bind mounts etc, then you really need to do some RTFM.

Just from looking at his prior fstab configuration, I'm pretty sure he already used disks to write his load line. Disks fingerprints are all over it, and as I say I'm not keen on some of it's decisions for options.


Exactly :point_up:

And this trust is some time betrayed... :cry:


I always make a backup of any important file I have to edit or manually replace just in case. Linux like Windows isn't that hard to get into to replace the original if need be and be back where one was. Looks like I will have to use the original command I put together to get auto-mount. That correction @jonathon posted does not have the two drives auto-mount.

@SGS I actually prefer using Disk rather than fstab, but the bright side this issue taught me something new.

@tbg Calling using Disk cheating is an opinion, As for the options it selects it typically selects to have the volume auto-mount and not have to be manually mounted. At least when you manually edit the volumes mount settings in Disk.

I see what you mean about the auto command. I just duplicated another line replaced with the correct UUID and path. That duplicate would of been done by the system.

It really really wasn't even an opinion, it was more of a joke. That's why there was a smiley at the end of my sentience, (so you'd get that I was just kidding around). This isn't EnOS or Arch, this distro is chock full of GUI tools for those that prefer them. Just in case you hadn't noticed all the new GUI system tools, we probably have far more GUI system config apps than most any other Arch based distro now.

The guys are busy developing more GUI tools to assist newbies all the time. This distro's probably more GUI friendly than most other Arch flavors I'd say. There's absolutely nothing wrong with using a GUI tool rather than the terminal or editing config files by hand.

My real opinion is however that sometimes editing a config file by hand gives you more fine grained control than a GUI app that makes rather more generic one size fits all type decisions. There's nothing wrong with using a GUI app to make those decisions. However, if you need to mount things in a more advanced manner you don't have a lot of other ways to do some of those things except via editing config files by hand. Some advanced methods of mounting really don't have any GUI tools available in Linux yet. So you don't have much alternatives except learning fstab usage or in some cases there might be an app (but it's not GUI).


@tbg I wrote that post in a hurry while in the middle of cooking dinner and half starving, so my apologies it wasn't my intention to step on anyones toes. To be honest I probably paid more attention to the post above yours. As for the GUI friendly that's exactly why I selected Garuda for my roommate. Myself I do prefer EOS cause I can build it to my liking without being as barebones as pure Arch. Unfortunately there are a couple on the EOS forums that are true Terminal diehards and true ***es to anyone using any GUI app.

Now that said I'm more than willing to get under the hood with a proper tut, and if I know in the particular instance it is either going to be faster or as you said give me better control over what I'm trying to do.

As for the mounting agree. As far as I know with whatever caused the issue on Gary's system going in to fstab or correcting via the terminal were my best options.

The thing with the terminal is I know I screw up with the keyboard a lot and I mean a lot, so I get a bit leery typing thing into the terminal without a cut and paste option from some tut I found or something someone posted trying to help me.

Now for those celebrating Turkey day please be salf while still enjoying the day.

Gobble Gobble,

1 Like