No Access Permissions

Real newbie question: How to get access permissions to my internal 3TB hdd? I have also external 3tb toshiba drive for backups and there is no any problems with permissions. How to solve this issue? :open_mouth:

While I think I more or less understand your question, it is in fact very vague.:

How to get access permissions…

Access to what for who?

Remember that the system only knows users. My assumption now is that you mean: How to get read, write and/or execute permissions for a particular user to the files on a file system.

That is of course a special case of something you should have at least basic knowledge of when running (or using as an enduser) any Unix/Linux system. Thus try to find information about file ownership (by user and group) and file permissions (read, write, execute for user, group, world/others). Else you will have more unpleasant surprises in the future.

For your special case, it is important to know what type of file system is on the device (or the partition(s) of the device).

For the device that you define as “external” it is probably a connectable mass-storage device with non-Linux file system, that is mounted through mediation of the desktop environment the users is using when it is connected. In that case, owing user/group and permissions are not in the non-Linux file system and they are faked by the system so that the desktop user can at least do the most basic things with the files on that file system.

Now to your other file system (what you call “internal”). We have to find out what type of file system is on there and how it is mounted. To find out


Post that here and add an explanation which one of the lines you think belongs to the device/partition you are talking about.

First sorry i was not so exact to told my “problem”. But i found way to get read/write permissions to my 3TB drive.Method: I go to File Manager as Super User and chance permission from /root to user name juha and group from /root to users. Now i can view and modify content how i want to do.

But it is still important to know how it is mounted, else after next boot you may have the same problem.

Things must be solved, noy bypassed.

What file system type is it?
Is it mounted through /etc/fstab?

I do not know it is mounted but here is error messages now: An error occurred while accessing ‘2.7 TiB Hard Drive’, the system responded: An unspecified error has occurred: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.


An error occurred while accessing ‘2.7 TiB Hard Drive’, the system responded: You are not authorized to perform this operation: Not authorized to perform operation >:(
So should i delete partition and create new?

As long as you do not provide any information nobody can help you.
And when you are changing the situation without coordinating with those who try to help you, your problem is a moving target and difficult to encounter.

So again. Show


and tell us which line you hink belongs to your problem file system.
And also show

cat /etc/fstab

and as root:

fdisk -l

here mount info: /dev/sdb1 on /run/media/juha/2648972b-6822-43ae-a3b0-dd9d7c4d6563 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
cat /etc/fstab
UUID=71aa942d-1819-42be-8834-83d903aa2b4c / btrfs defaults 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=4289cdfa-6534-4ae0-b79b-dad5f8e3c97f swap swap defaults 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /var btrfs subvol=/@/var 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /usr/local btrfs subvol=/@/usr/local 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /tmp btrfs subvol=/@/tmp 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /srv btrfs subvol=/@/srv 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /root btrfs subvol=/@/root 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /opt btrfs subvol=/@/opt 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /home btrfs subvol=/@/home 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=71aa942d-1819-42be-8834-83d903aa2b4c /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=94CC-2E64 /boot/efi vfat defaults 0 0

inux-itnv:/home/juha # fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 860
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CBF1BD12-D8E1-4C8C-B536-64D1E67DF682

Device Start End Sectors Size Type
/dev/sda1 2048 1026047 1024000 500M EFI System
/dev/sda2 1026048 972578815 971552768 463.3G Linux filesystem
/dev/sda3 972578816 976773134 4194319 2G Linux swap

Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST3000DM001-1ER1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B351D8C8-95C2-41F7-ADA3-FBC7711EB9BF

Device Start End Sectors Size Type
/dev/sdb1 2048 5860532223 5860530176 2.7T Linux filesystem


sdb is a GPT partiotioned disk with one partition sdb1.
On that partition sdb1 there is an ext4 (thus a Linux) file system.

That file partition/file sytem is not in /etc/fstab, thus it is not mounted at boot, but it seems to be mounted on behalf of a desktop session run by user juha. which most probably means that that mount point is owned by user juha.

But, this being a Linux file system, all files (and thus directories) inside the file system are subject to the Linux laws of ownership and permissions. Apparently the files in there were NOT owned by juha, thus probably not created by juha and probably even on another system (is the disk moved from another system?).

So what you did is using brute force by using root privileges and changing ownership of all the files from what it was to juha. User juha is very pleased now, but I have no idea what the original owner of these files will think about this ;).

This being a Linux file system, this wonership changes are in the file system and will still be there after a new boot, so no worry about that.

Probably you are now satisfied with the situation. Nevertheless a few advices you may or may not follow.

  • When this disk will allways be available on the system, consider giving it an entry in /etc/fstab. When you decide to do this, consider giving it a proper mount point, one withn the realm of user juha to make it more easily reachable for him. Either by using a mount point with his home directory (like /home/juha/nice-name, or by mounting at /mnt/juha-data and then juha can create a symlink to it from within his home directiry to /mnt/juha-data.
  • Try to find and read some article on the internet about file ownership and permissions.

And last but not least something about how to post computer texts (like those you posted above);
There is an important, but not easy to find feature on the forums.
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.