Question

Droplet showing error: file '/grub/i386-pc/normal.mod' not found

Hi, Yesterday one of our droplets started showing error: file ‘/grub/i386-pc/normal.mod’ not found error due to this our server got down and we are unable to connect with the server.

We raised a ticket to resolve it but they said:

After reviewing the details and the droplet Techdost the issue stems from the GRUB bootloader failing to find the file listed due to a change in GRUB’s method of checking for available files (or perhaps this file has actually been removed, either due to a problematic update or some improperly-formatted shell command). One way to try working around this would be to boot into our Recovery ISO: https://www.digitalocean.com/docs/droplets/resources/recovery-iso/

From there, you should be able to select option #1 from the Recovery menu to mount the Droplet’s virtual disk, then select option #5 to attempt to chroot into the Droplet’s filesystem. From within the chroot, you may issue a grub-install command as noted below, replacing $disk with your current disk’s name as identified by the lsblk command (usually this will be vda): grub-install --root-directory=/ $disk If you’re unable to boot into your Droplet at this point, it may be helpful to try performing a manual check of the GRUB recovery environment as noted in the following link: https://askubuntu.com/a/462995

As with any critical maintenance task, we advise that you create a snapshot of the Droplet before proceeding. https://docs.digitalocean.com/products/images/snapshots/how-to/create-and-restore-droplets/

We tried it but when we select option #5, nothing happened. We told him then they sent other instructions.

Can you please share the screenshot when your are trying to get in chroot by typing 5?

I understand that you are still stuck at Grub Rescue mode. It may be helpful to try performing a manual check of the GRUB recovery environment. Please review the below suggested links on how to troubleshoot the grub issue:

https://askubuntu.com/questions/266429/error-file-grub-i386-pc-normal-mod-not-found/462995#462995 https://askubuntu.com/questions/232215/stuck-in-grub-rescue-mode https://www.howtoforge.com/tutorial/repair-linux-boot-with-grub-rescue/

In order to install Grub, you can try to manually chroot into your Droplet’s filesystem by typing 6 in the recovery menu and then run:

chroot /mnt/

If you encounter any issues at this point, then you might want to try to unmount the disk, then go back to the BASH shell (from the Recovery menu) and try to manually mount your disk before attempting a chroot:

mount /dev/vda1 /mnt mount --bind /dev /mnt/dev mount --bind /dev/pts /mnt/dev/pts mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt/

If that all completes without error, then from inside the chroot you can try to manually reinstall the GRUB bootloader with the below command:

grub-install /dev/vda

If that completes without error, then you can exit the chroot (CTRL+d keystroke, or the exit command), go back to the Cloud panel and select the option to boot the Droplet from its Hard Disk, then power it off and back on.

This also didn’t work.

We then changed the Boot from Hard Drive and found the location of /grub/i386-pc/normal.mod at (hd0,glt1)/usr/lib/grub with the help of this video https://www.youtube.com/watch?v=vhZ415ZWNdY

We followed this video but got stucked when we run ls (hd0,gpt2)/boot command but it didn’t show vmlinuz-4.18.0-16-generic, initrd.img-4.18.0-16-generic files.

Kindly help me, I’m trying to resolve it since yesterday, it’s very urgent as we don’t have a data backup.


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello,

In such situations, I’ll recommend starting the recovery console and following these steps:

  1. grub rescue> set pager=1
  2. grub rescue> ls

The output should be something like:

  1. (hd0) (hd0,msdos1) (hd0,msdos2) (hd0,msdos3) (hd0,msdos4)

Now you need to ls each partition to find out which points to your Linux installation if you don’t know already. For that run,

  1. grub rescue> ls (hd0,msdosX) # X can be any number based on previous command output

Take note of the partition number and then run,

  1. grub rescue> set root=(hd0,msdos2) # replace `msdos2` with your Linux partition
  2. grub rescue> set prefix=(hd0,msdos2)/usr/lib/grub/
  3. grub rescue> insmod normal
  4. grub rescue> normal

After that, you should see your grub prompt has changed from grub rescue> to grub>. Now we are in normal GRUB mode.

Boot the system by loading the kernel manually The next step is to load the kernel and boot the system as follows,

  1. grub> linux /boot/vmlinuz-X.YY.Z root=/dev/sda1
  2. grub> initrd /boot/initrd.img-X.YY.Z
  3. grub> boot

Once you run the boot command, your Linux should start booting.

Copy grub files to /boot/grub After booting the system successfully the last step is to copy the missing files and update the GRUB for safety as follows:

$ sudo cp -r /usr/lib/grub/i386-pc /boot/grub
$ sudo update-grub # or grub-mkconfig -o /boot/grub/grub.cfg