Results 1 to 2 of 2

Thread: Solving "Read Only FileSystem" problem in Ubuntu 19.04 which occurs once a week.

  1. #1
    Join Date
    Dec 2018
    Beans
    17

    Solving "Read Only FileSystem" problem in Ubuntu 19.04 which occurs once a week.

    I alway keep my Laptop OSes update. I am a dual boot user (Windows 10 Pro & Ubuntu 1904).
    Windows is as always had no problem but in Ubuntu I run into different kinds problem everyday.

    One big problem is FSCK and File System being Readonly.

    How to maintain this distro? Did I made a wrong decision choosing a non-LTS version?
    I really like to use non-LTS version because of features and speed improvemnt. Apart from this, this distro has always disappointed to me.

    I have 64GB pendrive dedicated for this recurring issue. What i do is, I live boot 19.04 > Try without installing > Open Gparted > Select / and home partition leaving swap partition alone > Choose Check disk > Run.

    This will solve the problem for a while and that's it. A week after, again the loop of "Read Only FileSystem and FSCK" circulates.

    #SaveMe #EnlightenMe

  2. #2
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    Hidden!
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Solving "Read Only FileSystem" problem in Ubuntu 19.04 which occurs once a week.

    File systems get mounted read-only when there is corruption to it. That should never happen. EVER.

    So you have some sort of issue, major issue, that will cause data loss. It needs to be fixed.
    Never just power off any Unix computer. Always shut it down. ALWAYS.

    Never let Windows open any Linux file systems and not close them cleanly. Windows likes to leave file systems open between "boots."

    Check the SMART data for the storage device. I would use smartctl. Look at the raw data. To my knowledge, the GUI tools don't show the raw data.

    Check that the cabling to the storage is tight and can't become loose.

    Using gparted seems like the hard way for something like running fsck. I would just open a terminal and run fsck on the partition from the "Live Boot" environment.

    File systems that have been around for 5+ yrs don't have corruption issues unless you are using them in a way they recommend against. If you are using ext4, there hasn't been any file corruption issues in released versions about 10 yrs. LTS or not, it doesn't matter. If you are using BTRFS, there are some specific use cases which can be problematic. Do some research to see if your use falls into the sort with issues. For example, using BTRFS with virtual machines under some specific use-cases can be a problem.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •