pbatard
commented
4 years ago The persistence partition is created is of fat32.
No it's not. The other (non persistent) partition is FAT32, but the persistent partition is ext3.
The log explicitly tells you so:
(...)
Partitioning (GPT)...
● Creating Main Data Partition (offset: 1048576, size: 4.5 GB)
● Creating Linux Persistence Partition (offset: 4789871104, size: 10.0 GB)
(...)i.e. TWO partitions are created
(...)
Formatting (ext3)...
(...)i.e. the persistent partition (second one) is being formatted using the ext3 file system
(...)
Formatting (FAT32)...
(...)i.e. the main (i.e. non-peristent) partition is formatted as FAT32.
In other words, the problem is not that the persistent partition is not created using the ext file system (using ext3 instead of ext4 is not an issue. Persistent partitions work fine regardless of whether ext2, ext3 or ext4 is used, and I actually have no plans to add ext4 support at this stage, since ext3 is absolutely fine for a persistent partition and ext4 would add a lot of complexity for little benefit). The problem is that the Kali Linux people have chosen to use a persistence method that isn't a Debian or Ubuntu derivative.
THIS is actually the main issue with persistence in Linux (outside of Ubuntu bug 1489855, which is plaguing Ubuntu derivative distros and is very slowly being patched): There is no standard to adding persistence in Linux, so every distro is free to do whatever the hell they want, which would just be fine if they were doing the RIGHT thing, and just checking to see if there exists a partition with the right label (Ubuntu & derivatives) or a persistent.conf (Debian & derivatives), without bothering with kernel options, but the problem is they don't.
So you'll need to take the problem to the Kali people and ask them explicitly this:
Why is is that, if I create 2 partitions on a USB drive, one formatted as FAT32 and the other as ext3, then extract the whole content of the Kali ISO onto the FAT32 partition and boot the drive in UEFI mode, Kali does not automatically recognize the ext3 partition as a persistent one, even if it contains a persistence.conf at the root level, and the persistence keyword was added to the boot option which is all Debian requires?
You don't even need to involve Rufus here. You'll see the same issue if you do it as described above, so, really, since Kali is supposed to be a Debian derivative, it's up to the Kali folks to fix this, because is Debian works (and you can validate that it does with Debian Live), then there's no reason Kali shouldn't
lock[bot]
Checklist
<FULL LOG>below.Rufus version: x.y.z- I have NOT removed any part of it.Additionally (if applicable):
(✓)button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.Issue description
I used a kali lunix live boot file to make bootable my pen drive[16 GB]. It show create a persistence i selected 10 GB. The persistence partition is created is of fat32. It should have EXT4. So please fix it so that the persistence will work in kali lunix. Else everything is great. Thanks for this app
Log