Question

File system went read only after adding ssh key

  • Posted on December 4, 2014
  • arthurswAsked by arthursw

I followed this guide to set up ssh key on my digital ocean droplet, but since I made step 4 my file system went read-only. I changed /etc/ssh/sshd_config from PermitRootLogin yes to PermitRootLogin without-password and then reload ssh; and when I logged back in, I had no writing rights anymore.

I can log in using ssh root@123.45.67.89 but it does not ask me for any password, and I can not modify any file.

Before doing this, I upgraded my ubuntu from 12.04 to 14.04, it asked me during the upgrade which setting did I want for PermitRootLogin and when I looked at /etc/ssh/sshd_config after the installation (and after adding my ssh key) it was set on PermitRootLogin yes.

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

After a Power cycle I had nothing anymore. I went to the Consol Access and I had to reboot. Then it asked me if I want to solve some problems. I said yes, and it solved them. Thanks!

Run this, and give me the output:

fsck -n

Also, if it comes up with errors, you have 2 choices, with choice 1 being:

  • Power down the system
  • From DO control panel, put system into recovery
  • boot the system
  • from web console, run “fsck -yf /dev/vda1”. If that fails, run “fsck -yf /dev/sda”
  • power down the machine after it completes
  • exit recovery mode
  • power system back up

Second choice is as follows:

  • Open up web console
  • reboot system
  • boot into single user mode
  • run fsck -r
  • reboot

This comment has been deleted