For the second time in 3 months for vm went down - a fsck was necessary. No warning. Just down.
Has this happened to anyone else? What do you do to mitigate the problem? Has support been helpful?
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!
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.
ray: have you opened up a support ticket?
Been experiencing the same thing, only thing I can pin it down to is a lot of read/writes, exact same operations I carry out daily on multiple VPS machines with other companies and my own servers. This is the second time it’s happened in a month so at least I have been backing up daily just in case. I’ve done a lot of sysadmin work and development and this isn’t normal, there’s nothing that should’ve caused the disk to remount itself as read only.
Here is a follow-up - it may be a little long - maybe it will help others make informed decisions regarding using DO or VMs in general. <br> <br>So, ultimately, at the end of the day, my server became hosed and I was forced to provision another one to bring my app back up. It was down for 16*+ hours. We (the owner who pays me) got 80 bucks to compensate and some friendly guesses regarding what might of happened - ‘probably because I had shut down improperly’ - unlikely because I simply had not shutdown. More likely, after doing some research, the need for fsck was caused by faulty (or faltering) hardware - or faulty disk mounting (of SSDs). Would I bet my life on it? No. They did mention no others had experienced the same problem - which would blow that theory out of the water. Which is interesting since they have a kernel mode specifically for booting and running fsck. <br> <br>In any case this was the second time in 3 months that my app was left down. I’ve been running this same app for years without issues both on hardware(a mac mini which had a hybrid persistance hd/ssd, which I do miss sometimes) and on other VMs. <br> <br>I’ve moved my app server to Linode - leaving my asset host in place (which thank goodness also had backups from the server that was hosed). I should have done this before to mitigate risk anyway. <br> <br>So my lesson, learned: <br>1) Make damn sure you are making backups. Do them yourself the old fashioned cron/rsync way. Use 2+ DCs. (yea, I had done this) <br>2) Have a fallback. Like I set I got set up in Linode - and kept my DO asset host/backup andI might come back someday and setup an app server again - and fail over to it if Linode craps out <br>4) Experiment with ‘managed’ plans. It might be worth it. It might have helped in this case <br>5) Reboot and run fsck periodically - investigate what it finds, examining specifically for possible faulty sectors/drives/mounts <br> <br>My theory: SSDs are awesome. But may not be ideal for servers (that write often). <br> <br>I won’t be severing ties completely with DO, but I won’t be recommending them either. <br> <br>Hope that helps someone. <br> <br>Paul <br>