Recover a Digital Ocean server. NodeJS and postgres are used. May need to recover data from a non-running postgres server.
Budget: £20 – £36 GBP
The server has been restarted and since then fails to boot. The issue is very likely due to the code being build to run on an older droplet/server/os and digital ocean automatically updated this to the latest version, causing incompatibility issue with the filesystem, now can't find the right files to book successfully. Here is a message from their support:
I understand that you are not able to connect to the Droplet. The Droplet appears to be stuck during the boot process, halting with the following error: 'kernel panic - not syncing: Attempted to kill init!'.
The init process ( binary ) is called by the kernel to pass control into managing the system above the kernel. The error shown indicates that the system has a bad environment. Any search for “attempted to kill init” or “missing /sbin/init” will bring up many threads related to the scenarios associated with this.
The Droplet boots up properly, and the system passes control to the boot loader. This finds the kernel, which loads and then attempts to kick off the init system; the first process on the system that finishes the boot up. In this situation, the init binary is not working or is corrupted. The only way to recover this in place would be to ensure that:
1) the Droplet’s filesystem is properly intact.
2) the init binary is properly installed
3) the grub legacy or grub 2 (whichever applies) correctly references init.
On many modern systems, this is called systemd, but older systems may be different. Issues can be caused by file system problems, bad updates, or broken grub configurations/updates. There isn't any action on the platform that can resolve this case.
I understand that you are not able to connect to the Droplet. The Droplet appears to be stuck during the boot process, halting with the following error: 'kernel panic - not syncing: Attempted to kill init!'.
The init process ( binary ) is called by the kernel to pass control into managing the system above the kernel. The error shown indicates that the system has a bad environment. Any search for “attempted to kill init” or “missing /sbin/init” will bring up many threads related to the scenarios associated with this.
The Droplet boots up properly, and the system passes control to the boot loader. This finds the kernel, which loads and then attempts to kick off the init system; the first process on the system that finishes the boot up. In this situation, the init binary is not working or is corrupted. The only way to recover this in place would be to ensure that:
1) the Droplet’s filesystem is properly intact.
2) the init binary is properly installed
3) the grub legacy or grub 2 (whichever applies) correctly references init.
On many modern systems, this is called systemd, but older systems may be different. Issues can be caused by file system problems, bad updates, or broken grub configurations/updates. There isn't any action on the platform that can resolve this case.