I update my droplet with pacman -Syu and rebooted it.
The droplet not startup. I connected via web console and I see errors:
systemd[99]: Failed to open serialization file: Read-only file system
systemd[1]: Failed to fully start up daemon: RemoteI/O error
[!!!!!!] Failed to start up manager, freezing.
systemd[1]: Freezing execution.
I ran fsck via the recovery but I not found error. The disk seen fine but the droplet not start up. please, help me.
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.
hey there, i had got the same issue as op however luckily, after hours and hours experimenting… i finally got my arch up and running now.
for some reason after upgrading the system, the systemd just can’t mount the /dev/vda1 correctly with write access.
so what i did is a bit hacky:
- shutdown your droplet
- boot from recovery iso, you can select this from recovery menu
- start your droplet and open console
- select 1 from menu to mount the disk
- select 5 to chroot into your arch
- move original /sbin/init, rename it as init.real:
mv /sbin/init /sbin/init.real - create your own “init” to mount the disk correctly, don’t forget to chmod +x it, here is the script:
#!/bin/sh
mount -o remount,rw /dev/vda1 /
exec init.real
at last shutdown your droplet and turn of recovery mode, and reboot it
hey there, i had got the same issue as op however luckily, after hours and hours experimenting… i finally got my arch up and running now.
for some reason after upgrading the system, the systemd just can’t mount the /dev/vda1 correctly with write access.
so what i did is a bit hacky:
- shutdown your droplet
- boot from recovery iso, you can select this from recovery menu
- start your droplet and open console
- select 1 from menu to mount the disk
- select 5 to chroot into your arch
- move original /sbin/init, rename it as init.real:
mv /sbin/init /sbin/init.real - create your own “init” to mount the disk correctly, don’t forget to chmod +x it, here is the script:
#!/bin/sh
mount -o remount,rw /dev/vda1 /
exec init.real
at last shutdown your droplet and turn of recovery mode, and reboot it
hey there, i had got the same issue as op however luckily, after hours and hours experimenting… i finally got my arch up and running now.
for some reason after upgrading the system, the systemd just can’t mount the /dev/vda1 correctly with write access.
so what i did is a bit hacky:
- shutdown your droplet
- boot from recovery iso, you can select this from recovery menu
- start your droplet and open console
- select 1 from menu to mount the disk
- select 5 to chroot into your arch
- move original /sbin/init, rename it as init.real:
mv /sbin/init /sbin/init.real - create your own “init” to mount the disk correctly, don’t forget to chmod +x it, here is the script:
#!/bin/sh
mount -o remount,rw /dev/vda1 /
exec init.real
at last shutdown your droplet and turn of recovery mode, and reboot it
Arch Linux is not supported by DigitalOcean as a droplet distribution anymore. I doubt you’ll get much help with this.
If you’re using “DigitalOcean Debian to Arch” on the droplet then ask for advice through the issues page perhaps.
This bit me too. I’m still digging into this, I’ll update if I figure this out.
@jahagirdarvs
@hatul I am facing the same issue.
@hatul Yeah, not what I wanted to hear, but I guess that’s pretty much it. Cheers.
@case I could not solve the problem. As I wrote above, I re-created droplet with DigitalOcean Debian to Arch.
Hey, I know this is an older thread, but I’m in the same position now after doing an update on my droplet (what a bad idea). So did anyone find any solution apart from pretty much starting from scratch with a new droplet as suggested above?
Thanks.
I created new droplet, installed Arhclinux with DigitalOcean Debian to Arch and transfered all files from old droplet.
Note: default mirror (http://mirrors.kernel.org/archlinux) contain defective packages, change to another mirror. Note 2: the script not define locale and it should cause problems. Set locale after the installaion.
@l4zmq2r @hatul I have the same problem, did you find any solution?