NTFS volumes read-only since update
Since yesterdays update to my Ubuntu 18.04 desktop system, all the NTFS volumes have become read-only. I haven't had time to research this fully yet; just seeing if anyone else is having the same problem. I see many old threads on this topic, but my system has been running perfectly until yesterday and there seem to be no new posts.
Permissions on those volumes looks good, but attempting to delete files or folders from Nemo fails and using rm in terminal line gives the message "read-only file system".
The system dual-boots with Windows 10 (which I use only rarely) and Windows now won't start, which may or not be related.
mount ntfs
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
add a comment |
Since yesterdays update to my Ubuntu 18.04 desktop system, all the NTFS volumes have become read-only. I haven't had time to research this fully yet; just seeing if anyone else is having the same problem. I see many old threads on this topic, but my system has been running perfectly until yesterday and there seem to be no new posts.
Permissions on those volumes looks good, but attempting to delete files or folders from Nemo fails and using rm in terminal line gives the message "read-only file system".
The system dual-boots with Windows 10 (which I use only rarely) and Windows now won't start, which may or not be related.
mount ntfs
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
If would suggest scanning logs for when themountwas performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy thenumountthenmountvia terminal so you can see the error message on your terminal (instead of view/grep..)
– guiverc
Jan 19 at 23:19
add a comment |
Since yesterdays update to my Ubuntu 18.04 desktop system, all the NTFS volumes have become read-only. I haven't had time to research this fully yet; just seeing if anyone else is having the same problem. I see many old threads on this topic, but my system has been running perfectly until yesterday and there seem to be no new posts.
Permissions on those volumes looks good, but attempting to delete files or folders from Nemo fails and using rm in terminal line gives the message "read-only file system".
The system dual-boots with Windows 10 (which I use only rarely) and Windows now won't start, which may or not be related.
mount ntfs
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
Since yesterdays update to my Ubuntu 18.04 desktop system, all the NTFS volumes have become read-only. I haven't had time to research this fully yet; just seeing if anyone else is having the same problem. I see many old threads on this topic, but my system has been running perfectly until yesterday and there seem to be no new posts.
Permissions on those volumes looks good, but attempting to delete files or folders from Nemo fails and using rm in terminal line gives the message "read-only file system".
The system dual-boots with Windows 10 (which I use only rarely) and Windows now won't start, which may or not be related.
mount ntfs
mount ntfs
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
asked Jan 19 at 23:07
wurlyfanwurlyfan
165
165
If would suggest scanning logs for when themountwas performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy thenumountthenmountvia terminal so you can see the error message on your terminal (instead of view/grep..)
– guiverc
Jan 19 at 23:19
add a comment |
If would suggest scanning logs for when themountwas performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy thenumountthenmountvia terminal so you can see the error message on your terminal (instead of view/grep..)
– guiverc
Jan 19 at 23:19
If would suggest scanning logs for when the
mount was performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy then umount then mount via terminal so you can see the error message on your terminal (instead of view/grep..)– guiverc
Jan 19 at 23:19
If would suggest scanning logs for when the
mount was performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy then umount then mount via terminal so you can see the error message on your terminal (instead of view/grep..)– guiverc
Jan 19 at 23:19
add a comment |
1 Answer
1
active
oldest
votes
I had similar problem once. The NTFS partition was mounted read-only. The problem I had was that windows somehow mark the partition 'dirty'. Boot back to the windows and did a check disk and that fixed it.
answered Jan 19 at 23:10
GuangliangGuangliang
1013
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
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%2f1111236%2fntfs-volumes-read-only-since-update%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 had similar problem once. The NTFS partition was mounted read-only. The problem I had was that windows somehow mark the partition 'dirty'. Boot back to the windows and did a check disk and that fixed it.
answered Jan 19 at 23:10
GuangliangGuangliang
1013
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
add a comment |
I had similar problem once. The NTFS partition was mounted read-only. The problem I had was that windows somehow mark the partition 'dirty'. Boot back to the windows and did a check disk and that fixed it.
answered Jan 19 at 23:10
GuangliangGuangliang
1013
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
add a comment |
I had similar problem once. The NTFS partition was mounted read-only. The problem I had was that windows somehow mark the partition 'dirty'. Boot back to the windows and did a check disk and that fixed it.
answered Jan 19 at 23:10
GuangliangGuangliang
1013
I had similar problem once. The NTFS partition was mounted read-only. The problem I had was that windows somehow mark the partition 'dirty'. Boot back to the windows and did a check disk and that fixed it.
answered Jan 19 at 23:10
GuangliangGuangliang
1013
answered Jan 19 at 23:10
GuangliangGuangliang
1013
answered Jan 19 at 23:10
GuangliangGuangliang
1013
answered Jan 19 at 23:10
GuangliangGuangliang
1013
1013
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
add a comment |
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
Thanks for the response. I haven't booted into Windows for days (maybe even weeks) and Windows won't start at present, but I.ll follow up shortly.
– wurlyfan
Jan 19 at 23:19
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
You can download free and create a windows 10 installation usb stick (with a 16GB or bigger usb)..
– Guangliang
Jan 19 at 23:21
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
Thanks, it was dirty file systems, although why four NTFS file systems should become dirty at the same time beats me! Fixed with Windows install disk (to check and fix Windows volume) then used Windows to fix the other volumes.
– wurlyfan
Jan 20 at 19:49
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%2f1111236%2fntfs-volumes-read-only-since-update%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
If would suggest scanning logs for when the
mountwas performed, and you'll see the reason. As Guangliang has stated in his answer, I'd suspect a 'dirty' state too and thus fsck (file system check) should be performed. Since NTFS is a windows fs, I'd probably do it in windows too. But I would scan logs for the reason; or if you're lazy thenumountthenmountvia terminal so you can see the error message on your terminal (instead of view/grep..)– guiverc
Jan 19 at 23:19