Related

Certbot unable to locate virtual host Question Question
Why my website down? SSH cannot be accessed Question Question

Question

How to Fix: "Failed to open serialization file readonly file system"

Posted December 1, 2019 3.5k views
Ubuntu 18.04

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?

Add a comment
jahagirdarvs
By:
jahagirdarvs

Related

Certbot unable to locate virtual host Question Question
Why my website down? SSH cannot be accessed Question Question
Add a comment
1 comment

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.

×
7 answers
ghostseven December 4, 2019

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.

Reply Report
ghostseven December 4, 2019

DO have not been overly helpful to be fair. I am however working on the problem and have made some progress. I had a backup from a week ago that I have restored to a new droplet. I have been working through the updates and have identified (for me at least) which update has caused this issue.

I updated the snapd package (snapd/bionic-updates 2.42.1+18.04 amd64 [upgradable from: 2.40+18.04]) and it replicated the fault. I am just in the process of booting the test droplet to remove this package and see what occurs. Hold this space and I will report back :)

Reply Report
ghostseven December 2, 2019

I am having the exact same issue after performing an update and upgrade. Attempting to boot the droplet using a recovery shell.

Edit: If i boot into recovery then, reboot and select boot from harddisk the droplet boots. Exact replication of above behaviour.

OS is Ubuntu 18.04.3

Reply Report
alexanderlndbrg December 3, 2019

Just wanted to chime in to say that I had the exact same issue right now. The recovery-reboot method worked for me as well. I’ve also created a ticket.

Reply Report
jahagirdarvs December 4, 2019

@ghostseven @alexanderlndbrg Did you get any resolution from DigitalOcean’s support staff?

In my case,
Once in a day someone responds, “Hey we checked your console. Everything is fine!”

My response of “That’s because it is booted in recovery mode. It does not work in normal mode” falls on deaf ears…

I have also posted to serverfault without any response https://serverfault.com/questions/994177/digital-ocean-failed-to-open-serialization-file-readonly-file-system-issue-u

Reply Report
jahagirdarvs December 4, 2019

@ghostseven Thanks a lot! Can you also file a report at https://bugs.launchpad.net/ubuntu

Reply Report
gerrard00 April 2, 2020

Any updates on this or at least a link to the Canonical bug?

Reply Report
  • dlbaldwin April 10, 2020

    @gerrard00 I’m on exactly the same page. I used to regularly update my droplet without any problems, but the snapd issue changed that. It sure would be nice to know when a fix is planned for release.

    Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help