[javacandy]

I followed all the steps. Downloaded the kali linux iso and used USB universal installer to put the iso onto my memory stick. Once done, I partitioned the USB using MiniTool partition wizard, I formatted the USB (Sandisk 58gb) and called FAT32.

Moved and resized 6.5gb for Kali Linux, then for the grey memory left, I named it 'persistence', changed the file system to EXT3 (some comments say EXT4?) and changed logical to primary.

Booted Kali Linux and clicked 'Live USB persistence' I first noticed the persistence file isn't there, only the audio cd in my disk drive.

I went to the terminal to make my USB persistent but this is where I hit my problem.

Why sudo mount /dev/sdb1 /mnt/UUI?

When I type in: fdisk -l

I see this:

Device Boot Start End Sectors Size Id Type

/dev/sdb1 64 13719509 13719446 6.6G c W95 FAT32 (LBA)

The videos I have seen have this:

Device Boot Start End Sectors Size Id Type

/dev/sdc1 etc etc etc etc etc

/dev/sdc2 * etc etc etc etc etc

Why am I having sdb1 and only sdb1? Why do the videos which I have followed from the beginning, have sdc1 and sdc2?

[Praet0rian]

I followed all the steps. Downloaded the kali linux iso and used USB universal installer to put the iso onto my memory stick. Once done, I partitioned the USB using MiniTool partition wizard, I formatted the USB (Sandisk 58gb) and called FAT32.

Moved and resized 6.5gb for Kali Linux, then for the grey memory left, I named it 'persistence', changed the file system to EXT3 (some comments say EXT4?) and changed logical to primary.

Booted Kali Linux and clicked 'Live USB persistence' I first noticed the persistence file isn't there, only the audio cd in my disk drive.

I went to the terminal to make my USB persistent but this is where I hit my problem.

Why sudo mount /dev/sdb1 /mnt/UUI?

When I type in: fdisk -l

I see this:

Device Boot Start End Sectors Size Id Type

/dev/sdb1 64 13719509 13719446 6.6G c W95 FAT32 (LBA)

The videos I have seen have this:

Device Boot Start End Sectors Size Id Type

/dev/sdc1 etc etc etc etc etc

/dev/sdc2 * etc etc etc etc etc

Why am I having sdb1 and only sdb1? Why do the videos which I have followed from the beginning, have sdc1 and sdc2?

Perhaps you haven't installed the USB right? try to see if you can boot BIOS or UEFI to see if it makes a difference.

[wertfrei12345]

It doesn´t matter if the stick is named "sda/sdb/sdc or sdz" Its just the name. It sounds like u have to format and reinstall the Stick. Did u check the checksum after downloading kali? Did u get Kali from the official Kali Page? Does it have to be a persitant instalation? Kali works just fine in Live enviroment. If u realy want a persistant instalation i (and so does Kali :D) highly recommend using a VM.

[captainspalding]

Perhaps you haven't installed the USB right? try to see if you can boot BIOS or UEFI to see if it makes a difference.

What the shit? Do you know nothing of how linux handles block devices? Installing USBs.. Booting to BIOS... What in the actual..... Why do you keep answering questions you don't even understand!?

@OP When you insert a USB into linux, it can become /dev/sdb1, /dev/sdb2, /dev/sdb3, etc. Some distros even /dev/sdcX and others. If you insert USB and it identifies as /dev/sdb1, mount that. Best way to be sure is to run

Code

fdisk -l

before and after inserting the USB to know exactly which one appears.

[Hash G.]

What the shit? Do you know nothing of how linux handles block devices? Installing USBs.. Booting to BIOS... What in the actual..... Why do you keep answering questions you don't even understand!?

@OP When you insert a USB into linux, it can become /dev/sdb1, /dev/sdb2, /dev/sdb3, etc. Some distros even /dev/sdcX and others. If you insert USB and it identifies as /dev/sdb1, mount that. Best way to be sure is to run

Code

fdisk -l

before and after inserting the USB to know exactly which one appears.

This. The two answers above makes no sense what so ever.

/dev/sdxy
x => identifier of the disk: a for the 1st disk, b for the 2nd disk, etc.
y => identifier of the partition: 1, 2, 3...

Amazingly enough, these identifiers can change depending of your hardware. That's why you don't blindly follow a tutorial.