How could they have their land voted away? AB separating just wouldn’t work, with First Nations land being just one reason. Most separatists are simply traitors who don’t understand what the consequences would be. The ones who know what they’re doing know it would never work, but that’s not the point. The point is a weakened and fractured Canada. There’s a vested interest (primarily from the US) in dividing Canada, and this is a great way to do it.

All I’m saying is I hope Albertans don’t get complacent, and actually get out and vote at the referendum. Brexit has proven what lack of understanding and voter apathy can result in. It can just as easily happen in AB, and all it takes is Albertans not bothering to vote because “there’s no way separation will happen”.

Both quotes refer to humans. Nazis are sub human. Monsters get what they get.

Haha no, where did you get that out of what I said?

Two TV quotes go through my head every day.

Bill Nye: Everyone you’ll ever meet knows something you don’t.

Doctor Who: Always try to be nice, but never fail to be kind.

The real danger is voter apathy, with Albertans figuring there’s no way separation will win based on the high number of sigs on the petition so they don’t bother voting, much like Brexit.

The last AB referendum showed 38.7% of eligible voters voted. If that number holds the same, and your number of 30% want to separate is correct, it’s over. Every single traitor is going to vote, which could result in a landslide separatist win with 77% of voters voting to separate.

Wow, that fstab info is great thanks! I’ve added it to my notes.

Did Emby work after this? You said you had to remount, what did you use to do that?

If you can get Emby to work, you can then look at findmnt to see how the working directory is mounted (which options/etc) and then you can update your fstab to have those options so that it will mount on startup.

Yes, it works as it should. I’ve done it twice, and remounted once with gnome disk and once in Dolphin. However, I’m wondering if it’s an issue with installing Emby itself. Emby can access everything it should after remounting the drives, but the drive permissions are all user:user with 777 (which is probably why Emby can access it, it’s permission is other?) There’s nothing with permissions for user:emby like it should be, and sudo chown doesn’t change the group. There’s also no emby group option in the pulldown menu (when I was on Ubuntu I just used the pulldown to change the group permission). I went to make sure and ran groupadd emby but it said there’s already a group emby.

As it is right now it all works after remounting, that said the drives that should say ntfs-3g in findmnt say fuseblk, in fact all the NTFS drives are fuseblk.

Awesome thank you so much. I was wondering about the auto option. I’ll try changing that to ntfs-3g in gnome disk. I’m guessing I could also open fstab and change it manually but I’m not quite there yet haha. I just tried findmnt -t ntfs-3g and there was nothing. I’m expecting to see something when I run it again after changing from auto.

Edit: Changed one drive to ntfs-3g and rebooted. findmnt -t ntfs-3g is still nothing, but sudo nano /etc/fstab does show it’s ntfs-3g. Still had to remount for Emby to get write privileges. I then unmounted Samsung and ran sudo mount -t ntfs-3g -o uid=1000,gid=1000,rw /dev/disk/by-label/Samsung /mnt/Samsung. fstab still shows auto on that one.

This is what one of the drives looks like /dev/disk/by-label/Samsung /mnt/Samsung auto nosuid,nodev,nofail,x-gvfs-show,uid=1000,gid=1000,rw 0 0

Awesome thank you, I appreciate the rundown. I…sort of get it haha. I need to remount after reboot or they go back to ro, but it’s functional at least.

You should try to get off of NTFS ASAP. It’ll be fine for media storage but some things (pc games, esp) really hate running off of NTFS. I know how unwieldy it is to shift the data around, but it will save you a lot of headaches going forward.

I would love to, but it’s just not in the cards for the foreseeable future. I’m all in on Linux and the NTFS drives are the last remnant of Windows. One day…

How is Emby installed? In a container or are you running it on bare metal?

Just installed, no container.

When you say it sees them as read only, what indicates this? A log? A GUI element?

If I try to change artwork, delete, etc, a popup comes up saying it’s read only.

However, I think I got it set. I added uid=1000,gid=1000 to the end of the options string and Emby now has control.

Yeah, I’d prefer ext4 but the drives are large and full (made on Windows) and I have nothing to transfer to to reformat. They’re staying NTFS for now. I’ve used sudo ntfsfix -d /dev/sdxY on them and it comes up all good.

How could I bypass it if that’s the issue?

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.

EDIT: I think the issue is that the drives are ntfs so they mount as root automatically. Does this sound right? Unmount in gnome disk utility and change mount options back to auto. Then mount -t ntfs3 /dev/sdxY /mnt/drivename

If this is correct, I’m still unsure about the fact that gnome disk utility made changes to fstab and I don’t know if that will cause issues?

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.

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

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.

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.

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

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.

deleted by creator

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.