19
Help changing mount point in Cachyos (lemmy.ca)
submitted 1 day ago* (last edited 1 day ago) by Jack_Burton@lemmy.ca to c/linux@lemmy.ml
28 comments fedilink hide all child comments

I just installed Cachyos and I'm having trouble with mount points I think. At boot, I need a password to mount sata drives, and whatever permissions I change don't stay after rebooting. From what I can tell, it has to do with the drives mounting on /run/media, and apparently /run is a temp folder or something.

I think I need to change the mount points to something else, like /media (which doesn't exist and I'm hoping I can just create the folder and use it as a mount point?)

fstab is confusing me, can anyone help me with a quick rundown?

Edit: Think I've got it using gnome disk utility. I switched the mounts, everything boots up connected now. Had an issue where I couldn't read or write to the drives tho haha, but seems to have corrected after a reboot ( I think I may have installed ntfs-3g before the reboot). The owner and group for all of them are now root for some reason, but it seems to be working anyway.

all 29 comments
sorted by: hot top controversial new old
[-] brucethemoose@lemmy.world 3 points 22 hours ago* (last edited 22 hours ago)

I think I may have installed ntfs-3g before the reboot

Isn’t this the legacy driver? Why do you need it?

…Respectfully, it feels like you’re falling into the classic Arch trap of “messing with too much stuff.”

I mount a whole bunch of NTFS Sata partitions at boot, on CachyOS, and they don’t need a password or FUSE driver package or anything. It just works out of the box. The only thing I chose to mess with was adding a single mount flag in fstab, and only so it plays with Windows permissions better.

[-] Jack_Burton@lemmy.ca 1 points 22 hours ago* (last edited 22 hours ago)

You're probably right. Did your drives mount in /run? That's where mine mounted on initial install which kicked off this whole thing. I read that /run was temp and that's why they need to be manually mounted with password at boot. I had no issues in Ubuntu Studio, and after finally finding the locations in /run I just figured it's how Cachy does it.

I'm debating just reinstalling from scratch and starting over. I must have done something wrong at install.

[-] brucethemoose@lemmy.world 2 points 22 hours ago* (last edited 22 hours ago)

I just let KDE handle it. I think… it was a long time ago. I’ll turn on my PC and check my fstab in a sec.

But yeah. I’d recommend a fresh install, with the philosophy of “don’t mess with the defaults unless it isn’t working, or you have a very good reason.” As not only are CachyOS defaults pretty good, but they’re set up in a way so the system will maintain itself through updates.

It’s (ironically) very different than my experience with Ubuntu, where I had to manually maintain a bunch of stuff and fight the system packages.

[-] Neptr@lemmy.blahaj.zone 4 points 1 day ago* (last edited 1 day ago)

For managing drives and mount points I usually use gnome-disk-utility because it makes everything easier and it uses mount options like nofail by default. You can choose whether a drive requires password to mount in there too.

[-] Jack_Burton@lemmy.ca 1 points 1 day ago

Interesting. I just checked, is this right? Unmount > additional partition options > deselect user session defaults > edit mount point to /media? The existing mount point in that section is /mnt/2c148... is that meant to be different from /run/media that it's currently on?

[-] Neptr@lemmy.blahaj.zone 1 points 1 day ago

/run/media is for ephemeral mount points (like a removable USB drive). /mnt is for more permanent mount points. Idr what /media is for but I have seen some Linux distros also use it for removable media.

[-] Jack_Burton@lemmy.ca 1 points 1 day ago

Appreciate it. I made a folder called media in root and mounted them there per your suggestion with gnome disk utility. I think part of the problem may have been I didn't know to install ntfs-3g (only used Ubuntu Studio prior to this which had a bunch of stuff auto installed). I had an issue after mounting where all the drives were read only but a reboot solved it, though I think I installed ntfs-3g right before the reboot so I can't be sure what made it work. The drives are all owner group root root now but they work at least.

[-] Neptr@lemmy.blahaj.zone 1 points 1 day ago

I can't tell if you are saying you literally mounted the drive at /media or that you mounted it at a subfolder, example: /media/drive1. The 2nd is the proper way of doing it.

Either way, glad I could help!

[-] Jack_Burton@lemmy.ca 1 points 1 day ago

Sorry it's the second. Each drive has a folder in /media that it's mounted in. Not sure if they're meant to be root:root though, when I chown nothing changes. I think I might need figure out chmod 755 stuff. It all seems to be working except my server can't write to any of them, it says they're read-only. They're also mounted as fuseblk.

