Question
File system went read only after adding ssh key
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.
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.
×
I ran
dmesg | grep "EXT4-fs error"to see if I have any issues related to the filesystem / journaling system itself.It returned many times:
[68241.757233] EXT4-fs error (device vda): htree_dirblock_to_tree:892: inode #533953: block 2108070: comm updatedb.mlocat: bad entry in directory: rec_len is smaller than minimal - offset=0(0), inode=0, rec_len=0, name_len=0And when I run
sudo fsck -Af -M, it returnsUnable to resolve 'UUID=XYZ:root@DropletName:~# sudo fsck -Af -Mfsck from util-linux 2.20.1
fsck.ext4: Unable to resolve 'UUID=b96601ba-7d51-4c5f-bfe2-63815708aabd'
What can I do?