You do not have the permissions necessary to view the contents of “HDD”

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

So I was recently doing an Arch install and ended up formatting my HDD in the process with fdisk. I gave up on Arch and reinstalled Ubuntu 14.04. Now whenever I try and open my HDD in Nautilus I get an error 'This Location could not be displayed. You do not have permissions necessary to view the contents of "HDD".'

I can use sudo nautilus and am able to view the files just fine. I can also format and relabel it with sudo gnome-disks , but the issue is that is a pain to do and would rather just have access to it without being root. I've tried running sudo chmod -R ug+rw /media/kalenpw/HDD but that does not solve this issue.

All the answers I find about this issue are about folders that always require elevated permissions, but this is the entire drive I can't access so they don't apply

Thanks for the help.

asked Jul 22 '16 at 21:13

kalenpw

3162417

What's the output of sudo LC_ALL=POSIX ls -ld "$HOME" /media/kalenpw/HDD?

– David Foerster
Jul 23 '16 at 14:42

add a comment |

All the answers I find about this issue are about folders that always require elevated permissions, but this is the entire drive I can't access so they don't apply

Thanks for the help.

asked Jul 22 '16 at 21:13

kalenpw

3162417

What's the output of sudo LC_ALL=POSIX ls -ld "$HOME" /media/kalenpw/HDD?

– David Foerster
Jul 23 '16 at 14:42

add a comment |

All the answers I find about this issue are about folders that always require elevated permissions, but this is the entire drive I can't access so they don't apply

Thanks for the help.

asked Jul 22 '16 at 21:13

kalenpw

3162417

All the answers I find about this issue are about folders that always require elevated permissions, but this is the entire drive I can't access so they don't apply

Thanks for the help.

permissions hard-drive nautilus

asked Jul 22 '16 at 21:13

kalenpw

3162417

asked Jul 22 '16 at 21:13

kalenpw

3162417

asked Jul 22 '16 at 21:13

kalenpw

3162417

asked Jul 22 '16 at 21:13

kalenpw

3162417

asked Jul 22 '16 at 21:13

kalenpw

3162417

What's the output of sudo LC_ALL=POSIX ls -ld "$HOME" /media/kalenpw/HDD?

– David Foerster
Jul 23 '16 at 14:42

add a comment |

What's the output of sudo LC_ALL=POSIX ls -ld "$HOME" /media/kalenpw/HDD?

– David Foerster
Jul 23 '16 at 14:42

What's the output of sudo LC_ALL=POSIX ls -ld "$HOME" /media/kalenpw/HDD?

– David Foerster
Jul 23 '16 at 14:42

add a comment |

2 Answers
2

active

oldest

votes

You should change owners. Run this command:

sudo chown $USER: /media/$USER/HDD

where $USER will complete to your current Ubuntu user and HDD is the name of the partition in question

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

add a comment |

After doing chown and chmod ...
In default file manager like Nemo -> right click on the folder or click on the background in you are inside that folder already -> properties -> Permissions -> Apply Permissions to enclosed files OR make the owner able to "read and write"

answered Dec 21 '17 at 6:08

Russo

1013

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f801852%2fyou-do-not-have-the-permissions-necessary-to-view-the-contents-of-hdd%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

You should change owners. Run this command:

sudo chown $USER: /media/$USER/HDD

where $USER will complete to your current Ubuntu user and HDD is the name of the partition in question

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

add a comment |

You should change owners. Run this command:

sudo chown $USER: /media/$USER/HDD

where $USER will complete to your current Ubuntu user and HDD is the name of the partition in question

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

add a comment |

You should change owners. Run this command:

sudo chown $USER: /media/$USER/HDD

where $USER will complete to your current Ubuntu user and HDD is the name of the partition in question

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

You should change owners. Run this command:

sudo chown $USER: /media/$USER/HDD

where $USER will complete to your current Ubuntu user and HDD is the name of the partition in question

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

edited Oct 17 '16 at 3:04

Wolf

7771719

edited Oct 17 '16 at 3:04

Wolf

7771719

edited Oct 17 '16 at 3:04

Wolf

7771719

answered Jul 22 '16 at 21:20

Sinoosh

8441620

answered Jul 22 '16 at 21:20

Sinoosh

8441620

answered Jul 22 '16 at 21:20

Sinoosh

8441620

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

add a comment |

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

Awesome thanks a million that fixed it. I'll accept your answer in 7 minutes when it lets me

– kalenpw
Jul 22 '16 at 21:21

This is not a long-term fix. These permissions will be lost as soon as you unplug the drive, so you'll have to run this command again every time you plug the drive back in.

– Cerin
May 23 '17 at 17:28

At first you may have to run ls -l /media/$USER to find out which mount point your drive is located at. In this case, of course, it was known to be mounted at /media/$USER/HDD. Ultimately, you may even want to run chown -R instead of just chown. If there’s a lost+found directory on the drive, you can change it back to root using sudo chown -R root:root /media/$USER/HDD/lost+found. And, by the way, the wrong owner for the hard drive can happen, for example, if you formatted the drive using a live CD/DVD, where the user is 999 and that’s who the owner will be.

– caw
Feb 1 '18 at 13:21

add a comment |

answered Dec 21 '17 at 6:08

Russo

1013

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

add a comment |

answered Dec 21 '17 at 6:08

Russo

1013

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

add a comment |

answered Dec 21 '17 at 6:08

Russo

1013

answered Dec 21 '17 at 6:08

Russo

1013

answered Dec 21 '17 at 6:08

Russo

1013

answered Dec 21 '17 at 6:08

Russo

1013

answered Dec 21 '17 at 6:08

Russo

1013

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

add a comment |

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

This will only work if you have the permissions to write on all the files/directories within that directory. Would be better to simply add the -R option (for recursive) to the chown command since anyway OP is already in the terminal

– derHugo
Dec 21 '17 at 6:31

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Ask Ubuntu!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Dtyjlui