Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Cloudron install Ubuntu 20.04 "init script failed"

Cloudron install Ubuntu 20.04 "init script failed"

Scheduled Pinned Locked Moved Solved Support
installationgrublxc
6 Posts 3 Posters 1.3k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • l0u1sgL Offline
    l0u1sgL Offline
    l0u1sg
    wrote on last edited by girish
    #1

    Hello,

    I tried several times to install Cloudron on my VPS running Ubuntu 20.04 but I'm always stuck at the installation stage. Apparently this is a problem with GRUB. Here are the installation logs

    Unpacking libefiboot1:amd64 (37-2ubuntu2.2) ...
    Selecting previously unselected package grub-common.
    Preparing to unpack .../grub-common_2.04-1ubuntu26.12_amd64.deb ...
    Unpacking grub-common (2.04-1ubuntu26.12) ...
    Selecting previously unselected package grub2-common.
    Preparing to unpack .../grub2-common_2.04-1ubuntu26.12_amd64.deb ...
    Unpacking grub2-common (2.04-1ubuntu26.12) ...
    Setting up libefivar1:amd64 (37-2ubuntu2.2) ...
    Setting up libefiboot1:amd64 (37-2ubuntu2.2) ...
    Setting up grub-common (2.04-1ubuntu26.12) ...
    Created symlink /etc/systemd/system/multi-user.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/>Created symlink /etc/systemd/system/rescue.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/grub>Created symlink /etc/systemd/system/emergency.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/g>
    Job for grub-initrd-fallback.service failed because the control process exited with error code.
    See "systemctl status grub-initrd-fallback.service" and "journalctl -xe" for details.
    update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
    Setting up grub2-common (2.04-1ubuntu26.12) ...
    Processing triggers for systemd (245.4-4ubuntu3.11) ...
    Processing triggers for man-db (2.9.1-1) ...
    Processing triggers for install-info (6.7.0.dfsg.2-5) ...
    Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
    sed -e 's/^GRUB_CMDLINE_LINUX="\(.*\)"$/GRUB_CMDLINE_LINUX="\1 cgroup_enable=memory swapaccount=1 panic_on_oops=>
    sed: can't read /etc/default/grub: No such file or directory
    

    Does anyone have a potential solution to my problem?

    nebulonN 1 Reply Last reply
    0
    • l0u1sgL l0u1sg

      Hello,

      I tried several times to install Cloudron on my VPS running Ubuntu 20.04 but I'm always stuck at the installation stage. Apparently this is a problem with GRUB. Here are the installation logs

      Unpacking libefiboot1:amd64 (37-2ubuntu2.2) ...
      Selecting previously unselected package grub-common.
      Preparing to unpack .../grub-common_2.04-1ubuntu26.12_amd64.deb ...
      Unpacking grub-common (2.04-1ubuntu26.12) ...
      Selecting previously unselected package grub2-common.
      Preparing to unpack .../grub2-common_2.04-1ubuntu26.12_amd64.deb ...
      Unpacking grub2-common (2.04-1ubuntu26.12) ...
      Setting up libefivar1:amd64 (37-2ubuntu2.2) ...
      Setting up libefiboot1:amd64 (37-2ubuntu2.2) ...
      Setting up grub-common (2.04-1ubuntu26.12) ...
      Created symlink /etc/systemd/system/multi-user.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/>Created symlink /etc/systemd/system/rescue.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/grub>Created symlink /etc/systemd/system/emergency.target.wants/grub-initrd-fallback.service -> /lib/systemd/system/g>
      Job for grub-initrd-fallback.service failed because the control process exited with error code.
      See "systemctl status grub-initrd-fallback.service" and "journalctl -xe" for details.
      update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
      Setting up grub2-common (2.04-1ubuntu26.12) ...
      Processing triggers for systemd (245.4-4ubuntu3.11) ...
      Processing triggers for man-db (2.9.1-1) ...
      Processing triggers for install-info (6.7.0.dfsg.2-5) ...
      Processing triggers for libc-bin (2.31-0ubuntu9.2) ...
      sed -e 's/^GRUB_CMDLINE_LINUX="\(.*\)"$/GRUB_CMDLINE_LINUX="\1 cgroup_enable=memory swapaccount=1 panic_on_oops=>
      sed: can't read /etc/default/grub: No such file or directory
      

      Does anyone have a potential solution to my problem?

      nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      @l0u1sg which VPS provider is this? Looks like they have tweaked the ubuntu image a bit an use a different bootloader by default.

      Also do you know which one is used instead?

      l0u1sgL 1 Reply Last reply
      0
      • nebulonN nebulon

        @l0u1sg which VPS provider is this? Looks like they have tweaked the ubuntu image a bit an use a different bootloader by default.

        Also do you know which one is used instead?

        l0u1sgL Offline
        l0u1sgL Offline
        l0u1sg
        wrote on last edited by
        #3

        @nebulon It's a not too well known provider... I'll ask what bootloader they use

        1 Reply Last reply
        0
        • girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          I have seen this occur when trying to install Cloudron on LXC. Can you check that it's not using LXC?

          1 Reply Last reply
          0
          • l0u1sgL Offline
            l0u1sgL Offline
            l0u1sg
            wrote on last edited by
            #5

            I just checked, it is indeed lxc that is used as virtualization technology @girish ... As for the bootloader, it is GRUB 2.0 that is installed @nebulon

            1 Reply Last reply
            0
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #6

              Unfortunately, we don't support lxc.

              1 Reply Last reply
              0
              • nebulonN nebulon referenced this topic on
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search