Hi,
I just installed Kvm (through Docker) in a machine running Deepin.
When Kvm boots it goes to grub-rescue with the following error message: "error: file /boot/grub/i386-pc/normal.mod not found".
I googled the problem and all answers center on checking if root is correct (it is,since there is only one partition), setting prefix correctly (which is now "(hd0,msdos1)/boot/grub) and typing "insmod normal" - "normal".
The problem is, even after checking, when I type "insmod normal", the error message appears again.
I did "ls /boot" to see what was in there, and /boot is empty.
I read in another forum that this could be solved by: "cp -r /usr/lib/grub/i386-pc /boot/grub", but I have no idea how to do that in a vm, or if its even possible.

Any help would be greatly appreciated.

1. Please post /etc/fstab
2. Please post fdisk -l

1 members found this post helpful.

Read this: https://askubuntu.com/questions/2664...-mod-not-found

1 members found this post helpful.

that is your problem /boot shouldn't be empty. Give complete details of what you did to set up kvm and any error messages.

1 members found this post helpful.

Hi all, thank you for taking the time to help.
I'll by order of the posts:

Keruskerfuerst - my /etc/fstab is this:

# /dev/sda4
UUID=4d4030dd-dfd9-4d99-a59c-24dd7faa3813 / ext4 rw,relatime,data=ordered 0 1

# /dev/sda3
UUID=8e5ab1bf-660a-4895-bb78-78b722e69ba6 none swap defaults 0 0

My fdisk -l is the following:

Device Boot Start End Blocks Id System
/dev/sda1 1 1 8001 83 Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2 * 1 17 128520 83 Linux
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda3 17 82 522112 83 Linux
Warning: Partition 3 does not end on cylinder boundary.
/dev/sda4 82 60802 487733400 83 Linux
Warning: Partition 4 does not end on cylinder boundary.

AwesomeMachine - I already read it but it didn't help. I looked for "/i386-pc/normal.mod" as suggested, but couldn't find it, but as the vm created only one partition (the output of "ls" in grub rescue was "(hd0), (hd0, msdos1))", I think there is no other possibility but to be on hd0,1. I set the prefix to (hd0,1)/boot/grub and root to (hd0,1), but, as there is nothing inside boot, it didn't help.

colorpurple21859 - I set up kvm through docker, using this files: https://github.com/jessfraz/dockerfiles/tree/master/kvm. I had no error messages prior to the one I already told you about.

I see 4 partitions and / on the 4th partition

1 members found this post helpful.

That refers to the host. When I answered Keruskerfuerst, I took the information from the host, since I had already explained that in the vm I was in grub-rescue mode and unable to collect the asked information.

The fstab and fdisk output from the host machine won't be helpful. When you see the grub prompt when trying to boot in the virtual machine and run the following do you see the grub directory? If you add grub to the command, do you see any files?

1 members found this post helpful.

Your running kvm inside of a container? what is the output of ls (hd0,msdos1)/

1 members found this post helpful.

Hi,

Answering yancek and colourpurple21859 questions:

Output of (hd0,msdos)/

"lost+found / vmlinuz var / bin / usr / lib / etc / tmp /sys / sbin / run /root / proc / home /dev / boot/ mnt / srv /opt / media / initrd.img vmlinuz,old initrd.img.old"

Output of ls (hd0,msdos1)/boot

Nothing.

Output of ls (hd0,msdos1)/boot/grub

" 'boot/grub' not found"

The normal answer would be to boot from a live iso, chroot into the system, install grub with package manager if not installed and then install grub to drive. However, because your running kvm from docker, I suspect you will have to pass parameters to the container when starting, but I don't know what they would be. Some one smarter than me will have to chime in on this one.

I recently had this problem after installing Linux Mint onto a HDD on a Dell laptop (not shared with any other OS). After the installation had completed (with no errors) it would not boot into the new OS, just came up with the “/boot/grub/i386-pc/normal.mod" not found GRUB error message.

I entered the Bios setup (F2 at powerup) and changed the SATA mode from AHCI to IDE mode, ignoring the warning about maybe making the HDD unreadable, and after saving & exiting the setup menu it booted into Linux Mint with no further actions needed.

Dave