[-] Neptr@lemmy.blahaj.zone 1 points 19 hours ago

What I usually do is sudo chown $USER -R /media/drive1

[-] Jack_Burton@lemmy.ca 1 points 19 hours ago

No go, can't change it. Gonna start from scratch I think.

[-] Oinks@lemmy.blahaj.zone 3 points 1 day ago* (last edited 1 day ago)

From what I can tell, it has to do with the drives mounting on /run/media, and apparently /run is a temp folder or something.

Probably not. Yes /run is a tmpfs, but that doesn't affect any other filesystems mounted inside of it - those have their own permissions (or don't in the case of FAT).

Since the drives are being mounted in /run/media they're probably being mounted by your file manager, not via /etc/fstab. You could instead have them mounted on boot by the root user via /etc/fstab (the classic way) or systemd.mount (slightly friendlier), or configure polkit to allow mounting drives without a password (more reasonable if you're talking about external or thumb drives).

The permission issue is probably for a different reason. Are you sure the filesystem(s) you're mounting supports POSIX style permissions? FAT doesn't, and NTFS requires a special flag for it. The files might look like they have permissions, but they're coming from the mount options and modifying them will either fail outright or not do anything.

Edit: Run lsblk -f to see all connected drives, partitions and file systems and their file system type.

[-] Jack_Burton@lemmy.ca 2 points 1 day ago

Since the drives are being mounted in /run/media they’re probably being mounted by your file manager, not via /etc/fstab. You could instead have them mounted on boot by the root user via /etc/fstab (the classic way) or systemd.mount (slightly friendlier),

