My Server is down with error: file '/boot/grub/i386-pc/normal.mod' not found.

When I try to launch the console from panel I get this error: file ‘boot/grub/i386-pc/normal.mod’ not found. And prompt of “grub rescue” comes. I have no idea how to resolve this issue. Here is what I have tried so far:

  1. Tried contacting support but no satisfactory answer. they gave me 2 link as below, I tried and couldn’t find anything.

  2. The above links suggested to change the prefix I tried, but it didn’t worked, here is the output of ls. grub rescue> ls (hd0,gpt1)/boot ./ …/ efi/ grub rescue> ls (hd0,gpt1)/boot/efi ./ …/ NO FILES/FOLDER inside efi folder and there no grub folder as well. So I think grub is removed. And I have no idea why/how.


  1. I was having issues in accessing the SSH and SFTP it was giving the access denied error. I contacted support and they suggested to do a root password reset from DO panel. I did. And that was the disastrous step. After that server RAM usage is at 60%+ and I am not able to access anything. I tried the root password reset again. Password changed server restarted and we are back to zero.
  2. I tried turning off the server and turn back on. Again no change.

Please help me out. Everything is down.

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.

What operating system do you have?

The first thing that you should do when setting up a droplet, is create a regular user, give that user ssh permission, and then after testing it, disable root ssh. Then always log in as regular user, then you can su - to root.

Wayne Sallee