No problem with 3 of the external drives I use for media storage but can’t get it done on the 4th drive for some reason. All 4 drives are ext4.
Used this cmd…
sudo chown $USER:$USER /mnt/18TB1/4K
No problem with 3 of the external drives I use for media storage but can’t get it done on the 4th drive for some reason. All 4 drives are ext4.
Used this cmd…
sudo chown $USER:$USER /mnt/18TB1/4K
Can you share the output of findmnt /mnt/18TB1/4K or whatever directory is the one that is actually the root of the mount?
Adding the 4K doesn’t return anything, removing that gives this…
[eosblu@machina ~]$ findmnt /mnt/18TB1/4K
[eosblu@machina ~]$ findmnt /mnt/18TB1
TARGET SOURCE FSTYPE OPTIONS
/mnt/18TB1 /dev/sdb1 ext4 rw,relatime
try this then
sudo chown -R $USERNAME /mnt/18TB1
Returned this…
[eosblu@machina ~]$ sudo chmod -R $USERNAME /mnt/18TB1
chmod: missing operand after ‘/mnt/18TB1’
Try ‘chmod --help’ for more information.
yeah I meant chown not mod that was a typo on me
Same thing?
[eosblu@machina ~]$ sudo chown -R $USERNAME /mnt/18TB1
[sudo] password for eosblu:
chown: missing operand after ‘/mnt/18TB1’
Try ‘chown --help’ for more information.
are you replacing $USERNAME with your actual username?
No pasting it as shown. Now, with my user spelled out…
[eosblu@machina ~]$ sudo chown esoblu /mnt/18TB1
chown: invalid user: ‘esoblu’
[eosblu@machina ~]$
not sure but it seems the username is not valid. ![]()
Oooops spelling error on my part on username. Corrected seems to work …
EDIT: But still not the owner.
[eosblu@machina ~]$ sudo chown eosblu /mnt/18TB1
[eosblu@machina ~]$
show us the results of ls -l /mnt/18TB1
[eosblu@machina ~]$ ls -l /mnt/18TB1
total 16
drwxr-xr-x+ 158 eosblu eosblu 16384 Jan 22 2025 4K
ok its shows you are the owner of the root of the device. maybe rerun the command with the -R option like I posted will give you ownership of all
[eosblu@machina ~]$ sudo chown -R eosblu /mnt/18TB1
[eosblu@machina ~]$
That did it, many thx!!
Been trying to figure this out for 2 days. ![]()
A̶r̶r̶r̶g̶h̶!̶ ̶W̶h̶e̶n̶ ̶I̶ ̶t̶r̶i̶e̶d̶ ̶t̶o̶ ̶a̶d̶d̶ ̶t̶h̶a̶t̶ ̶f̶o̶l̶d̶e̶r̶ ̶t̶o̶ ̶J̶e̶l̶l̶y̶f̶i̶n̶ ̶I̶ ̶w̶a̶s̶ ̶n̶o̶ ̶l̶o̶n̶g̶e̶r̶ ̶t̶h̶e̶ ̶o̶w̶n̶e̶r̶ ̶a̶g̶a̶i̶n̶.̶
̶I̶ ̶r̶a̶n̶ ̶ ̶s̶u̶d̶o̶ ̶c̶h̶o̶w̶n̶ ̶-̶R̶ ̶e̶o̶s̶b̶l̶u̶ ̶/̶m̶n̶t̶/̶1̶8̶T̶B̶1̶ ̶a̶g̶a̶i̶n̶ ̶a̶n̶d̶ ̶n̶o̶t̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶n̶o̶w̶.̶
EDIT: I clicked on the wrong drive to check the Properties in the above screenshot so using -R didn’t actually work as I thought it did.
you may have an issue with your jellyfin then. Maybe the jellyfin is changing ownership?
I edited my post above. I had clicked on the wrong drive in the screenshot so using -R actually didn’t work.
-R should give you ownership “recursively” this is why you run it from the root folder. Then everything under that top (root) folder is owned by the same person. I actually have this as an alias to take ownership of drives
I originally ran chown with -R on all 4 drives during some of my many attempts to take ownership but this drive is the only one it’s not working on for some reason.
I can change the user and group but not owner.