Question
How to Fix: "Failed to open serialization file readonly file system"
- Posted on December 1, 2019
- Ubuntu 18.04
Asked by jahagirdarvs
Hi, I performed apt update +upgrade and rebooted the machine when prompted to do so. Now my droplet fails to boot and gives a message of “Failed to open serialization file readonly file system” Is there any guidance on how to resolve this issue?
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Ok so after running up a new droplet with my week old backup and updating to the point that it broke as described. I identified that it was the snapd package (snapd/bionic-updates 2.42.1+18.04 amd64 [upgradable from: 2.40+18.04]) that caused the break.
I then booted via the recovery console and removed the snapd package. I then shutdown and switched back to booting via the standard method and the test system is now working as expected.
I am now going to fully update the test system and reboot.
If this works I will replicate this to my live system.
Edit: This has worked and I have replicated to live system and all is working. The ‘snapd’ package was the issue for me, once removed all was good.
It worked for me too! thanks a lot!!!
Uninstalling snap solved my problem as well. I’m going to upgrade to a newer version of Ubuntu to see if this problem persists there.