Results 1 to 5 of 5

Thread: Inherited Ubuntu Server Not able to boot

  1. #1
    Join Date
    Oct 2018

    Inherited Ubuntu Server Not able to boot

    I am having a critical issue with one of our Ubuntu Servers that is pretty old now. I want to say this is a ver. 16x Server.
    Has been running for years without issue. Routine reboot gave the below errors:

    run-init: /sbin/init: No such file or directory
    Target filesystem doesn't have requested /sbin/init.
    run-init: /sbin/init: No such file or directory
    run-init: /etc/init: Permission denied
    run-init: /bin/init: No such file or directory
    /bin/sh: 0: Can't open ro
    [ 17.445318] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
    [ 17.445318]

    I have limited information on this box as far as past in concerned. It runs as a VM on Hyper-V and rely on it heavily for redmine and Docker.
    I am at a loss as far as how to get it too boot back up. Please help. Thank you.

    Some notes on the box:

    If i press "e" when grub loads and this is the linux section:

    linux /vmlinuz-3.8.0-34-generic root=/dev/mapper/docker--a-root ro

  2. #2
    Join Date
    Oct 2018

    Re: Inherited Ubuntu Server Not able to boot

    I have successfully loaded a 16x server live .iso to get into "Repair broken system"
    Changed the resolv.config to hit the outside world
    i have also changed the repo's to point to the correct legacy repositories

    i can:
    Sudo apt-get update successfully

    what i cant do and what i think will fix the issue:

    sudo apt-get install init
    I get a "unable to locate package"

    im assuming i need to mount /dev/sda1 /mnt
    and sudo chroot /mnt

    but if i try to chroot into /mnt i get
    failed to run command ‘/bin/bash’: No such file or directory

  3. #3
    Join Date
    Nov 2009
    Mataro, Spain
    Ubuntu 14.04 Trusty Tahr

    Re: Inherited Ubuntu Server Not able to boot

    1. What do you mean with legacy repositories? Ubuntu 16.04 LTS is still in full support (until Apr 2021) so you can use the standard repos. Please be careful when changing repos especially when that step was not needed.

    2. You can try to boot it in recovery mode without any CD/DVD. When booting it up it will show the grub menu shortly. Select the recovery mode option and boot it. During the process it will show you small menu where you can select to activate networking (otherwise the recovery mode will have no network active), and then after that go to "drop to root shell".

    Once in the shell you can check if those directories mentioned really exist or not (/sbin/init, /etc/init, /bin/init).
    Ubuntu 14.04 LTS 64bit & Windows 10 Pro 64bit

  4. #4
    Join Date
    Mar 2010
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Inherited Ubuntu Server Not able to boot

    I used to run a redmine server. Never touched hyper-v or docker.

    What level are your skills?
    What do the system logs show?
    When you say you did a chroot, please be exact. To do it correctly, there are about 6 steps.

    To see which release is installed, look at /etc/lsb-release. The answer is important.

  5. #5
    Join Date
    Jun 2009
    SW Forida

    Re: Inherited Ubuntu Server Not able to boot

    linux /vmlinuz-3.8.0-34-generic root=/dev/mapper/docker--a-root ro
    kernel 3.8 was standard with Raring, but may have been one of the updates to 12.04, but do not remember or have notes.
    13.04 Raring Ringtail 18 April 2013 October 2014 3.8
    But both 12.04 & 13.04 are EOF - end of life.
    Or backup, and new install will be required.
    For more info on UEFI boot install & repair - Regularly Updated :
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts