How to troubleshoot cause of read-only file system errors
I'm running Xubuntu off of a fairly new Samsung EVO 250GB SSD.
Recently my root file system has been going into read-only mode and I need help troubleshooting it.
These are all the errors (and many more, basiclly nothing that needs to write to the file system works)
mktemp: failed to create file via template ‘/tmp/david/virtualenvwrapper-initialize-hook-XXXXXXXXXX’: Read-only file system
touch: cannot touch ‘’: No such file or directory
ERROR: virtualenvwrapper could not create a temporary file name.
zsh: locking failed for /home/david/.zhistory: read-only file system: reading anyway
Here are some dmesg logs:
[264394.925883] EXT4-fs error (device sda7): ext4_mb_free_metadata:4588: group 100, block 3305968:Block already on to-be-freed list
[264394.925952] EXT4-fs error (device sda7) in ext4_free_blocks:4879: Journal has aborted
[264394.925958] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926012] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926061] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926104] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926146] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926154] EXT4-fs error (device sda7) in ext4_ext_remove_space:3048: Journal has aborted
[264394.926201] EXT4-fs error (device sda7) in ext4_ext_truncate:4669: Journal has aborted
[264394.926251] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926292] EXT4-fs error (device sda7) in ext4_truncate:3648: Journal has aborted
[264394.926335] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264483.167154] EXT4-fs error (device sda7): ext4_remount:4888: Abort forced by user
I can usually solve the problem by restarting a couple of times.
I need one of two things:
- Prove that the SSD is faulty so I can return it.
- Find the issue.
Also, I'm dual booting windows 10 on the SSD as well if that's relevant.
xubuntu filesystem ssd read-only
asked Sep 23 '15 at 9:50
davegridavegri
13628
add a comment |
I'm running Xubuntu off of a fairly new Samsung EVO 250GB SSD.
Recently my root file system has been going into read-only mode and I need help troubleshooting it.
These are all the errors (and many more, basiclly nothing that needs to write to the file system works)
mktemp: failed to create file via template ‘/tmp/david/virtualenvwrapper-initialize-hook-XXXXXXXXXX’: Read-only file system
touch: cannot touch ‘’: No such file or directory
ERROR: virtualenvwrapper could not create a temporary file name.
zsh: locking failed for /home/david/.zhistory: read-only file system: reading anyway
Here are some dmesg logs:
[264394.925883] EXT4-fs error (device sda7): ext4_mb_free_metadata:4588: group 100, block 3305968:Block already on to-be-freed list
[264394.925952] EXT4-fs error (device sda7) in ext4_free_blocks:4879: Journal has aborted
[264394.925958] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926012] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926061] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926104] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926146] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926154] EXT4-fs error (device sda7) in ext4_ext_remove_space:3048: Journal has aborted
[264394.926201] EXT4-fs error (device sda7) in ext4_ext_truncate:4669: Journal has aborted
[264394.926251] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926292] EXT4-fs error (device sda7) in ext4_truncate:3648: Journal has aborted
[264394.926335] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264483.167154] EXT4-fs error (device sda7): ext4_remount:4888: Abort forced by user
I can usually solve the problem by restarting a couple of times.
I need one of two things:
- Prove that the SSD is faulty so I can return it.
- Find the issue.
Also, I'm dual booting windows 10 on the SSD as well if that's relevant.
xubuntu filesystem ssd read-only
asked Sep 23 '15 at 9:50
davegridavegri
13628
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34
add a comment |
I'm running Xubuntu off of a fairly new Samsung EVO 250GB SSD.
Recently my root file system has been going into read-only mode and I need help troubleshooting it.
These are all the errors (and many more, basiclly nothing that needs to write to the file system works)
mktemp: failed to create file via template ‘/tmp/david/virtualenvwrapper-initialize-hook-XXXXXXXXXX’: Read-only file system
touch: cannot touch ‘’: No such file or directory
ERROR: virtualenvwrapper could not create a temporary file name.
zsh: locking failed for /home/david/.zhistory: read-only file system: reading anyway
Here are some dmesg logs:
[264394.925883] EXT4-fs error (device sda7): ext4_mb_free_metadata:4588: group 100, block 3305968:Block already on to-be-freed list
[264394.925952] EXT4-fs error (device sda7) in ext4_free_blocks:4879: Journal has aborted
[264394.925958] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926012] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926061] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926104] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926146] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926154] EXT4-fs error (device sda7) in ext4_ext_remove_space:3048: Journal has aborted
[264394.926201] EXT4-fs error (device sda7) in ext4_ext_truncate:4669: Journal has aborted
[264394.926251] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926292] EXT4-fs error (device sda7) in ext4_truncate:3648: Journal has aborted
[264394.926335] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264483.167154] EXT4-fs error (device sda7): ext4_remount:4888: Abort forced by user
I can usually solve the problem by restarting a couple of times.
I need one of two things:
- Prove that the SSD is faulty so I can return it.
- Find the issue.
Also, I'm dual booting windows 10 on the SSD as well if that's relevant.
xubuntu filesystem ssd read-only
asked Sep 23 '15 at 9:50
davegridavegri
13628
I'm running Xubuntu off of a fairly new Samsung EVO 250GB SSD.
Recently my root file system has been going into read-only mode and I need help troubleshooting it.
These are all the errors (and many more, basiclly nothing that needs to write to the file system works)
mktemp: failed to create file via template ‘/tmp/david/virtualenvwrapper-initialize-hook-XXXXXXXXXX’: Read-only file system
touch: cannot touch ‘’: No such file or directory
ERROR: virtualenvwrapper could not create a temporary file name.
zsh: locking failed for /home/david/.zhistory: read-only file system: reading anyway
Here are some dmesg logs:
[264394.925883] EXT4-fs error (device sda7): ext4_mb_free_metadata:4588: group 100, block 3305968:Block already on to-be-freed list
[264394.925952] EXT4-fs error (device sda7) in ext4_free_blocks:4879: Journal has aborted
[264394.925958] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926012] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926061] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926104] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926146] EXT4-fs error (device sda7): ext4_journal_check_start:56: Detected aborted journal
[264394.926154] EXT4-fs error (device sda7) in ext4_ext_remove_space:3048: Journal has aborted
[264394.926201] EXT4-fs error (device sda7) in ext4_ext_truncate:4669: Journal has aborted
[264394.926251] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264394.926292] EXT4-fs error (device sda7) in ext4_truncate:3648: Journal has aborted
[264394.926335] EXT4-fs error (device sda7) in ext4_reserve_inode_write:4752: Journal has aborted
[264483.167154] EXT4-fs error (device sda7): ext4_remount:4888: Abort forced by user
I can usually solve the problem by restarting a couple of times.
I need one of two things:
- Prove that the SSD is faulty so I can return it.
- Find the issue.
Also, I'm dual booting windows 10 on the SSD as well if that's relevant.
xubuntu filesystem ssd read-only
xubuntu filesystem ssd read-only
asked Sep 23 '15 at 9:50
davegridavegri
13628
asked Sep 23 '15 at 9:50
davegridavegri
13628
asked Sep 23 '15 at 9:50
davegridavegri
13628
asked Sep 23 '15 at 9:50
davegridavegri
13628
asked Sep 23 '15 at 9:50
davegridavegri
13628
13628
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34
add a comment |
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34
add a comment |
1 Answer
1
active
oldest
votes
When I was having this problem my issue was that the dual boot of windows which had access to the same drive was not shutting down fully - despite clicking on shut-down it was going into a type of sleep which kept an edit lock over the disk.
shutdown /s
From windows command prompt does a proper shutdown - and there's a tutorial here about how to turn of the Fast Startup option here:
https://www.howtogeek.com/349114/shutting-down-doesnt-fully-shut-down-windows-10-but-restarting-it-does/
answered Mar 16 at 21:37
kabdullakabdulla
1013
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%2f677422%2fhow-to-troubleshoot-cause-of-read-only-file-system-errors%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
When I was having this problem my issue was that the dual boot of windows which had access to the same drive was not shutting down fully - despite clicking on shut-down it was going into a type of sleep which kept an edit lock over the disk.
shutdown /s
From windows command prompt does a proper shutdown - and there's a tutorial here about how to turn of the Fast Startup option here:
https://www.howtogeek.com/349114/shutting-down-doesnt-fully-shut-down-windows-10-but-restarting-it-does/
answered Mar 16 at 21:37
kabdullakabdulla
1013
add a comment |
When I was having this problem my issue was that the dual boot of windows which had access to the same drive was not shutting down fully - despite clicking on shut-down it was going into a type of sleep which kept an edit lock over the disk.
shutdown /s
From windows command prompt does a proper shutdown - and there's a tutorial here about how to turn of the Fast Startup option here:
https://www.howtogeek.com/349114/shutting-down-doesnt-fully-shut-down-windows-10-but-restarting-it-does/
answered Mar 16 at 21:37
kabdullakabdulla
1013
add a comment |
When I was having this problem my issue was that the dual boot of windows which had access to the same drive was not shutting down fully - despite clicking on shut-down it was going into a type of sleep which kept an edit lock over the disk.
shutdown /s
From windows command prompt does a proper shutdown - and there's a tutorial here about how to turn of the Fast Startup option here:
https://www.howtogeek.com/349114/shutting-down-doesnt-fully-shut-down-windows-10-but-restarting-it-does/
answered Mar 16 at 21:37
kabdullakabdulla
1013
When I was having this problem my issue was that the dual boot of windows which had access to the same drive was not shutting down fully - despite clicking on shut-down it was going into a type of sleep which kept an edit lock over the disk.
shutdown /s
From windows command prompt does a proper shutdown - and there's a tutorial here about how to turn of the Fast Startup option here:
https://www.howtogeek.com/349114/shutting-down-doesnt-fully-shut-down-windows-10-but-restarting-it-does/
answered Mar 16 at 21:37
kabdullakabdulla
1013
edited Mar 16 at 22:11
answered Mar 16 at 21:37
kabdullakabdulla
1013
answered Mar 16 at 21:37
kabdullakabdulla
1013
answered Mar 16 at 21:37
kabdullakabdulla
1013
1013
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%2f677422%2fhow-to-troubleshoot-cause-of-read-only-file-system-errors%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
have the same issue with my Samsung EVO 250GB SSD. I've used it for a mongo database for 4 months.
– Stefan Rogin
Mar 22 '16 at 21:34