This is where I'm stuck. I read that changing the mount via fstab requires the UUID, which I can see with lsblk -f. But /etc/fstab has the same UUID for every drive, I have no idea what to do with it. As it is the 3 internal sata drives don't auto mount (even though they're selected in settings) and require a password to mount, and revert pemissions after reboot. I read it's due to /run but I'm stuck.

The permission issue is probably for a different reason. Are you sure the filesystem(s) you’re mounting supports POSIX style permissions? FAT doesn’t, and NTFS requires a special flag for it. The files might look like they have permissions, but they’re coming from the mount options and modifying them will either fail outright or not do anything.

They're NTFS. I just switched from Ubuntu Studio to Cachyos and they worked fine with mounting and permissions on Studio. Studio had them mounted in /media, took me a while to find that they were under /run/media on Cachy.

[-] Oinks@lemmy.blahaj.zone 3 points 1 day ago* (last edited 1 day ago)

But /etc/fstab has the same UUID for every drive, I have no idea what to do with it.

That would be because every entry (except /boot and /tmp) is a subvolume of the same btrfs volume. Your other drives just aren't in there.

You might want to read man fstab and maybe the Arch wiki pages for fstab and NTFS. It's not that difficult as long as you make sure to not reboot with a broken fstab (using nofail is also a good idea). And yes you can just mount them to /media if you want, as long as the mount point is an empty directory.

Ubuntu Studio might have achieved this in a different way but since you're in Arch land now it's probably better to do what the Arch documentation recommends.

[-] Jack_Burton@lemmy.ca 2 points 1 day ago

Haha yeah it's been a journey. 5 months into Linux but I've learned a ton. I'll start digging into this and in the mean time just settle for mounting at boot and changing the permissions to /run/media/USER every time so my server can get in. Appreciate the time, thank you.

[-] JASN_DE@feddit.org 3 points 1 day ago

Can you post your fstab?

[-] Jack_Burton@lemmy.ca 2 points 1 day ago

[-] littleomid@feddit.org 1 points 1 day ago

And your lsblk-f

[-] Jack_Burton@lemmy.ca 1 points 1 day ago

command not found

[-] littleomid@feddit.org 1 points 1 day ago

Are you sure? That seems unlikely. Wray does pacman -Qi util-linux say?

Also see this: https://wiki.cachyos.org/configuration/automount_with_fstab/

[-] Jack_Burton@lemmy.ca 1 points 23 hours ago* (last edited 23 hours ago)

Nevermind, I didn't put a space for -f

[-] littleomid@feddit.org 1 points 22 hours ago

Then please post the output of lsblk -f.

All you need to do after that is to take the UUID and add it to /etc/fstab.

[-] Jack_Burton@lemmy.ca 1 points 22 hours ago* (last edited 22 hours ago)

Thank you. I've since changed the mount point to /media/user/drive folder with gnome disk utility. They now boot up no problem, but I've hit some other snags haha. The mount point is owned by me but the drives themselves are root with full privileges for all users (not sure if that's normal, chown does nothing). I can manually create, delete, move, etc in the drives but my media server (emby) can access everything but cannot create or modify, it says the drives are read only. I can't remember the command I used to check but the all seem to be rw enabled. I can't change the group to emby from root either, chown seems like it succeeds but permissions don't change. They're also all fuseblk filesystem now.

Everything but the server seems to be working but I don't feel like it's right with permissions. After Ubuntu Studio I thought I'd have a handle on going to arch-based haha, everything else is perfect it's just this drive stuff that's not right.

[-] littleomid@feddit.org 1 points 14 hours ago

What does ls -l say in the directory where you mounted the drive?

[-] Jack_Burton@lemmy.ca 1 points 14 hours ago* (last edited 14 hours ago)

I've reinstalled Cachy. Still having issues with setting up my emby server. I left the drives in the /run/media/user directory, though the /user folder has a lock on it. I can chown to me, but it doesn't stay after reboot. In fact nothing does, the hello screen pops up every time even when it's switched off and I had to re-do permissions on everything to let the server in. Permissions for the server say they're correct, but in the right-click permissions, the Group, Owner, Others pulldowns are blank and greyed out. This is ls -l from /run/media/user

drwxrwxrwx 1 user user 24576 Dec 18 15:26  Samsung
drwxrwxrwx 1 user user  4096 Aug 21 15:47  Seagate
drwxrwxrwx 1 user user  4096 Dec 17 20:32 'Seagate II'
drwxrwxr-x 1 user user  24576 Dec 18 15:26 'Seagate III'
drwxrwxr-x 1 user user  4096 Dec 17 20:29 'Storage Mark IV'
drwxrwxrwx 1 user user  4096 Nov 29 20:18 'Storage Mark V'

Can't see it here but the first 3 drives names and the last one are highlighted green and I have no idea what that means.

[-] littleomid@feddit.org 1 points 5 hours ago* (last edited 4 hours ago)

Honest critique: if you want to use arch, learn to install it manually first. I don’t like the fact that Cachy advertises itself as beginner friendly because it obviously is not.

Hit the arch wiki and learn how to mount, his file system works etc. also for love of God, stop chowning/777ing all your files 😀

[-] Jack_Burton@lemmy.ca 1 points 52 minutes ago

Haha I didn't 777 anything, that's how they mounted as root after changing the mount point. But you're totally right, Cachy gave me the impression it would be a simple setup.

That said, I'm hoping you can answer a quick question. I've reinstalled again, changed mount points with gnome disk utility to /mnt/drivename, and they mount at boot but they're all owned by root now. I'm able to access everything (I'm assuming due to 777) and my server can see everything using sudo setfacl -m user:emby:rwx /mnt (but this doesn't stay after reboot and I have to do it again).

The server has an option to auto organize files, but it can't access the folder I use for it, it says the drive is read only (I can create/delete in it so it must be rw).

After everything I've learned, I think I need to dive into learning fstab and permissions properly, but honestly I'm pretty overwhelmed. At this point, would you say permissions and fstab are where I need to focus? Fstab because drives mount as root and permissions for, well, permissions? I'm just looking for guidance on where to start to solve this myself.

[-] Jack_Burton@lemmy.ca 1 points 1 day ago

` GNU nano 8.7 /etc/fstab

/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=286B-26F7 /boot vfat defaults,umask=0077 0 2 UUID=25d4a86d-3af5-4b4f-96db-004e921390dd / btrfs subvol=/@,defaults,noatime,compress=zstd,> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /home btrfs subvol=/@home,defaults,noatime,compress=z> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /root btrfs subvol=/@root,defaults,noatime,compress=z> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /srv btrfs subvol=/@srv,defaults,noatime,compress=zs> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /var/cache btrfs subvol=/@cache,defaults,noatime,compress=> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /var/tmp btrfs subvol=/@tmp,defaults,noatime,compress=zs> UUID=25d4a86d-3af5-4b4f-96db-004e921390dd /var/log btrfs subvol=/@log,defaults,noatime,compress=zs> tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

`

this post was submitted on 17 Dec 2025
19 points (100.0% liked)

Linux

57274 readers
238 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz