Linux ext4 partition keeps converting all files to read-only mode

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
0
down vote

favorite












I have installed Linux deepin os on my laptop which I have been using for the past 6 months now, the past two weeks,the computer slows down and when I save a file, I get and error Read-only file system. I have two ext4 partitions /dev/sda1(is bootable and has home partition) and /dev/sda3. It's affecting the two partitions.



I have been fixing this using this command as explained in this question.



$ sudo fsck.ext4 /dev/sda1


Here is a screenshot of the output when I run the above command.



enter image description here



This fixes the problem but it happens at least twice a day, affecting my work significantly. I need help fixing this issue permanently or something that will point the cause.







share|improve this question

















  • 1




    I'm assuming your ran this on unmounted partitions? How old is the disk?
    – Kusalananda
    Jul 28 at 7:06










  • Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
    – Ulrich Schwarz
    Jul 28 at 7:21










  • @Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
    – Joe Nyugoh
    Jul 29 at 18:45
















up vote
0
down vote

favorite












I have installed Linux deepin os on my laptop which I have been using for the past 6 months now, the past two weeks,the computer slows down and when I save a file, I get and error Read-only file system. I have two ext4 partitions /dev/sda1(is bootable and has home partition) and /dev/sda3. It's affecting the two partitions.



I have been fixing this using this command as explained in this question.



$ sudo fsck.ext4 /dev/sda1


Here is a screenshot of the output when I run the above command.



enter image description here



This fixes the problem but it happens at least twice a day, affecting my work significantly. I need help fixing this issue permanently or something that will point the cause.







share|improve this question

















  • 1




    I'm assuming your ran this on unmounted partitions? How old is the disk?
    – Kusalananda
    Jul 28 at 7:06










  • Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
    – Ulrich Schwarz
    Jul 28 at 7:21










  • @Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
    – Joe Nyugoh
    Jul 29 at 18:45












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have installed Linux deepin os on my laptop which I have been using for the past 6 months now, the past two weeks,the computer slows down and when I save a file, I get and error Read-only file system. I have two ext4 partitions /dev/sda1(is bootable and has home partition) and /dev/sda3. It's affecting the two partitions.



I have been fixing this using this command as explained in this question.



$ sudo fsck.ext4 /dev/sda1


Here is a screenshot of the output when I run the above command.



enter image description here



This fixes the problem but it happens at least twice a day, affecting my work significantly. I need help fixing this issue permanently or something that will point the cause.







share|improve this question













I have installed Linux deepin os on my laptop which I have been using for the past 6 months now, the past two weeks,the computer slows down and when I save a file, I get and error Read-only file system. I have two ext4 partitions /dev/sda1(is bootable and has home partition) and /dev/sda3. It's affecting the two partitions.



I have been fixing this using this command as explained in this question.



$ sudo fsck.ext4 /dev/sda1


Here is a screenshot of the output when I run the above command.



enter image description here



This fixes the problem but it happens at least twice a day, affecting my work significantly. I need help fixing this issue permanently or something that will point the cause.









share|improve this question












share|improve this question




share|improve this question








edited Jul 28 at 21:32









slm♦

232k65479649




232k65479649









asked Jul 28 at 6:55









Joe Nyugoh

11




11







  • 1




    I'm assuming your ran this on unmounted partitions? How old is the disk?
    – Kusalananda
    Jul 28 at 7:06










  • Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
    – Ulrich Schwarz
    Jul 28 at 7:21










  • @Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
    – Joe Nyugoh
    Jul 29 at 18:45












  • 1




    I'm assuming your ran this on unmounted partitions? How old is the disk?
    – Kusalananda
    Jul 28 at 7:06










  • Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
    – Ulrich Schwarz
    Jul 28 at 7:21










  • @Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
    – Joe Nyugoh
    Jul 29 at 18:45







1




1




I'm assuming your ran this on unmounted partitions? How old is the disk?
– Kusalananda
Jul 28 at 7:06




I'm assuming your ran this on unmounted partitions? How old is the disk?
– Kusalananda
Jul 28 at 7:06












Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
– Ulrich Schwarz
Jul 28 at 7:21




Could also be dodgy RAM, with the in-memory filesystem structures getting failures. Running memtest just in case might be a good idea. (It's a startup option on most Linux install media I've seen.)
– Ulrich Schwarz
Jul 28 at 7:21












@Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
– Joe Nyugoh
Jul 29 at 18:45




@Kusalananda, yes am running the command when unmounted. Am not sure how old the laptop is but can't be older than 4 years.
– Joe Nyugoh
Jul 29 at 18:45










