Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: Kali Live via USB --> not enough storage space

  1. #1
    Junior Member
    Join Date
    Nov 2017
    Posts
    10

    Kali Live via USB --> not enough storage space

    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

  2. #2
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    Create bootable USB using rufus in ISO mode.

  3. #3
    Junior Member
    Join Date
    Dec 2016
    Location
    California
    Posts
    9
    This has been fixed it in the weekly W45.

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

  4. #4
    Junior Member
    Join Date
    Nov 2017
    Posts
    10
    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)
    Last edited by th-vb; 2017-11-11 at 02:13 PM.

  5. #5
    Junior Member
    Join Date
    Dec 2016
    Location
    California
    Posts
    9
    Did you check the checksum on the downloaded iso?
    Is the iso in the root ~ path?

  6. #6
    Junior Member
    Join Date
    Nov 2017
    Posts
    10
    I checked the checksum with bodhilinux. (md5)

    How can I check if the iso is in the root ~ path
    Last edited by th-vb; 2017-11-11 at 06:25 PM.

  7. #7
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    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.

  8. #8
    Junior Member
    Join Date
    Nov 2017
    Posts
    10
    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?

  9. #9
    Senior Member
    Join Date
    Oct 2016
    Location
    /dev/sda
    Posts
    731
    Quote Originally Posted by th-vb View Post
    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.

  10. #10
    Junior Member
    Join Date
    Nov 2017
    Posts
    10
    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
    Last edited by th-vb; 2017-11-12 at 01:57 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •