Partition remains as read only
I just switched from Windows over to Ubuntu 18.04 and I am trying to get my internal drives set up. I have one SSD that has the os on it and a second larger SSD that I am trying to format.
To start I changed the format to ext4 using gparted. The drive formatted and then I was successfully able to mount the drive to a folder I had created. However this drive was in read-only mode.
In my research I found that I shouldn't be using the following command to open gparted:
sudo gparted
The reason being that there can be some problems with how the permissions are handed down when creating the partition. I then found that I could use this modified command to fix the problem:
sudo -H gparted
The documentation says this about -H.
The -H (HOME) option requests that the security policy set the HOME
environment variable to the home directory of the target user (root by
default) as specified by the password database. Depending on the
policy, this may be the default behavior.
The mount command I used was:
sudo mkdir /ssd
sudo mount /dev/sdc1 /ssd
It doesn't seem to output anything. The terminal just goes to the next line. However I can check inside of gparted to see that the drive has been mounted to the location I specified.
The error shows up when I try to create a new steam folder inside of the new drive:
Another thing that I noticed is that I am getting an error when launching gparted. An error comes up that says the following:
Unit -.mount does not exist, proceeding anyway.
I couldn't find a solution to this either and that might be related to why the drive is stuck.
partitioning mount gparted
edited Jan 11 at 22:01
Fabby
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
|
show 3 more comments
I just switched from Windows over to Ubuntu 18.04 and I am trying to get my internal drives set up. I have one SSD that has the os on it and a second larger SSD that I am trying to format.
To start I changed the format to ext4 using gparted. The drive formatted and then I was successfully able to mount the drive to a folder I had created. However this drive was in read-only mode.
In my research I found that I shouldn't be using the following command to open gparted:
sudo gparted
The reason being that there can be some problems with how the permissions are handed down when creating the partition. I then found that I could use this modified command to fix the problem:
sudo -H gparted
The documentation says this about -H.
The -H (HOME) option requests that the security policy set the HOME
environment variable to the home directory of the target user (root by
default) as specified by the password database. Depending on the
policy, this may be the default behavior.
The mount command I used was:
sudo mkdir /ssd
sudo mount /dev/sdc1 /ssd
It doesn't seem to output anything. The terminal just goes to the next line. However I can check inside of gparted to see that the drive has been mounted to the location I specified.
The error shows up when I try to create a new steam folder inside of the new drive:
Another thing that I noticed is that I am getting an error when launching gparted. An error comes up that says the following:
Unit -.mount does not exist, proceeding anyway.
I couldn't find a solution to this either and that might be related to why the drive is stuck.
partitioning mount gparted
edited Jan 11 at 22:01
Fabby
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
Can you give us the output of and the exactmountcommand you're using? Please edit your Q and then ping me @Fabby
– Fabby
Jan 11 at 21:24
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
try unmounting, thenchown szUserName:szUserName /ssdwhereszUsernameis the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.
– Fabby
Jan 11 at 22:03
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
1
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56
|
show 3 more comments
I just switched from Windows over to Ubuntu 18.04 and I am trying to get my internal drives set up. I have one SSD that has the os on it and a second larger SSD that I am trying to format.
To start I changed the format to ext4 using gparted. The drive formatted and then I was successfully able to mount the drive to a folder I had created. However this drive was in read-only mode.
In my research I found that I shouldn't be using the following command to open gparted:
sudo gparted
The reason being that there can be some problems with how the permissions are handed down when creating the partition. I then found that I could use this modified command to fix the problem:
sudo -H gparted
The documentation says this about -H.
The -H (HOME) option requests that the security policy set the HOME
environment variable to the home directory of the target user (root by
default) as specified by the password database. Depending on the
policy, this may be the default behavior.
The mount command I used was:
sudo mkdir /ssd
sudo mount /dev/sdc1 /ssd
It doesn't seem to output anything. The terminal just goes to the next line. However I can check inside of gparted to see that the drive has been mounted to the location I specified.
The error shows up when I try to create a new steam folder inside of the new drive:
Another thing that I noticed is that I am getting an error when launching gparted. An error comes up that says the following:
Unit -.mount does not exist, proceeding anyway.
I couldn't find a solution to this either and that might be related to why the drive is stuck.
partitioning mount gparted
edited Jan 11 at 22:01
Fabby
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
I just switched from Windows over to Ubuntu 18.04 and I am trying to get my internal drives set up. I have one SSD that has the os on it and a second larger SSD that I am trying to format.
To start I changed the format to ext4 using gparted. The drive formatted and then I was successfully able to mount the drive to a folder I had created. However this drive was in read-only mode.
In my research I found that I shouldn't be using the following command to open gparted:
sudo gparted
The reason being that there can be some problems with how the permissions are handed down when creating the partition. I then found that I could use this modified command to fix the problem:
sudo -H gparted
The documentation says this about -H.
The -H (HOME) option requests that the security policy set the HOME
environment variable to the home directory of the target user (root by
default) as specified by the password database. Depending on the
policy, this may be the default behavior.
The mount command I used was:
sudo mkdir /ssd
sudo mount /dev/sdc1 /ssd
It doesn't seem to output anything. The terminal just goes to the next line. However I can check inside of gparted to see that the drive has been mounted to the location I specified.
The error shows up when I try to create a new steam folder inside of the new drive:
Another thing that I noticed is that I am getting an error when launching gparted. An error comes up that says the following:
Unit -.mount does not exist, proceeding anyway.
I couldn't find a solution to this either and that might be related to why the drive is stuck.
partitioning mount gparted
partitioning mount gparted
edited Jan 11 at 22:01
Fabby
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
edited Jan 11 at 22:01
Fabby
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
edited Jan 11 at 22:01
Fabby
26.8k1360161
edited Jan 11 at 22:01
Fabby
26.8k1360161
edited Jan 11 at 22:01
Fabby
26.8k1360161
26.8k1360161
asked Jan 11 at 4:12
driftwood14driftwood14
62
asked Jan 11 at 4:12
driftwood14driftwood14
62
asked Jan 11 at 4:12
driftwood14driftwood14
62
62
Can you give us the output of and the exactmountcommand you're using? Please edit your Q and then ping me @Fabby
– Fabby
Jan 11 at 21:24
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
try unmounting, thenchown szUserName:szUserName /ssdwhereszUsernameis the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.
– Fabby
Jan 11 at 22:03
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
1
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56
|
show 3 more comments
Can you give us the output of and the exactmountcommand you're using? Please edit your Q and then ping me @Fabby
– Fabby
Jan 11 at 21:24
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
try unmounting, thenchown szUserName:szUserName /ssdwhereszUsernameis the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.
– Fabby
Jan 11 at 22:03
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
1
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56
Can you give us the output of and the exact
mount command you're using? Please edit your Q and then ping me @Fabby– Fabby
Jan 11 at 21:24
Can you give us the output of and the exact
mount command you're using? Please edit your Q and then ping me @Fabby– Fabby
Jan 11 at 21:24
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
try unmounting, then
chown szUserName:szUserName /ssd where szUsername is the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.– Fabby
Jan 11 at 22:03
try unmounting, then
chown szUserName:szUserName /ssd where szUsername is the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.– Fabby
Jan 11 at 22:03
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
1
1
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56
|
show 3 more comments
1 Answer
1
active
oldest
votes
I was able to solve the issue. I can write to the drive now.
I followed the directions on this wikihow of all things
Thanks @Fabby for the help.
answered Jan 12 at 4:01
driftwood14driftwood14
62
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108753%2fpartition-remains-as-read-only%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I was able to solve the issue. I can write to the drive now.
I followed the directions on this wikihow of all things
Thanks @Fabby for the help.
answered Jan 12 at 4:01
driftwood14driftwood14
62
add a comment |
I was able to solve the issue. I can write to the drive now.
I followed the directions on this wikihow of all things
Thanks @Fabby for the help.
answered Jan 12 at 4:01
driftwood14driftwood14
62
add a comment |
I was able to solve the issue. I can write to the drive now.
I followed the directions on this wikihow of all things
Thanks @Fabby for the help.
answered Jan 12 at 4:01
driftwood14driftwood14
62
I was able to solve the issue. I can write to the drive now.
I followed the directions on this wikihow of all things
Thanks @Fabby for the help.
answered Jan 12 at 4:01
driftwood14driftwood14
62
answered Jan 12 at 4:01
driftwood14driftwood14
62
answered Jan 12 at 4:01
driftwood14driftwood14
62
answered Jan 12 at 4:01
driftwood14driftwood14
62
62
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108753%2fpartition-remains-as-read-only%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you give us the output of and the exact
mountcommand you're using? Please edit your Q and then ping me @Fabby– Fabby
Jan 11 at 21:24
@Fabby I am tagging here because I am not sure if I can tag in the question or not.
– driftwood14
Jan 11 at 21:48
try unmounting, then
chown szUserName:szUserName /ssdwhereszUsernameis the user name of your user and then mount again. Ping me again in the comments whether that solves your problem or not.– Fabby
Jan 11 at 22:03
@Fabby Do I have to run that command with sudo? If I don't it says "operation not permitted"
– driftwood14
Jan 11 at 22:29
1
That leads to the same read only error after mounting and changing the permissions. Just to check that I entered the code right, if the username was bob I would enter sudo chown bob:bob /ssd?
– driftwood14
Jan 11 at 22:56