Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


errors in Rescue mode
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

errors in Rescue mode

JDMcPeaJDMcPea Member

My VPS will start but shows the error:

Booting from Hard Disk...
error: file '/boot/grub/i386-pc/normal.mod' not found
Entering rescue mode...
grub rescue>

But normal.mod IS present in the /boot/grub/i386-pc folder.

When I boot into Rescue mode from the Solus CP it boots I get the same kind of errors, for example when I run:

rescue # chroot /mnt/root

Get the error:

chroot: failed to run command ‘/bin/bash’: No such file or directory

Again can see that the /bin/bash directory is present.

Can anyone tell me how to fix this, or what would cause this kind of error, or point me in the right direction?

Thanks

Comments

  • try with sudo, and run fsck and grub-install:
    umount /mnt
    mount /dev/sda3 /mnt
    grub-install --root-directory=/mnt /dev/sda

    Replace parition names to fit your scheme.

    Thanked by 2JDMcPea desperand
  • Thanks @luckypenguin

    Sudo command not found:

    rescue # sudo mkdir /test
    -bash: sudo: command not found

    The Rescue mode from Solus is 4.x (Roaring Lionus) Kernel - 64bit and login is root. But I get all kinds of errors as mentioned above and even when I try to do something simple does not work- example:

    rescue # mkdir /test
    mkdir: cannot create directory ‘/test’: Read-only file system

    Can anyone tell me what I am missing here and/or point me in the right direction?

  • jmgcaguiclajmgcaguicla Member
    edited July 2022

    @JDMcPea said:
    The Rescue mode from Solus is 4.x (Roaring Lionus) Kernel - 64bit and login is root. But I get all kinds of errors as mentioned above and even when I try to do something simple does not work- example:

    rescue # mkdir /test
    mkdir: cannot create directory ‘/test’: Read-only file system

    This is expected, squashfs as root (which is read-only by itself if not used with overlayfs/aufs + tmpfs) is a common setup in rescue images (assuming you're not chroot-ed yet when you run this).

    @JDMcPea said:
    When I boot into Rescue mode from the Solus CP it boots I get the same kind of errors, for example when I run:

    rescue # chroot /mnt/root

    Get the error:

    chroot: failed to run command ‘/bin/bash’: No such file or directory

    Again can see that the /bin/bash directory is present.

    Are you sure it's there? Note that the indicated path is relative to the directory you're chroot-ing into, in that case it's trying to find bash in /mnt/root/bin/bash.

    How did you mount the disk, is it mount /dev/sdX /mnt/root?

    Thanked by 1JDMcPea
  • @jmgcaguicla . Was able to make some changes using your tips but the OS is still won't boot. Anyway added to my linux knowledge a bit. Thanks

  • If you're still having problems try contacting your provider's support

Sign In or Register to comment.