[Solved] No access to files with ls despite correct chmod

SuperManitu · 13. Januar 2015

Hello,
I tried to access my files on my shared device via CLI as user account and I get access denied

this is the output of ls -l (as root):

Code

drwxrws---+  2 root users 4096 Jan  6 18:59 Calibre
drwxrws---  14 root users 4096 Dez 31 19:15 Dirk
drwxrws---  22 root users 4096 Jan 11 23:12 Familie
drwxrws---  48 root users 4096 Dez 31 22:27 Gesa
drwxrws---   4 root users 4096 Dez 31 22:28 Goldene Hochzeit
drwxrws---   6 root users 4096 Jan 11 23:11 Jan
drwxrws---  18 root users 4096 Dez 31 22:35 Kluthe
drwxrws---  11 root users 4096 Dez 31 22:38 Lina
drwxrws---  15 root users 4096 Dez 31 23:10 Stark

the output of id -a (as user):

Code

uid=1000(jan) gid=100(users) Gruppen=100(users),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),108(ssh),111(netdev),114(sambashare)

why I don't get access?

subzero79 · 13. Januar 2015

So you're trying to access CLI as jan?

please go to the web interface for users and check that the user jan has a valid shell

SuperManitu · 13. Januar 2015

I want to read and write files as user (so as jan)

I have no problems logging into the shell, I get this output for the two commands:

Code

jan@NAS-vanBruegge:~$ id -a
uid=1000(jan) gid=100(users) Gruppen=100(users),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),108(ssh),111(netdev),114(sambashare)
jan@NAS-vanBruegge:~$ ls /media/be27e9ef-403e-4678-9762-fade43d22a34/Daten
ls: Access to /media/be27e9ef-403e-4678-9762-fade43d22a34/Daten not possible: No Permissions

subzero79 · 13. Januar 2015

Zitat von SuperManitu

device via CLI as user account and I get access denied

This what i understood, access denied not "No Permissions"

Can you post the following command stat /media/be27e9ef-403e-4678-9762-fade43d22a34/ and stat /media/be27e9ef-403e-4678-9762-fade43d22a34/Daten as root please.

Is this non single disk configuration like AUFS or Snapraid?

SuperManitu · 13. Januar 2015

Here is the output:

Code

root@NAS-vanBruegge:~# stat /media/be27e9ef-403e-4678-9762-fade43d22a34/
  Datei: „/media/be27e9ef-403e-4678-9762-fade43d22a34/“
  Größe: 4096           Blöcke: 8          EA Block: 4096   Verzeichnis
Gerät: 831h/2097d       Inode: 2           Verknüpfungen: 6
Zugriff: (2770/drwxrws---)  Uid: (    0/    root)   Gid: (    0/    root)
Zugriff    : 2015-01-13 08:46:37.704471437 +0100
Modifiziert: 2015-01-12 19:16:06.107518600 +0100
Geändert   : 2015-01-12 19:16:06.107518600 +0100
 Geburt    : -
root@NAS-vanBruegge:~# stat /media/be27e9ef-403e-4678-9762-fade43d22a34/Daten
  Datei: „/media/be27e9ef-403e-4678-9762-fade43d22a34/Daten“
  Größe: 4096           Blöcke: 8          EA Block: 4096   Verzeichnis
Gerät: 831h/2097d       Inode: 55836673    Verknüpfungen: 11
Zugriff: (2770/drwxrws---)  Uid: (    0/    root)   Gid: (  100/   users)
Zugriff    : 2015-01-13 19:27:57.942489328 +0100
Modifiziert: 2015-01-06 18:54:41.731974674 +0100
Geändert   : 2015-01-13 19:27:51.858485404 +0100
 Geburt    : -

Alles anzeigen

It's just a normal ext4 disk without any Raid or similar stuff

SuperManitu · 13. Januar 2015

I see what you mean, I set the permissions for the whole disk with the same chmod command and i can read it now

command:

Code

chown root:users -R /media/<UUID>
chmod 2770 -R /media/<UUID>

Thanks

subzero79 · 13. Januar 2015

That FS was coming from another system probably?. Run this please

chmod 0755 /media/be27e9ef-403e-4678-9762-fade43d22a34/ below this path the permissions seems correct, the default is 775, but apparently you choose 770. In both cases users should be able to access the files now

subzero79 · 13. Januar 2015

Zitat von SuperManitu

I set the permissions for the whole disk

I understand now, the top level file system has root:root by default, so if you close perms to 770 you deny access to others, in this particular case the group users (you, jan, everybody else)

Don't mess with the file permissions if you don't know what you're doing

Jetzt mitmachen!