Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: Kali 2016.2 after-instal issue HDD not a proper boot device

  1. #1
    Junior Member
    Join Date
    Apr 2017
    Posts
    9

    Kali 2016.2 after-instal issue HDD not a proper boot device

    I have successfully installed kali 2016.2 64 bit with encrypted LVM on my HDD (A WD caviar 1Tb) but after I reboot it says "Reboot and select proper Boot device - Insert Boot Media in selected Boot device and press a key". I actually had installed the the 32-bit version whitout issues.

    My sys specs are:

    CPU: Intel i3-6100T,3.2 Ghz,3mb cache,LGA1151,35W
    RAM:Ballistix 16Gb(4x4) DDR4-3200 UDIMM 1.35V
    GPU:XFX Radeon RX 460 4GB 1220M
    Mobo:MSI Z170A-G43 PLUS(Crossfire version)

    I already know that the processor supports 64-bit, this seems like a grub bootloader issue, any help?

  2. #2
    Senior Member
    Join Date
    Apr 2013
    Location
    in a computer
    Posts
    551
    I'd try making a bootable USB or DVD, and see if it will run on your system.

  3. #3
    Junior Member
    Join Date
    Apr 2017
    Posts
    9
    I have made a usb and the live version works fine, but the issue remains

  4. #4
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    417
    Is grub installed in your HDD? Did you check if it is installed in your boot sector?

  5. #5
    Junior Member
    Join Date
    Apr 2017
    Posts
    9
    Quote Originally Posted by _defalt View Post
    Is grub installed in your HDD? Did you check if it is installed in your boot sector?
    While the installer says that GRUB is installed I'm not really sure though this only occurs in the 64-bit version. In the 32-bit installer I see it immediately after the BIOS finishes.

    I'm actually suspicious that GRUB hasn't installed normally, but this has been persistent between installs and I'm not sure how to check

    PS: I'm writing from Kali 2016.2 64-bit live without issues

  6. #6
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    417
    Show the output of fdisk -l

  7. #7
    Junior Member
    Join Date
    Apr 2017
    Posts
    9
    Quote Originally Posted by _defalt View Post
    Show the output of fdisk -l
    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

    Device Start End Sectors Size Type
    /dev/sda1 2048 1050623 1048576 512M EFI System
    /dev/sda2 1050624 1550335 499712 244M Linux filesystem
    /dev/sda3 1550336 1953523711 1951973376 930.8G Linux filesystem

  8. #8
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    417
    Boot into kali-live and enter mount /dev/sda1 /mnt and see if it is in /mnt/EFI/kali/grubx64.efi. If it is there then It might be got corrupted. For that run these commands:

    Code:
    sudo mount /dev/sda2 /mnt
    sudo mount --bind /dev /mnt/dev
    sudo mount --bind /proc /mnt/proc
    sudo mount --bind /sys /mnt/sys
    sudo mount /dev/sda1 /mnt/boot/efi
    sudo chroot /mnt
    grub-install /dev/sda
    exit
    sudo umount /mnt/dev
    sudo umount /mnt/proc
    sudo umount /mnt/sys
    sudo umount /mnt/boot/efi
    sudo umount /mnt

  9. #9
    Junior Member
    Join Date
    Apr 2017
    Posts
    9
    Boot into kali-live and enter mount /dev/sda1 /mnt and see if it is in /mnt/EFI/kali/grubx64.efi. If it is there then It might be got corrupted. For that run these commands:
    A lot of the directories are missing(/dev, /proc, /sys)

    The only one in /dev/sda2 are:

    config-4.6.0-kali1-amd64
    efi
    grub
    initrd.img-4.6.0-kali1-amd64
    lost+found
    System.map-4.6.0-kali1-amd64
    vmlinuz-4.6.0-kali1-amd64

    There is a chance that they are in /dev/sda3 but because I setup encrypted LVM I can't mount it to /mnt because the file system is crypto_LUKS even though I have decrypted the drive in the file browser. Other than that they might just be straight up missing
    Last edited by alexertech; 2017-04-07 at 05:28 PM.

  10. #10
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    417
    I told you to mount only EFI partition in /mnt. Your EFI partition isn't encrypted. Once you come to know that grub is there or missing then either it is corrupted or not-installed.

    Only then you are supposed to perform those list of commands after restarting kali live.

Posting Permissions

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