Results 1 to 6 of 6

Thread: Kali 2.0 USB persistent: old howto no more valid

  1. #1
    Join Date
    2015-Aug
    Posts
    15

    [SOLVED] Kali 2.0 USB persistent: old howto still valid?

    Hi all, I'm trying to setup a persistent USB with Kali 2.0, but http://docs.kali.org/downloading/kal...sb-persistence and http://docs.kali.org/kali-dojo/03-ka...nce-encryption does't seem usable anymore.
    The USB dongle with kali v2 installed by "dd if=... of=/dev/sdb bs=512" boots regularly, but parted and gparted show this error: "Invalid partition table - recursive partition on /dev/sdb."
    No partition table, thus no partitions. The while USB dongle seems "unallocated".
    Any hint?
    Thanks.
    Last edited by ovosodo; 2015-08-15 at 14:56. Reason: Marked SOLVED, the ISO was corrupt

  2. #2
    This is a Kali-Linux support forum - not general IT/infosec help.

    Useful Commands: OS, Networking, Hardware, Wi-Fi
    Troubleshooting: Kali-Linux Installation, Repository, Wi-Fi Cards (Official Docs)
    Hardware: Recommended 802.11 Wireless Cards

    Documentation: http://docs.kali.org/ (Offline PDF version)
    Bugs Reporting & Tool Requests: https://bugs.kali.org/
    Kali Tool List, Versions & Man Pages: https://tools.kali.org/

  3. #3
    Join Date
    2013-Mar
    Posts
    77
    Dojo 2 guide has instructions of what you must do but no commands to use for

    Kali 2 documentation should be updated also...

  4. #4
    Join Date
    2015-Aug
    Posts
    15
    The Dojo 2 guide is very nice, but doesn't solve the issue: by copying the iso to the pendrive, the partition table isn't valid, there isn't "unallocated" space where allocate the persistence partition.
    Code:
    $ sudo dd if=kali-linux-2.0-amd64.iso of=/dev/sdb bs=16M
    197+1 records in
    197+1 records out
    3320840192 bytes (3.3 GB) copied, 167.98 s, 19.8 MB/s
    
    $ sudo parted -l /dev/sdb
    Model: ATA WDC WD10JPVT-24A (scsi)
    Disk /dev/sda: 1000GB
    Sector size (logical/physical): 512B/4096B
    Partition Table: msdos
    Disk Flags: 
    Number  Start   End     Size    Type      File system     Flags
     1      1049kB  983GB   983GB   primary   ext4            boot
     2      983GB   1000GB  16.9GB  extended
     5      983GB   1000GB  16.9GB  logical   linux-swap(v1)
    Error: Invalid partition table - recursive partition on /dev/sdb.
    fdisk doesn't directly show any partition table error, but goes crazy with the size of the added primary partition 1.8 TB:
    Code:
    $ sudo fdisk /dev/sdb
    
    Welcome to fdisk (util-linux 2.25.2).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.
    
    Command (m for help): p
    Disk /dev/sdb: 1.8 TiB, 2000396746752 bytes, 3907024896 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: 0x0a9a1b1a
    
    Device     Boot Start     End Sectors  Size Id Type
    /dev/sdb1  *        0 6486015 6486016  3.1G 17 Hidden HPFS/NTFS
    
    Command (m for help): n
    Partition type
       p   primary (1 primary, 0 extended, 3 free)
       e   extended (container for logical partitions)
    Select (default p): p
    Partition number (2-4, default 2): 
    First sector (6486016-3907024895, default 6486016): 
    Last sector, +sectors or +size{K,M,G,T,P} (6486016-3907024895, default 3907024895): 
    
    Created a new partition 2 of type 'Linux' and of size 1.8 TiB.
    
    Command (m for help): p
    Disk /dev/sdb: 1.8 TiB, 2000396746752 bytes, 3907024896 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: 0x0a9a1b1a
    
    Device     Boot   Start        End    Sectors  Size Id Type
    /dev/sdb1  *          0    6486015    6486016  3.1G 17 Hidden HPFS/NTFS
    /dev/sdb2       6486016 3907024895 3900538880  1.8T 83 Linux
    
    Command (m for help):
    Any hint?

  5. #5
    Join Date
    2015-Aug
    Posts
    1

  6. #6
    Join Date
    2015-Aug
    Posts
    15
    Solved.

    The ISO was corrupt, its sha1 hash was wrong even though qbittorrent checks did not signal any torrent hash discrepancy.
    Mainly only the partition table was corrupt, i downloaded through the official .torrent

    I wrongly trusted the qbittorrent client hash checks.
    Lesson learned: be paranoid and check the hash, and possibly the signature, of any downloaded critical file.

    Thanks to g0tmi1k and 0120 for the useful hints.
    OS

Similar Threads

  1. Howto: Build a Kali MATE Image (The right way)
    By scorpius in forum Building Archive
    Replies: 7
    Last Post: 2016-03-21, 18:19
  2. [HOWTO] Install Kali 1.0.9 in Macbook Air 3,2 A1369
    By miguekun in forum How-To Archive
    Replies: 6
    Last Post: 2014-12-09, 20:39

Posting Permissions

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