What ISO image did you use to install Kali?

Can you share the files from /var/log/installer in the problematic system?

Thank you.

ISO image I used is kali-linux-2016.2-amd64.iso
$ sha1sum kali-linux-2016.2-amd64.iso
25cc6d53a8bd8886fcb468eb4fbb4cdfac895c65 kali-linux-2016.2-amd64.iso

and /var/log/installer is uploaded to my Dropbox.
https://www.dropbox.com/s/cg38mhysyt7i3ow/installer.tar.bz2?dl=0

Check please, thank you.

Ok, I have this on a fresh install as well. But if I run update-grub after install, then I get a grub.cfg with UUID.

I'm not sure what explains this behaviour but I'm also not convinced that we need to dig deeper. Does your machine fail to boot due to usage of /dev/sdc1 instead of the corresponding filesystem UUID?

Sorry for late reply.

Yes. my laptop's storage configuretion was below:

When installing
(1) /dev/sda: internal SSD storage. (not used while installing)
(2) /dev/sdb: USB memory stick written kali-linux install image.
(3) /dev/sdc: USB memory stick to be installed

after installing
(3) /dev/sdc ==> /dev/sda (because of boot up media)
(1) ?
(2) removed from the laptop

So, it didn't boot up from (3) USB memory stick..

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/