18
/etc/fstab bing a very important NTFS drive on boot (lemmy.world)
submitted 3 weeks ago by to c/linux4noobs@programming.dev
3 comments fedilink hide all child comments
 

Debian 13.

I have an FSTAB config that auto mounts a second drive , NTFS fstype that used to be on windows (same laptop) UUID=666 /media/userName/Data auto defaults,nofail,x-systemd.automount 0 2

Because the /media/userName/Data path was made in a way that didn't transfer ownership to my user, and because I am clueless about user/group management on linux, Virtual machine manager and jenkins and all the other program based users that don't really get a "real" user I can manage on cockpit or similar (AFAIK) can't use that disk for writing information to and etc.

I already tried to change owner to a shared group in a shitty way that locked me out of that very important drive. Also, it doesn't seem to work anyway, and just fucking sets it back to root or ignores it when I try to do it.

What's the simplest change I can make to the fstab entry or ownership to make use of that drive for jenkins pipelines , steam games and most importantly, Virtual Machine Manager guest machines?

This shit scares me, and I have very little time, so I will get back to you guys in due time, and appreciate your assistance.

all 3 comments

sorted by: hot top controversial new old
[–] 4 points 3 weeks ago* (last edited 3 weeks ago)

You can't set permissions and ownership because NTFS doesn't support Linux style permissions and ownership.

Why not copy the data elsewhere, format drive to ext4 or btrfs, then copy the data back? Don't use NTFS on Linux unless you enjoy having less control, unless you're sharing the drive with Windows then you have no choice I suppose.

TLDR: NTFS bad (not really, but sort of).

If you are staying on NTFS, you can stop reading here.

Anyway if you decide to migrate off NTFS, and assuming your username is zapBrannigan:

(recursively sets user ownership to zapBrannigan, sets group ownership to root, setting the group to root is a nice default because it's effectively "no group" and limits access to non-privileged, non-you users)
sudo chown -R zapBrannigan:root /path/to/drive

(recursively sets user, group, other permissions, where 664 corresponds to "allow rw-rw-r--", in this representation, the mode bits 664 are a binary mask, 6=110, 4=100, so you're setting 110110100 which sets the allow described above)
sudo chmod -R 664 /path/to/drive

The first command sets ownership to you, the user. The second command allows the user to read and write every file, and other users to read every file, set to 660 to forbid other users.

After that I suspect your fstab issue will become solvable.

If anything scares you, audit the data and backup the critical segments before working with the drive. I am assuming you don't have free space to backup the entire drive, if you do, then just do that.

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 3 weeks ago* (1 child)

    Try adding uid=<your uid>,gid=<your gid> to the mount options. id will show your uid and gid (probably 1000). That should give you ownership of the file system.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •