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.

Edit 2: If anyone is here for the same issue, I’ve made another post which is more directed at the issue: NTFS drives. You can find it here https://lemmy.ca/post/57140934

  • brucethemoose@lemmy.world
    3·
    4 days 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.caOP
      1·
      4 days 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·
        4 days 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.

              • littleomid@feddit.orgEnglish
                1·
                4 days 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.caOP
                  1·
                  4 days 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.