Why is my Droplet booting in Read Only mode?

If your Droplet’s filesystem is booting in a read-only state, you can review the Droplet’s system or kernel logs for any details on what may have triggered this state.

You can find the system logs in the following locations:

Operating System Log Location
Debian and Ubuntu /var/log/syslog
Fedora or CentOS /var/log/messages

To view the logs, open the file in your preferred text editor. For example, to view the system log of an Ubuntu system using the nano text editor, run:

nano /var/log/syslog

If your Droplet is configured to capture kernel logs, you can review kernel logs by opening the /var/log/kern.log file in a text editor.

There are many possible causes for this problem, including file system corruption. If you suspect file system corruption, you can run a File System Check (FSCK) and attempt to recover the files.

Use recovery mode to access Droplets that fail to boot up or have system problems.
If you lost your Droplet’s SSH key or root password, reset the Droplet’s root password in the control panel. You can use the Recovery Console to regain access to the Droplet’s SSH configuration.
You may be receiving this error for various reasons, including a missing SSH key or incorrect password.