grubx64.efi is installed. That's why I went with the corrupted option.
After it's sda2 that is missing th files. Sorry for lack of info previously
Printable View
What's the error when you mount /dev, /proc, /sys? No such file or directory? It maybe in /dev/sda3. Mount /dev/sda3 instead of /dev/sda2. I can't see your swap partition, i don't know why.
I'm out of ideas. I never tried with encrypted file system.
I've managed to mount the drive(http://askubuntu.com/questions/63594...m-command-line) and it's sitting in the /media/root directory. Everything looks normal but mount still can't interact with the drive. Now looking for workarounds to this
After many trials and tribulations the solution was actually disappointing. The reason grub didn't install properly was because I started the live usb in UEFI mod. When in UEFI grub won't let you select the partition on which to install and usually fails. I finally figured this out on my parrot OS install(tried it hoping it would be different. It wasn't). So if anyone has the same problem make sure you aren't booting up in UEFI mode first. Sorry for the trouble and I hope this added a little information to the troubleshooters of this forum and reminded to those who knew this that seemingly small changes can have catastrophic events.
P.S. Thanks _defalt and sorry for not trying the obvious sooner, at least now I know how to troubleshoot the grub boot loader to an extent and familiarized myself with the linux command line
I registered just to thank you for posting the solution.
I've been having exactly the same problem, and with my motherboard bios configured for uefi-only, I couldn't work out what the issue was. I didn't see any error messages during the installation, and it all seemed to be working perfectly until I shut down the computer and cold booted.
So it seems I need to temporarily set the bios to legacy boot mode, install Kali to my hdd as gpt/uefi, then set the bios back to uefi-only again.
Addendum: Well, that was obviously never going to work, as I belatedly realized that booting into legacy mode precludes installation in uefi mode. So it looks like I can't install Kali onto a hard drive for uefi booting. I tried 2016.2 and 2017.1 with the same error each time.
I found another reason for this error, and a solution that allowed me to install Kali 2017.1 in UEFI mode.
The problem was caused by the installer designating the hard drive as 'hd1' instead of 'hd0'. Presumably this was due to the fact that I use a sata hot-swap internal enclosure to add and remove hard drives as needed, and when I install a new os I boot the usb first, and then insert the hard drive. The previous Ubuntu-derived installations I've done have handled this without a problem, designating the hdd correctly as hd0 in /boot/grub/grub.cfg, but Kali doesn't seem to handle this scenario well. When I inserted the hdd before booting the usb, Kali installed correctly.
if u mount from USB rempve it then put it again then press chose Yes then Continue