Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: GRUB loader not shown - Dual boot Windows 10 and Kali linux 2016.2

  1. #11
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda/root
    Posts
    265
    They should have worked. That's the appropriate way to re-install grub in UEFI.
    Last edited by _defalt; 2017-02-16 at 01:03 PM.

  2. #12
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda/root
    Posts
    265
    You can skip update-grub command and enter the remaining.

    There is a way to disable lvmetad from /etc/lvm/lvm.conf by setting use_lvmetad = 0 but whether it should be done from kali-live root directory or from the mounted linux partition is confusing. You can try this if skipping that step doesn't work.

  3. #13
    Junior Member
    Join Date
    Feb 2017
    Posts
    7
    Quote Originally Posted by _defalt View Post
    They should have worked. That's the appropriate way to re-install grub in UEFI.
    But shouldn't I see an instance then in BIOS Boot or in the Boot Manager?


    Quote Originally Posted by _defalt View Post
    There is a way to disable lvmetad from /etc/lvm/lvm.conf by setting use_lvmetad = 0 but whether it should be done from kali-live root directory or from the mounted linux partition is confusing. You can try this if skipping that step doesn't work.
    Edited the lvm.conf file and set use_lvmetad = 0.

    What would you say could show the GRUB loader on boot?
    I mean I found the two solutions (Holding Shift / pressing ESC continuously)
    Is there another way to "help" GRUB to show himself?


    EDIT:
    OK, maybe I found the problem, but could not solve it.

    I launched all the commands as usually.
    But this time, before I unmounted /mnt I checked the /boot directory.
    Before the unmount:
    ~# cd /boot
    efi/ grub/
    ~# cd /boot/grub
    fonts/ locale/ x86_64-efi/

    After that i unmounted as mentioned before all relevant mountpoints.
    After unmount:
    ~# ls /boot
    config-4.6.0-kali1-amd64 System.map-4.6.0-kali1-amd64
    initrd.img-4.6.0-kali1-amd64 vmlinuz-4.6.0-kali1-amd64

    So grub was no longer in the boot directory, and i don't understand why?
    Is it somewhere else?
    Last edited by Snaggor; 2017-02-17 at 10:54 AM.

  4. #14
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda/root
    Posts
    265
    I told you to run those commands again by skipping update-grub command. Did it work?

    Modifying lvm.conf was supposed to be that step if earlier resolution didn't have worked. You have modified lvm.conf file of kali-live partition which has no use and is reverted back to its original state after reboot. Even if you manage to set lvm=0 in your B]root[/B] partition that doesn't do anything. It was just to solve that error you were getting while update-grub. There is no other significance of modifying it at all.
    Last edited by _defalt; 2017-02-17 at 07:48 PM.

  5. #15
    Junior Member
    Join Date
    Feb 2017
    Posts
    7
    Quote Originally Posted by _defalt View Post
    I told you to run those commands again by skipping update-grub command. Did it work?
    Yeah I did what you told me to do.
    Well, it worked to go through all these commands without update-grub but the GRUB loader is still not shown.
    So no it didn't work...

  6. #16
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda/root
    Posts
    265
    Run umount /dev/sda2 /mnt/boot/efi and then open file manager. Go to /mnt/boot/efi/EFI/kali see if grubx64.efi is present?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •