Results 1 to 2 of 2

Thread: problem installing grub (kali linux light X windows 10 )

  1. #1
    Join Date

    problem installing grub (kali linux light X windows 10 )

    the installation finished with an error about grub-install dummy i finished the installation without grub
    when running kali linux on live dvd i tried to do the following commands to install grub
    mount /dev/sda* /mnt
    mount --bind /dev /mnt/dev
    mount --bind /proc /mnt/proc
    mount --bind /sys /mnt/sys
    mkdir /mnt/sys/firmware/efi/efivars
    mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars
    mkdir /mnt/boot/efi
    mount /dev/sda+ /mnt/boot/efi
    mount -o remount,rw /dev/sda+ /mnt/boot/efi
    mkdir /mnt/hostrun
    mount --bind /run /mnt/hostrun
    chroot /mnt
    mkdir /run/lvm
    mount --bind /hostrun/lvm /run/lvm
    grub-install /dev/sda
    umount /mnt/dev
    umount /mnt/proc
    umount /mnt/sys/firmware/efi/efivars
    umount /mnt/sys
    umount /mnt/boot/efi
    umount /mnt/hostrun
    umount /mnt/run/lvm
    umount /mnt

    /dev/sda* is your linux filesystem. Like mine is /dev/sda6
    /dev/sda+ is your EFI partition which is most likely /dev/sda1.
    Use fdisk -l to list all partitions.
    but i get stuck at mount --bind /hostrun/lvm /run/lvm
    i m running dvd on UEFI
    + THIS IS THE RESULT OF fdisk :
    Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disklabel type: gpt
    Disk identifier: 08B61F24-4A4F-455E-8E37-3CA938F1C637

    Device Start End Sectors Size Type
    /dev/sda1 2048 923647 921600 450M Windows recovery e
    /dev/sda2 923648 1128447 204800 100M EFI System
    /dev/sda3 1128448 1161215 32768 16M Microsoft reserved
    /dev/sda4 1161216 511687707 510526492 243.4G Microsoft basic da
    /dev/sda5 511688704 513781759 2093056 1022M Windows recovery e
    /dev/sda6 513783808 955801599 442017792 210.8G Microsoft basic da
    /dev/sda7 955801600 968603647 12802048 6.1G Linux filesystem
    /dev/sda8 968603648 976771071 8167424 3.9G Linux swap

    Disk /dev/loop0: 612.2 MiB, 641912832 bytes, 1253736 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    please i need it to work tonight, thank you in advance

  2. #2
    Join Date
    It would be helpful if you could post what exactly is reported on the failed command "but i get stuck at mount --bind /hostrun/lvm /run/lvm
    i m running dvd on UEFI".

    The way I see Fdisk reporting is that the system (laptop or PC or whatever) is setup to recover and reinstall Windows from sda1 when the correct keys are held at power on. sda2 looks like your EFI partition.

    sda1 is pretty small, just 450MB, there is another large recovery partition at sda5.

    You also appear to have two separate installs of Windows on sda4 and sda6, Your Linux filesystem is listed at sda7, not sda6 as stated in your first post.

    You might have borked the Restore partitions by corrupting them, but it looks like you didn't actually get close to writing data, ie putting grub on it.

    Even if the restore partitions are messed up, you can still reinstall Windows from a DVD or stick, but the built in one might be toast now. Hopefully not.

    Don't delete the spaces after the sda+ and sda* entries by mistake. Spaces are important as they show the command line interpreter where one part ends and the next begins. Cut and paste is not always your friend in these cases when you have to delete one dummy character like "*" and replace it with a number. YOU CAN DELETE A SPACE BY ACCIDENT AND MESS THINGS UP.

    Do you already have a menu to select between 2 installs of Windows or is a case of one Windows boot partition, one data? if you're only using one it would be useful to know which one is actually Windows.

    If you have data you want to keep on a dual boot system, back it up before you even attempt to install Kali Linux as per;-

    Also, it helps to have log files from installs to get support, as per;-

    But I think you'll get there or back out furiously and backup your data first. Having Windows with anything sharing a hard disk isn't ideal. In my opinion. But it's not that difficult, just a bit too easy to screw the thing up and have to rebuild it.
    Last edited by NoobLinuxuser; 2018-12-12 at 03:57.

Similar Threads

  1. No Grub after installing Kali alongside Windows 10
    By Rabiii3 in forum Installing Archive
    Replies: 1
    Last Post: 2018-06-28, 14:27
  2. Problem with installing kali linux along Windows 10 in UEFI
    By Grim95 in forum Installing Archive
    Replies: 1
    Last Post: 2017-12-07, 10:03
  3. kali linux 2.0 with windows 10 uefi mode - grub problem
    By Xele in forum Installing Archive
    Replies: 1
    Last Post: 2015-09-25, 08:22

Posting Permissions

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