Score:0

fsck.ext4 does not fix file system problems entirely

us flag

every now and then I fall into emergency mode and have to use command below to recover ubuntu:

fsck.ext4 /dev/sda3/

it works as expected and recover ubuntu. However, after using ubuntu once or twice and after restarting OS, I have to run fsck again. And it is also causing some problems when I'm using OS for example: read-write are too slow on HDD and all of a sudden everything turns to Read-only file system and get this error in terminal:

bash: /home/foo/.bashhub//log.txt: Read-only file system

and this happens all over the file-system for example can not save my code even. What I really want to know what is the cure even if it solves by changing HDD.

guiverc avatar
cn flag
Check the health of your hardware... A random system flipping to RO can occur (bad power, fridge/microwave etc drawing power & your line filters didn't cope well) but regular issues is a symptom of a problem. You can check the health of your drives (https://help.ubuntu.com/community/Smartmontools) but it's not the only cause...
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.