PDA

View Full Version : Kali Live via USB --> not enough storage space



th-vb
2017-11-10, 16:47
Hey

I downloaded the latest kali version and wrote it on a usb (8GB).
When I try to add Persistence to my live usb I get an error not enough space to build proposed filesystem while setting up superblock?

Here are my commands

root@kali:~# read start _ < <(du -bcm kali-linux-2016.2-amd64.iso | tail -1); echo $start
du: cannot access 'kali-linux-2016.2-amd64.iso': No such file or directory
0

root@kali:~# parted /dev/sdb mkpart primary $start $end
Warning: You requested a partition from 0.00B to 7000MB (sectors
0..13671875).
The closest location we can manage is 512B to 32.3kB (sectors 1..63).
Is this still acceptable to you?
Yes/No?
Yes/No? y
Warning: The resulting partition is not properly aligned for best
performance.
Ignore/Cancel? i
Information: You may need to update /etc/fstab.

mkfs.ext3 -L persistence /dev/sdb3
mke2fs 1.43.6 (29-Aug-2017)
/dev/sdb3: Not enough space to build proposed filesystem while setting up superblock


Hopefully someone can help me.
thank you in advance
th-vb

ps:
this is my fdisk command

root@kali:~# fdisk -l
Disk /dev/sda: 698.7 GiB, 750156374016 bytes, 1465149168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EE6B6A78-3798-440A-8172-CFA32D5AB0FC

Device Start End Sectors Size Type
/dev/sda1 2048 1333247 1331200 650M Windows recovery environment
/dev/sda2 1333248 1865727 532480 260M EFI System
/dev/sda3 1865728 2127871 262144 128M Microsoft reserved
/dev/sda4 2127872 1269620447 1267492576 604.4G Microsoft basic data
/dev/sda5 1269620736 1271472127 1851392 904M Windows recovery environment
/dev/sda6 1417781248 1465137151 47355904 22.6G Microsoft basic data




Disk /dev/sdb: 14.3 GiB, 15376000000 bytes, 30031250 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xfe0119ca

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 5996543 5996480 2.9G 17 Hidden HPFS/NTFS
/dev/sdb2 5996544 5997951 1408 704K 1 FAT12
/dev/sdb3 1 63 63 31.5K 83 Linux

Partition table entries are not in disk order.


Disk /dev/loop0: 2.6 GiB, 2821902336 bytes, 5511528 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

_defalt
2017-11-10, 18:34
Create bootable USB using rufus in ISO mode.

broomdodger
2017-11-11, 00:27
This has been fixed it in the weekly W45.

http://cdimage.kali.org/kali-images/kali-weekly/

th-vb
2017-11-11, 14:09
root@kali:~# end=7gb

root@kali:~# read start _ < <(du -bcm kali-linux-2017-W45-amd64.iso | tail -1); echo $start
du: cannot access 'kali-linux-2017-W45-amd64.iso': No such file or directory

I get an error message in this stage? any options?

Now i have written it with rufus and downloaded the iso file from your link.

my usb also only contains one partition?
root@kali:~# fdisk -l
Disk /dev/sda: 7.5 GiB, 8036285952 bytes, 15695871 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x010775ad

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 15695870 15693823 7.5G c W95 FAT32 (LBA)

broomdodger
2017-11-11, 15:24
Did you check the checksum on the downloaded iso?
Is the iso in the root ~ path?

th-vb
2017-11-11, 17:34
I checked the checksum with bodhilinux. (md5)

How can I check if the iso is in the root ~ path

_defalt
2017-11-12, 07:01
Now you have used rufus, everything looks fine to me.

No such file or directory means your iso image is present at somewhere else. You have to specify the complete path. Writing file name is not enough.

th-vb
2017-11-12, 11:48
So if I need to specify the path.

The iso file is probably somewhere on the usb stick. Is that the place to look for the iso file?

_defalt
2017-11-12, 12:57
So if I need to specify the path.

The iso file is probably somewhere on the usb stick. Is that the place to look for the iso file?
The iso is there where you see it.

You have already made a bootable USB using rufus. I don't think following that guide is necessary. It doesn't change anything.

th-vb
2017-11-12, 13:51
Should I look under 'computer' for the already written iso file (used rufus to write)

