new install to usb was successful, however cannot boot the usb drive

[kingfitz]

Hi,

I installed new kali-2016.1 to a new flash drive, and the procedure went successfully. I selected guided partitioning for the 32gb flash drive, installed grub bootloader to the same drive because I want it completely isolated from windows. It said successful, now restart system to boot drive. But it will not boot automatically, and even manually selecting the drive in UEFI bios just loads to a black screen with a blinking _

Not sure what the problem is, the new kali version fixed the problem where mouse keyboard werent detected, seems like it was improved nicely. But cannot boot.

I followed instructions here to a T (except on step 14, I didnt install to windows MBR, but instead installed grub loader to the same flash drive) : http://docs.kali.org/installation/ka...d-disk-install

Thanks. Sorry for previous post I was trying with the kali 2.0 version. please delete my first post.

[duxim]

you can try different approach to install Kali on usb describe here
https://forums.kali.org/showthread.p...ind-of-problem

[village_idiot]

I have been having similar problems. The bootable pen drive
seemed to load properly but when attempting to use it as
a boot device it would either bypass the device during the
boot process or just stop and display a black screen saver
with a blinking horizontal cursor. I have tried differing
manufacturers on the drives and thus far PNY 4GB Attache
drives have worked for me. I still have no clue why other
drives fail to work with the same load.

VI

Who is General Failure and why is he reading my hard disk?

[village_idiot]

Quick Followup

I ran a checksum on each of the partitions on
each of the two drives. There are two partitions
displayed on each drive when running fdisk -l

They are

/dev/sdc1 * 64 5679569 5679296 2.7 G 17 Hidden HPFS/NTFS
/dev/sdc2 5679360 5859071 179712 87.8 M 1 Fat12

Both drives display the exact same data for
partitioning information with one being a 4 GB
pen drive and the other a 16 GB pend drive.

SDC1 MDSUM was the same as SDD1 and SDC2
MD5SUM was the same as SDD2. The only
difference I can discern at this time is the
brand and size. Will see what other info I can
obtain.

VI

Eagles may soar but weasels don't get sucked into jet engines.

[Infinite Niubility]

I had also encountered a similar issue, just that the root device was not identified by uuid, but disk labels, so when I boot on another machine, it will just say that the root device /dev/sdxx not found, anyone knows how to fix this?