Steps To Fix Ubuntu Read-Only Boot File System

Over the past few weeks, several readers have reported to us that they have experienced booting a read-only ubuntu file system.

I upgraded to Ubuntu Desktop (although I use it pretty much like any server) 14.04 to 16.04 directly via ssh. After shutting down and restarting, the file system boots in read-only mode.

[email protected]:/# binds to en withtouch: 'a' cannot touch system: read-only initiations

ubuntu read only file system boot

I’ve tried mount -o remount,rw / all but the output of mount: can't explore UUID=/dev/sda1. I think the UUID says /dev/sda1 has changed. That’s all /etc/fstab.

[email protected]:/# Cat /etc/fstab# /etc/fstab: Fixed filesystem info.## Use 'blkid' to display the generic unique Equipment; identifier# Generally this can be used with UUID= as a slightly more reliable way to name devices.# The fact is that this works both when creating and deleting disks. See fstab(5).##  >   # / seemed to be on To /dev/sda1 when installedUUID=/dev/sda1 - error ext4=remount-ro null 1# UUID=643d9cab-177e-4eee-a52f-224ebf0bc405 / ext4-error=remount-ro 3 1# swap was on /dev/sda5 during installationUUID=481bc70a-eb80-4040-93a1-696c46faa638 no exchange 0

I think I could comment out the UUID=/dev/sda1 line,and then comment out the UUID=643d9cab- line just below it, but since the root file was mounted read-only, I couldn’t. I know if this will teach you, but here is the first message from the core.

ubuntu read only file system boot

[email protected]:/#mount[dmesg|grep 1.794106] (sda1): ext4-fs filesystem mounted in collated mode. (Zero)[Options: 5.675605] systemd[1]: Sets an automatic mount point for any executable file format on the file system.[19.677056] cgroup: new mounts, options probably don't match existing ones, superblock will be ignored

How can I solve this problem with the process? I’m trying to fix this via ssh, let us know if I need physical access to the machine.

[email protected]:~$ sudo blkid/dev/sda1: UUID="643d9cab-177e-4eee-a52f-224ebf0bc405" TYPE="ext4" PARTUUID="0000e118-01"/dev/sda5: UUID="481bc70a-eb80-4040-93a1-696c46faa638" TYPE="swap" PARTUUID="0000e118-05"`

Today I did an unwanted upgrade from an Ubuntu 14.04 LTS server to 16.04 LTS, and when it rebooted, I started getting “Original read-only system errors” on the base partition.

Here’s how I researched and solved some problems, including the list all the websites I found that really helped you.

Have You Run Out Of Disk Space?

I wasn’t sure if the questionable installation had failed or if it was dangerous because I was running out of space on the CD. Then I first searched and found that it didn’t:

Is The Hard Disk In Good Condition?

Good then I used fsck to check if the partition is correct. It was the helpdesk (fuh):

Is It Easy To Customize?

Since the partition is fine, I wanted to check that the disk configuration information is correct. Then I asked to view the file entry To:

The issue seems to be that an update changed a specific configuration to use a UUID:

So, of course, the question was, is UUID correct? So I checked the language which was uuid /dev/vda1:

Let’s Fix This!

Since everything used to work on the drive specified as /dev/vda1 and not as UUID, I decided to just change the fstab file, but it’s done:

Of course, the whole problem is that the system informationstupid read-only, so I’ll update the kernel file in the morning.

Mount Drive

Again, since everything seemed to work fine and it wasn’t a filesystem violation, I figured I should just remount the drive with a different ID:

Turn Off And On Again

And now I have a real mounted read-write root partition.


  • Upgrading to version 16.04 LTS causes the file system to be readable and not displayed.
  • How do I change the /etc/fstab desktop to read-only on startup?
  • What is the correct fstab line for the main filesystem in 16 ubuntu.04?
  • -dfFile System Used Blocks 1K Available Usage % Installed/dev/vda1 61796348 14439820 44194416 76% /
    - sudo /dev/vda1fsck fsck from util-linux 2.27.1e2fsck 1.42.13 (May 17, 2015)DOROOT: cleaning, 289048/3932160 computer data, 11328157/15728640 blocks
    # / was at the time of /dev/vda1 when installedUUID=815063a9-c956-44a6-ab11-05e1d0bb3a58/ext4-error=remount-ro 1
     0 - check vii -l /dev/disk/by-uuid/ | grep vda1
    code>lrwxrwxrwx 1 root 1 root0 on October day 88f2ec31-89b7-4164-8fb8-c7736b549505 04:26 -> ../../vda1
    Failed to create info /root/free.nano: read-only file systemIt takes a long time to save/load search history or other cursor locations.

    Ubuntu Systemu Plikow Tylko Do Odczytu
    Ubuntu Skrivskyddad Uppstart Av Filsystemet
    Ubuntu Schreibgeschutztes Dateisystem Booten
    Ubuntu Zagruzka Fajlovoj Sistemy Tolko Dlya Chteniya
    Inicializacao Do Sistema De Arquivos Somente Leitura Do Ubuntu
    Ubuntu Avvio Del File System Di Sola Lettura
    우분투 읽기 전용 파일 시스템 부팅
    Arranque Del Sistema De Archivos De Solo Lectura De Ubuntu
    Ubuntu Alleen Lezen Bestandssysteem Opstarten
    Demarrage Du Systeme De Fichiers En Lecture Seule Ubuntu