Geek Answers Handbook

Custom Linux Kernel Build Failure on VMware Workstation

When trying to compile / create and load the user kernel inside the vmware workstation when loading the new kernel, it fails and gets into the shell with the error "could not find the drive by uuid". I tried this with both ubuntu and centos.

Things I tried but didn't help

  • check uuid mapping in boot record and directory existence.
  • initramfs update
  • replaced root = uuid = <> with / dev / disk / sda 3

enter image description here

Is this a problem with vmware workstation? how can this be fixed .. ??

+6
source share
3 answers

The problem is creating initramfs after execution

do oldconfig

and selecting the default value for the new settings, make sure that the available ENOUGH disk space is available for the image being created. in my case, the created image was incorrect and, therefore, the image could not be mounted at boot time.

when comparing; the image size was significantly smaller than the existing image of a lower version, so I added another disk with more than enough size, and then

do bzImage

make modules

make modules_install

make installation

starts to work like a charm. I wonder why the image creation was completed earlier and led to a damaged image (with a smaller size) without causing errors [every time]

0
source

I had a similar error with my own attempts to load Fedora 22 onto an empty partition by installing Centos on another partition. I never solved it completely, but I found that the problem was in my initrd and not in the kernel.

The problem is that initrd does not start LVM because dracut did not tell initrd that it needs LVM. Therefore, if you start LVM manually, you can download it to your system to fix it.

I believe that this is a sequence of commands that I ran from the emergency shell to start LVM:

vgscan vgchange -ay lvs

this link helped me remember

This is followed by exit to resume normal boot.

You may need to manually mount the LVM / etc / fstab entries, I don’t remember whether I did this or not.

+2
source

Try the following:

 sudo update-grub

Then:

 mkinitcpio -p linux

Unable to check your fstab . There you should find the UUID of your drive. Make sure that the appropriate flags are set in fstab .

In addition, there is the grub.cfg parameter, which has GRUB , to use the old hexadecimal UUID style. Check it out too!

0
source

More articles:


All Articles