Ext4 Error and disk remounted read-onlyDisk problems prevent me from booting, or set the disk to read-only....
Is creating your own "experiment" considered cheating during a physics exam?
Does a creature that is immune to a condition still make a saving throw?
Single Colour Mastermind Problem
If Earth is tilted, why is Polaris always above the same spot?
Why does nature favour the Laplacian?
Find the coordinate of two line segments that are perpendicular
Pressure to defend the relevance of one's area of mathematics
Where did the extra Pym particles come from in Endgame?
How to replace the "space symbol" (squat-u) in listings?
Minimum value of 4 digit number divided by sum of its digits
Multiple options for Pseudonyms
Is it cheaper to drop cargo drop than to land it?
Are Boeing 737-800’s grounded?
Why does the Betti number give the measure of k-dimensional holes?
When and why did journal article titles become descriptive, rather than creatively allusive?
Help, my Death Star suffers from Kessler syndrome!
What's the metal clinking sound at the end of credits in Avengers: Endgame?
Lock in SQL Server and Oracle
What gives an electron its charge?
A non-technological, repeating, visible object in the sky, holding its position in the sky for hours
Were there two appearances of Stan Lee?
How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?
Does jamais mean always or never in this context?
Why do Ichisongas hate elephants and hippos?
Ext4 Error and disk remounted read-only
Disk problems prevent me from booting, or set the disk to read-only. How do I fix the disk?Ext3 file system became read-only and server reboots spontaneoulsyHow do I create small disk image with large partitionsfsck.ext4 can't repair block far behind end of the file systemFilesystem errors when restoring many filesPartition Errors and Remounts Read-Only when Accessing Specific FileProcess mount is read onlyWhen is a file freed in an ext file system?I/O error after power failure, filesystem remounting as read-onlyCorrupt ext4 file system
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
0
Sometimes I have an error ext4 and my disk becomes read-only.
I can fix it with a reboot and fcsk /dev/sda2 but it keeps coming back...
Here are some dmesg :
[ 3160.692730] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 3631.408303] perf: interrupt took too long (3144 > 3136), lowering kernel.perf_event_max_sample_rate to 63500
[ 4143.729000] perf: interrupt took too long (3992 > 3930), lowering kernel.perf_event_max_sample_rate to 50000
[ 4770.574303] perf: interrupt took too long (5018 > 4990), lowering kernel.perf_event_max_sample_rate to 39750
[ 5334.077445] perf: interrupt took too long (6289 > 6272), lowering kernel.perf_event_max_sample_rate to 31750
[ 8241.921553] acer_wmi: Unknown function number - 8 - 1
[11370.110956] perf: interrupt took too long (7918 > 7861), lowering kernel.perf_event_max_sample_rate to 25250
[11484.098212] acer_wmi: Unknown function number - 8 - 0
[11875.568601] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.575273] Aborting journal on device sda2-8.
[11875.575537] EXT4-fs error (device sda2) in ext4_da_write_end:3209: IO failure
[11875.575976] EXT4-fs (sda2): Remounting filesystem read-only
[11875.576792] EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
[11875.577612] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.583499] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.832886] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11899.686408] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686483] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686587] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686656] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686719] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686781] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686844] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686938] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686999] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.687084] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
And my /etc/fstab :
UUID=9c882ba5-b980-4f7d-dd02-cd0a1831ab1a / ext4 errors=remount-ro 0 1
UUID=0E37-D0A2 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
Should I remove or change remount-ro in fstab and ignore this error ? How to fix / avoid this error ?
linux filesystems hard-disk ext4 fstab
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
add a comment |
0
Sometimes I have an error ext4 and my disk becomes read-only.
I can fix it with a reboot and fcsk /dev/sda2 but it keeps coming back...
Here are some dmesg :
[ 3160.692730] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 3631.408303] perf: interrupt took too long (3144 > 3136), lowering kernel.perf_event_max_sample_rate to 63500
[ 4143.729000] perf: interrupt took too long (3992 > 3930), lowering kernel.perf_event_max_sample_rate to 50000
[ 4770.574303] perf: interrupt took too long (5018 > 4990), lowering kernel.perf_event_max_sample_rate to 39750
[ 5334.077445] perf: interrupt took too long (6289 > 6272), lowering kernel.perf_event_max_sample_rate to 31750
[ 8241.921553] acer_wmi: Unknown function number - 8 - 1
[11370.110956] perf: interrupt took too long (7918 > 7861), lowering kernel.perf_event_max_sample_rate to 25250
[11484.098212] acer_wmi: Unknown function number - 8 - 0
[11875.568601] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.575273] Aborting journal on device sda2-8.
[11875.575537] EXT4-fs error (device sda2) in ext4_da_write_end:3209: IO failure
[11875.575976] EXT4-fs (sda2): Remounting filesystem read-only
[11875.576792] EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
[11875.577612] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.583499] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.832886] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11899.686408] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686483] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686587] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686656] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686719] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686781] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686844] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686938] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686999] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.687084] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
And my /etc/fstab :
UUID=9c882ba5-b980-4f7d-dd02-cd0a1831ab1a / ext4 errors=remount-ro 0 1
UUID=0E37-D0A2 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
Should I remove or change remount-ro in fstab and ignore this error ? How to fix / avoid this error ?
linux filesystems hard-disk ext4 fstab
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
2
If this keeps happening even after afsckand a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.
– wurtel
Jan 14 at 9:01
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
2
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
You can delete read-only bit viahdparm:hdparm -r0 /dev/sda
– PersianGulf
Jan 22 at 8:21
add a comment |
0
0
0
Sometimes I have an error ext4 and my disk becomes read-only.
I can fix it with a reboot and fcsk /dev/sda2 but it keeps coming back...
Here are some dmesg :
[ 3160.692730] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 3631.408303] perf: interrupt took too long (3144 > 3136), lowering kernel.perf_event_max_sample_rate to 63500
[ 4143.729000] perf: interrupt took too long (3992 > 3930), lowering kernel.perf_event_max_sample_rate to 50000
[ 4770.574303] perf: interrupt took too long (5018 > 4990), lowering kernel.perf_event_max_sample_rate to 39750
[ 5334.077445] perf: interrupt took too long (6289 > 6272), lowering kernel.perf_event_max_sample_rate to 31750
[ 8241.921553] acer_wmi: Unknown function number - 8 - 1
[11370.110956] perf: interrupt took too long (7918 > 7861), lowering kernel.perf_event_max_sample_rate to 25250
[11484.098212] acer_wmi: Unknown function number - 8 - 0
[11875.568601] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.575273] Aborting journal on device sda2-8.
[11875.575537] EXT4-fs error (device sda2) in ext4_da_write_end:3209: IO failure
[11875.575976] EXT4-fs (sda2): Remounting filesystem read-only
[11875.576792] EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
[11875.577612] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.583499] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.832886] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11899.686408] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686483] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686587] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686656] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686719] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686781] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686844] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686938] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686999] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.687084] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
And my /etc/fstab :
UUID=9c882ba5-b980-4f7d-dd02-cd0a1831ab1a / ext4 errors=remount-ro 0 1
UUID=0E37-D0A2 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
Should I remove or change remount-ro in fstab and ignore this error ? How to fix / avoid this error ?
linux filesystems hard-disk ext4 fstab
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
Sometimes I have an error ext4 and my disk becomes read-only.
I can fix it with a reboot and fcsk /dev/sda2 but it keeps coming back...
Here are some dmesg :
[ 3160.692730] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 3631.408303] perf: interrupt took too long (3144 > 3136), lowering kernel.perf_event_max_sample_rate to 63500
[ 4143.729000] perf: interrupt took too long (3992 > 3930), lowering kernel.perf_event_max_sample_rate to 50000
[ 4770.574303] perf: interrupt took too long (5018 > 4990), lowering kernel.perf_event_max_sample_rate to 39750
[ 5334.077445] perf: interrupt took too long (6289 > 6272), lowering kernel.perf_event_max_sample_rate to 31750
[ 8241.921553] acer_wmi: Unknown function number - 8 - 1
[11370.110956] perf: interrupt took too long (7918 > 7861), lowering kernel.perf_event_max_sample_rate to 25250
[11484.098212] acer_wmi: Unknown function number - 8 - 0
[11875.568601] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.575273] Aborting journal on device sda2-8.
[11875.575537] EXT4-fs error (device sda2) in ext4_da_write_end:3209: IO failure
[11875.575976] EXT4-fs (sda2): Remounting filesystem read-only
[11875.576792] EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
[11875.577612] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.583499] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.832886] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11899.686408] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686483] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686587] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686656] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686719] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686781] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686844] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686938] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686999] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.687084] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
And my /etc/fstab :
UUID=9c882ba5-b980-4f7d-dd02-cd0a1831ab1a / ext4 errors=remount-ro 0 1
UUID=0E37-D0A2 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
Should I remove or change remount-ro in fstab and ignore this error ? How to fix / avoid this error ?
linux filesystems hard-disk ext4 fstab
linux filesystems hard-disk ext4 fstab
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
asked Jan 13 at 23:57
bob dylanbob dylan
5041618
5041618
2
If this keeps happening even after afsckand a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.
– wurtel
Jan 14 at 9:01
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
2
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
You can delete read-only bit viahdparm:hdparm -r0 /dev/sda
– PersianGulf
Jan 22 at 8:21
add a comment |
2
If this keeps happening even after afsckand a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.
– wurtel
Jan 14 at 9:01
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
2
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
You can delete read-only bit viahdparm:hdparm -r0 /dev/sda
– PersianGulf
Jan 22 at 8:21
2
2
If this keeps happening even after a
fsck and a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.– wurtel
Jan 14 at 9:01
If this keeps happening even after a
fsck and a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.– wurtel
Jan 14 at 9:01
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
2
2
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
You can delete read-only bit via
hdparm : hdparm -r0 /dev/sda– PersianGulf
Jan 22 at 8:21
You can delete read-only bit via
hdparm : hdparm -r0 /dev/sda– PersianGulf
Jan 22 at 8:21
add a comment |
1 Answer
1
active
oldest
votes
0
Can you check your disk for bad sectors or bad blocks? you can use badblocks or smartctl command to check in linux, I think bad disk is only reason for your issue.
Hope it will help.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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');
});
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%2funix.stackexchange.com%2fquestions%2f494322%2fext4-error-and-disk-remounted-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
0
Can you check your disk for bad sectors or bad blocks? you can use badblocks or smartctl command to check in linux, I think bad disk is only reason for your issue.
Hope it will help.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
0
Can you check your disk for bad sectors or bad blocks? you can use badblocks or smartctl command to check in linux, I think bad disk is only reason for your issue.
Hope it will help.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
0
0
0
Can you check your disk for bad sectors or bad blocks? you can use badblocks or smartctl command to check in linux, I think bad disk is only reason for your issue.
Hope it will help.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Can you check your disk for bad sectors or bad blocks? you can use badblocks or smartctl command to check in linux, I think bad disk is only reason for your issue.
Hope it will help.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 22 mins ago
asktyagiasktyagi
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 22 mins ago
asktyagiasktyagi
11
answered 22 mins ago
asktyagiasktyagi
11
11
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asktyagi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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');
});
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%2funix.stackexchange.com%2fquestions%2f494322%2fext4-error-and-disk-remounted-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
2
If this keeps happening even after a
fsckand a reboot, then something is corrupting the data in your filesystem. It may be a faulty disk (is it SSD? with a normal disk you'd get more errors...) or maybe your system has bad memory where memory is being corrupted. Either way, ignoring such errors is a recipe to completely destroy your data.– wurtel
Jan 14 at 9:01
ssd on a laptop ~6 months old
– bob dylan
Jan 14 at 12:14
2
Another possible cause is bad RAM - the buffer for a particular part of the ext4 FS is likely to end up in a similar place, and if the underlying RAM is bad, it can get corrupted. I had a similar case about a year ago (though other effects, not the FS), and it was hard to diagnose - memtest86+ didn't find errors. Changing the RAM solved it. And sometimes laptops get used parts like RAM, even if sold "new"...
– dirkt
Jan 20 at 13:11
You can delete read-only bit via
hdparm:hdparm -r0 /dev/sda– PersianGulf
Jan 22 at 8:21