32GB mSD; only 6.7GB available to system (Raspberry PI 2 B)

[spook_man]

Hello..
Was happy to see that there was a Kali image for a Raspberry PI 2.

Downloaded the image, used Win32DiskImage to burn to a new 32GB C10 mSD card.

Installation, updates and everything appeared good to go.

Went to install the kali-linux-full metapackage and it downloaded this fine.

During the installation process, it failed due to running out of drive space; wow, that doesn't seem right.

Ran df -h and it shows '/' as only being 6.7GB in size with nothing else showing as unallocated.

Any ideas on why this has occurred and how this can be resolved? Thanks..

[TheStigh]

This is the normal way when you create a bootable media from the images.

What I did was;
- Created the SD Image
- Booted from Live USB
- Used GParted to extend the partition of the SD Card to its max

Voila, full size partition of your SD card.

[spook_man]

Thank you for the reply.

I'm running Windows as my main OS (I know, ugh), but have a VirtualBox Linux install which I was able to use GParted on the SD card to expand the EXT4 partition to all but 1GB of unallocated space.

Now when I boot the system, I'm getting a Kernel Panic error. It states:
Kernel Panic - not syncing : VPS : unable to mount root fs on unknown-block(179,2)

I've re-imaged twice already and tried GParted twice from the virtual and this has occurred twice already.

Any ideas?

Thanks..

This is the normal way when you create a bootable media from the images.

What I did was;
- Created the SD Image
- Booted from Live USB
- Used GParted to extend the partition of the SD Card to its max

Voila, full size partition of your SD card.

[spook_man]

I was able to get GParted live working proper and extended the partition through the bootable USB. After this, put into my Raspberry and it worked fine.

Not entirely sure why the virtual machine caused the kernel panic, but running the live version resolved any issues.

Thanks..