or should I use a new ISO file and adjust it (and then write it using rufus)

(I have no idea where to look. If I look in other locations->computer->... (i cant seem to find it)


And if I search for it ''kali-linux-2017-W45-amd64.iso" the only hits I have are those from 'media/root/windows/user/downloads

_defalt
2017-11-12, 15:10
If I search for it ''kali-linux-2017-W45-amd64.iso" the only hits I have are those from media/root/windows/user/downloads
You found it.

th-vb
2017-11-12, 15:53
should I rewrite the iso file on my usb using rufus or not? I followed the instructions on kali docs usb kali live adding persistence...?

_defalt
2017-11-12, 16:34
should I rewrite the iso file on my usb using rufus or not? I followed the instructions on kali docs usb kali live adding persistence...?
You have already made it once so it doesn't make any change if you do it twice. If you want to add persistence, follow kali docs.

th-vb
2017-11-12, 19:58
So I tried adding persistence to my usb bootable kali live by running the commands you can find on kali docs adding persistance.

The proces goes as following

1)
fdisk -l

-> I checked the partitions already in place

* on my bootable usb
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 30031249 30029202 14.3G c W95 FAT32 (LBA)

*on my pc (running on windows 10)
Device Start End Sectors Size Type
/dev/sdb1 2048 1333247 1331200 650M Windows recovery enviro
/dev/sdb2 1333248 1865727 532480 260M EFI System
/dev/sdb3 1865728 2127871 262144 128M Microsoft reserved
/dev/sdb4 2127872 1269620447 1267492576 604.4G Microsoft basic data
/dev/sdb5 1269620736 1271472127 1851392 904M Windows recovery enviro
/dev/sdb6 1417781248 1465137151 47355904 22.6G Microsoft basic data

So I want to add persistance to my disk and NOT to my pc

2)
end=7gb
read start _ < <(du -bcm /media/root/Windows/Users/thibv_000/Download/kali-linux-2017-W45-amd64.iso | tail -1); echo $start
parted /dev/sdb mkpart primary $start $end

-> /media/root/ ... is where I can locate the original kali linux is download file
(as you can see I use kali linux 2017 w45)

-> With the last commandline I get this:

root@kali:~# parted /dev/sdb mkpart primary $start $end

Warning: You requested a partition from 2708MB to 7000MB (sectors
5289062..13671875).

The closest location we can manage is 650GB to 650GB (sectors
1269620449..1269620449).
Is this still acceptable to you?
Yes/No? y

Warning: The resulting partition is not properly aligned for best
performance.
Ignore/Cancel? i

Information: You may need to update /etc/fstab.

3)fdisk -l

* on my bootable usb
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 30031249 30029202 14.3G c W95 FAT32 (LBA)

*on my pc (running on windows 10)
Device Start End Sectors Size Type
/dev/sdb1 2048 1333247 1331200 650M Windows recovery enviro
/dev/sdb2 1333248 1865727 532480 260M EFI System
/dev/sdb3 1865728 2127871 262144 128M Microsoft reserved
/dev/sdb4 2127872 1269620447 1267492576 604.4G Microsoft basic data
/dev/sdb5 1269620736 1271472127 1851392 904M Windows recovery enviro
/dev/sdb6 1417781248 1465137151 47355904 22.6G Microsoft basic data
/dev/sdb7 1269620448 1269620448 1 512B Linux filesystem (!!!!!!!)

-> So my question now: as you can see there is an extra partition of 512B Linux filesystem.
Is that correct?
Does the extra partition need to come on my computer (and not my usb)
If the extra partition needs to come alongside my partition on my bootable usb, what should I do different?

-> Can I chose the amount of Bytes myself?

4)
mkfs.ext3 -L persistence /dev/sdb3
e2label /dev/sdb3 persistence

mkdir -p /mnt/my_usb
mount /dev/sdb3 /mnt/my_usb
echo "/ union" > /mnt/my_usb/persistence.conf
umount /dev/sdb3

-> those are the commands linux docs says I need to do next but I those don't work because the partition is created on my pc instead of my USB.


extra info:

* kali-linux-2017-W45-amd64
* written by rufus on my usb stick (16GB)



Thanks in advance