1 Answer
1






active

oldest

votes

















up vote
3
down vote













The filesystem going readonly by itself is very likely the result of the filesystem driver encountering errors. You might see the errors=remount-ro option in the output of mount. It does that to protect the filesystem from further issues. (The alternatives are to continue and ignore the error, or to panic the system, see ext4(5)). You should probably see something about the error in dmesg.



If it happens repeatedly, it's an indication of the hardware going bad. Check at least the disk and memory, and make backups while you can.






share|improve this answer





















  • How do I get more information about the filesystem driver errors? Below is the output of dmesg
    – Joe Nyugoh
    Jul 29 at 19:30










  • joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
    – Joe Nyugoh
    Jul 29 at 19:34










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',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459003%2flinux-ext4-partition-keeps-converting-all-files-to-read-only-mode%23new-answer', 'question_page');

);

Post as a guest






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote













The filesystem going readonly by itself is very likely the result of the filesystem driver encountering errors. You might see the errors=remount-ro option in the output of mount. It does that to protect the filesystem from further issues. (The alternatives are to continue and ignore the error, or to panic the system, see ext4(5)). You should probably see something about the error in dmesg.



If it happens repeatedly, it's an indication of the hardware going bad. Check at least the disk and memory, and make backups while you can.






share|improve this answer





















  • How do I get more information about the filesystem driver errors? Below is the output of dmesg
    – Joe Nyugoh
    Jul 29 at 19:30










  • joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
    – Joe Nyugoh
    Jul 29 at 19:34














up vote
3
down vote













The filesystem going readonly by itself is very likely the result of the filesystem driver encountering errors. You might see the errors=remount-ro option in the output of mount. It does that to protect the filesystem from further issues. (The alternatives are to continue and ignore the error, or to panic the system, see ext4(5)). You should probably see something about the error in dmesg.



If it happens repeatedly, it's an indication of the hardware going bad. Check at least the disk and memory, and make backups while you can.






share|improve this answer





















  • How do I get more information about the filesystem driver errors? Below is the output of dmesg
    – Joe Nyugoh
    Jul 29 at 19:30










  • joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
    – Joe Nyugoh
    Jul 29 at 19:34












up vote
3
down vote










up vote
3
down vote









The filesystem going readonly by itself is very likely the result of the filesystem driver encountering errors. You might see the errors=remount-ro option in the output of mount. It does that to protect the filesystem from further issues. (The alternatives are to continue and ignore the error, or to panic the system, see ext4(5)). You should probably see something about the error in dmesg.



If it happens repeatedly, it's an indication of the hardware going bad. Check at least the disk and memory, and make backups while you can.






share|improve this answer













The filesystem going readonly by itself is very likely the result of the filesystem driver encountering errors. You might see the errors=remount-ro option in the output of mount. It does that to protect the filesystem from further issues. (The alternatives are to continue and ignore the error, or to panic the system, see ext4(5)). You should probably see something about the error in dmesg.



If it happens repeatedly, it's an indication of the hardware going bad. Check at least the disk and memory, and make backups while you can.







share|improve this answer













share|improve this answer



share|improve this answer











answered Jul 28 at 7:47









ilkkachu

47.3k668130




47.3k668130











  • How do I get more information about the filesystem driver errors? Below is the output of dmesg
    – Joe Nyugoh
    Jul 29 at 19:30










  • joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
    – Joe Nyugoh
    Jul 29 at 19:34
















  • How do I get more information about the filesystem driver errors? Below is the output of dmesg
    – Joe Nyugoh
    Jul 29 at 19:30










  • joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
    – Joe Nyugoh
    Jul 29 at 19:34















How do I get more information about the filesystem driver errors? Below is the output of dmesg
– Joe Nyugoh
Jul 29 at 19:30




How do I get more information about the filesystem driver errors? Below is the output of dmesg
– Joe Nyugoh
Jul 29 at 19:30












joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
– Joe Nyugoh
Jul 29 at 19:34




joe@jarvis  ~  dmesg | grep mount [ 5.306033] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 8.798523] EXT4-fs (sda1): re-mounted. Opts: data=ordered [ 45.261146] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 45.261199] partition /media/joe/Jarvis [8, 3] added, comm[1701]: mount
– Joe Nyugoh
Jul 29 at 19:34












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f459003%2flinux-ext4-partition-keeps-converting-all-files-to-read-only-mode%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?