Services not Starting After Droplet Resize
I did a CPU/RAM resize on my Ubuntu 16.04 droplet after poweroff. The resize took around 10 min and after I powered it on I found that I was unable to SSH into the droplet.
I used the access console, and arrived at a prompt that says "Press Enter for maintenance (or press Control-D to continue". Pressing Enter allows me to access the terminal, but Ctrl+D will give an error message that says 'sulogin: cannot read /dev/tty1: Operation not permitted'.
When I check running services through 'service --status-all', I found that services that usually automatically start after reboot aren't running (they are inactive/dead). These include:
I checked systemctl is-enabled apache2, and the system confirms that the apache2 service is supposed to start on boot.
In terminal, I ran a reboot to see if the above services would automatically start again, but they did not.
Manually starting the services apache2 / mysql will allow me to access my webserver with no problems, but they would unexpectedly go down again after a few hours.
Manually starting the ssh service works, but accessing through putty gives me an error "Fatal Error: Server unexpectedly closed network connection". I didn't modify any of my SSH configuration files / keys / passwords. Note that this is not a "Connection refused" error, so I think the authentication was successful but
1) What is causing the services not to start at boot?
2) How do I check if boot / startup was completed, or if there were errors in starting some services?
3) What is causing the Fatal Error with SSH?
4) Is it possible that the file system was corrupted after power off? What error messages on boot would lead me to diagnose this? Would file system corruption cause all of the above issues?
Will be happy to provide logs / additional information. I'm not an expert with Ubuntu and would appreciate any help.