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

Thread: Weirdest Issue: Installing Kali Linux On An External Harddrive

  1. #11
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    619
    Your firmware doesn't have option to add entry of grub from EFI. Even if it has we might have missed it somewhere in the UEFI settings. So we are going to use the long way. Follow the instructions given here to reinstall grub: https://forums.kali.org/showthread.p...ith-Windows-10

    Also show the output of fdisk -l once you boot kali live.

  2. #12
    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

    This is the output of fdisk -l. Following your guide i have to mount all my linux partitions?

    I mounted all my partitions to /mnt. However when i do "root@kali:~# mount --bind /dev /mnt/dev" it says "mount: mount point /mnt/dev does not exits". A penny for your thoughts?
    Last edited by maiki; 2017-09-11 at 10:02 AM. Reason: Merge posts

  3. #13
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    619
    When you run those commands, replace /dev/sda* with /dev/sda4 and /dev/sda+ with /dev/nvme0n1p1. grub-install /dev/sda will become grub-install /dev/nvme0n1 where /dev/nvme0n1 is the name of your SSD.

    Be careful with spaces or copy paste them.
    Last edited by _defalt; 2017-09-09 at 08:28 PM.

  4. #14
    Junior Member
    Join Date
    Aug 2017
    Posts
    10
    You sure? The EFI folder with Grubx64.efi (or however its called) is located in /dev/sda2. I want to know why you choose the EFI partition on /dev/nvme0n1p1 (i want to learn more about it than just perform tasks )

    Alright so I reinstalled the bootloader to sda2. It works again!!!!! I owe you 40$! Please send me a paypal email address because you deserve the money for solving this issue that those people at the computer store couldnt.
    Last edited by maiki; 2017-09-11 at 10:03 AM. Reason: Merge posts

  5. #15
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    619
    Quote Originally Posted by G0dlyLuck View Post
    You sure? The EFI folder with Grubx64.efi (or however its called) is located in /dev/sda2.
    You can install grub in either of the EFI partition. Some people even install grub in USB.

    Quote Originally Posted by G0dlyLuck View Post
    I want to know why you choose the EFI partition on /dev/nvme0n1p1 (i want to learn more about it than just perform tasks )
    In /dev/nvme0n1p1 your windows bootloader is also present so it is just for convenience if both the bootloaders lies in same EFI partition.

    But while installing grub you have to make sure where you are installing it. You must know the name of partition to mount and the name of that EFI partition where grub will be installed. The name of disk is also required to point grub-install command to the disk where your EFI partition is. That's why i asked you to make following changes while entering those commands:
    Quote Originally Posted by _defalt View Post
    When you run those commands, replace /dev/sda* with /dev/sda4 and /dev/sda+ with /dev/nvme0n1p1. grub-install /dev/sda will become grub-install /dev/nvme0n1 where /dev/nvme0n1 is the name of your SSD.

    Be careful with spaces or copy paste them.

    Quote Originally Posted by G0dlyLuck View Post
    Alright so I reinstalled the bootloader to sda2.
    It wouldn't have worked if name of your disk and partitions were different. While creating that thread i chose the standard name as /dev/sda and this is different for each storage units attached with your system.
    Last edited by _defalt; 2017-09-09 at 08:57 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
  •