Kali Linux Live USB Persistence: Keep Your Work Across Reboots

Why Persistence Matters

When you run Kali Linux from a USB stick, the operating system boots from a read‑only image. Every change you make – installing tools, tweaking settings, or dropping a capture – disappears once you reboot. Persistence solves this by creating a writable area that survives reboots, allowing you to carry your custom configuration and data wherever you go.

Setting Up a Persistent Live USB

Below is a step‑by‑step guide that works on most Kali releases (2024‑04 and newer). It assumes you have a USB stick of at least 8 GB and a working Kali Live session.

1. Identify the USB device (replace /dev/sdx with your actual device):

   sudo fdisk -l
   # Look for the device that matches your USB size and model
   

2. Create a new partition for persistence using fdisk or parted. The partition should be ext4 for best compatibility.

   sudo fdisk /dev/sdx
   # In fdisk:
   #   n   (new partition)
   #   p   (primary)
   #   2   (partition number)
   #     (accept defaults to use remaining space)
   #   t   (change type)
   #   2   (partition number)
   #   83  (Linux filesystem)
   #   w   (write changes)
   

3. Format the new partition:

   sudo mkfs.ext4 -L persistence /dev/sdx2
   

4. Create the persistence configuration file on the boot partition (usually /dev/sdx1):

   sudo mkdir /mnt/usb
   sudo mount /dev/sdx1 /mnt/usb
   sudo nano /mnt/usb/persistence.conf
   # Add: /home
   # Save and exit
   sudo umount /mnt/usb
   

5. Enable persistence at boot by editing the boot menu. In Kali 2024, the default GRUB entry is already set to look for a persistence partition. If not, add the following to the boot line:

   persistence
   

6. Reboot and choose the persistent boot entry. Kali will mount /dev/sdx2 as /home/kali automatically.

Worked Example: Creating and Verifying a Persistent File

After booting into the persistent environment, test that writes survive reboots.

# Run as the default Kali user
mkdir -p /home/kali/test
echo "Persistence test" > /home/kali/test.txt
# Verify file exists
cat /home/kali/test.txt
# Reboot the system
sudo reboot

Once the system restarts, log back in and run:

cat /home/kali/test.txt

If the output still shows "Persistence test", the persistence area is working.

Limitations and Trade‑offs

• Size Constraint – The persistence partition is limited to the free space you allocated. If you need more, you must recreate the partition.
• No System Updates – System packages, kernel upgrades, and configuration files outside /home are not persisted. You’ll need to reinstall or reconfigure after each boot if you modify system files.
• Unencrypted by Default – Data stored in /home/kali is plain text. If the USB falls into the wrong hands, sensitive data is exposed. Consider setting up an encrypted partition or using tools like VeraCrypt.
• Write‑Protected Media – If the USB is write‑protected or read‑only, persistence will not work. Ensure the write‑protect switch is off.

Verifying the Persistence Partition is Mounted Correctly

After boot, confirm the partition is present and mounted:

# List block devices and labels
sudo blkid | grep persistence
# Check mount points
mount | grep persistence

The output should show /dev/sdx2 mounted at /home/kali. If not, revisit the persistence.conf and boot menu entries.

Practical Takeaway

Persistence turns a disposable Kali Live USB into a portable, personalized toolkit. By following the steps above, you can keep custom tools, scripts, and data across reboots, saving time and reducing the need to re‑install or re‑configure each session. Just remember the trade‑offs: limited size, no system updates, and lack of encryption. For sensitive work, layer an encrypted partition or use full‑disk encryption on the USB.