Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 34

Thread: UEFI: How to repair kali-linux grub dual boot with Windows 10

  1. #21
    Junior Member
    Join Date
    Jul 2017
    Posts
    4
    Quote Originally Posted by _defalt View Post
    /dev/sda is the name of your hard disk. It can be different for different storage units. Always use fdisk -l to see the name of your device.
    I have different disks for Windows and for the Linux I'm trying to install. In my case, Linux partitions are /dev/sdi1, 2 and 3. So I my case, this command should be

    grub-install /dev/sdi

    Right?

    Thanks for this guide and for the reply, and sorry if this question is kind of dumb.

  2. #22
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    The name of disk should be that where you want to install grub. In your case /dev/sdi is the appropriate name. Your situation is similar to this: https://forums.kali.org/showthread.p...-on-Hard-Drive

  3. #23
    Junior Member
    Join Date
    Jul 2017
    Posts
    4
    Ok! Kept getting stuck on the "grub install" command with different errors (even an "input/output" one that looked dreadful). It turned out to be something completely different. Although my BIOS was reporting "secure boot" as disabled, Windows reported it as "Enabled". I had to update my BIOS to get the correct reading and disable it. After that, setup finished without any errors, and GRUB even shows my Windows disk as a bootable option, which I still haven't tried. Thanks again for taking the time to help me out!

  4. #24
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    So did you get it solved or need more asistance with grub installation?

  5. #25
    Junior Member
    Join Date
    Jul 2017
    Posts
    4
    Quote Originally Posted by _defalt View Post
    So did you get it solved or need more asistance with grub installation?
    Everything is running fine. Again, thanks for your help!

  6. #26
    Junior Member
    Join Date
    Aug 2017
    Posts
    10
    root@kali:~# fdisk -l
    Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 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
    Disklabel type: gpt
    Disk identifier: CD914108-4C59-49AC-89E2-56C495FD3BC5

    Device Start End Sectors Size Type
    /dev/nvme0n1p1 2048 616447 614400 300M EFI System
    /dev/nvme0n1p2 616448 878591 262144 128M Microsoft reserved
    /dev/nvme0n1p3 878592 498274303 497395712 237.2G Microsoft basic data
    /dev/nvme0n1p4 498274304 500117503 1843200 900M Windows recovery environment


    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 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: 7B37B810-43B9-458C-A01B-9CED3B9BF283

    Device Start End Sectors Size Type
    /dev/sda1 2048 865132543 865130496 412.5G Microsoft basic data
    /dev/sda2 865132544 866183167 1050624 513M EFI System
    /dev/sda3 1914009600 1953523711 39514112 18.9G Windows recovery environment
    /dev/sda4 866183168 939511807 73328640 35G Linux filesystem
    /dev/sda5 939511808 959565823 20054016 9.6G Linux filesystem
    /dev/sda6 959565824 967907327 8341504 4G Linux swap
    /dev/sda7 967907328 971812863 3905536 1.9G Linux filesystem
    /dev/sda8 971812864 1914009599 942196736 449.3G Linux filesystem

    Partition table entries are not in disk order.


    Disk /dev/sdb: 14.5 GiB, 15597568000 bytes, 30464000 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
    Disklabel type: dos
    Disk identifier: 0xbad74d2f

    Device Boot Start End Sectors Size Id Type
    /dev/sdb1 * 64 5456223 5456160 2.6G 17 Hidden HPFS/NTFS
    /dev/sdb2 5456224 5457631 1408 704K 1 FAT12
    /dev/sdb3 5457920 30463999 25006080 11.9G b W95 FAT32


    Disk /dev/loop0: 2.4 GiB, 2558234624 bytes, 4996552 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

  7. #27
    Junior Member
    Join Date
    Aug 2017
    Posts
    10
    I posted my fdisk -l output. Which partitions do you want me to mount and where do you want me to mount them to? Also the mount --bind /dev /mnt/dev says it cant find mount point /dev when I mount all partitions to /mnt.
    Last edited by G0dlyLuck; 2017-09-09 at 03:44 PM.

  8. #28
    Junior Member
    Join Date
    Jul 2017
    Posts
    11
    Through a bunch of research I found it makes a difference how you setup your USB disk to install Kali. I had previously been using unetbootin to create the image for the install. I found Rosa Image Writer, and I was able to install Kali without any issues. Grub installed automatically during setup.

  9. #29
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    Quote Originally Posted by joed1960 View Post
    Through a bunch of research I found it makes a difference how you setup your USB disk to install Kali. I had previously been using unetbootin to create the image for the install. I found Rosa Image Writer, and I was able to install Kali without any issues. Grub installed automatically during setup.
    You were choosing the wrong partition when you were encountered with grub rescue mode.

  10. #30
    Junior Member
    Join Date
    Jul 2017
    Posts
    11
    Quote Originally Posted by _defalt View Post
    You were choosing the wrong partition when you were encountered with grub rescue mode.
    Case closed.
    Last edited by joed1960; 2017-11-09 at 10:04 PM.

Posting Permissions

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