Looking for a method to enlarge the /dev/mmcblk1 disk to its maximum storage capabilities

Hi,

I managed to save the image from an USB-disk to the internal eMMc-disk. I used the method of the two disks (sd-card in combination with an USB-disk). The image is 4Gb and after copying the unpacked image on the /dev/mmcblk1 will also be 4Gb. I am looking for a method to enlarge the /dev/mmcblk1 disk to its maximum storage capabilities after copying the image? Anyone an idea?

Rene

------------------------------------------------------------------------------------------
Split from How to install Example Image to eMMc.

Unless there was a problem, this expansion happens automatically on first boot. Check "systemctl status expand-on-first-boot" after that first boot.

If you prefer to build a custom image, you could also assign the size upfront, of course.

Hi Jan-k,

Thanks! It seems to work:

1. I made an image (SD-card 4Gb) and the last step I performed: systemctl enable expand-on-first-boot (great suggestion)

2. Then I made an image to a file (Win32DiskImager) and copied this file to an USB-disk.

3. I follow the instructions in the manual 'Install_image_eMMc_V1.0' and copied the image to the eMMc. 

4. Power down the IOT, removed the SD-card and USB-disk and powered up. The result is that /dev/mmcblk1 is now approx. 15 Gb. So your suggestion works fine!

But... (there is always a but). If I install the SD-card again and power up the IOT won't boot up. Why? Because there is a UUID conflict. The eMMC and the SD-card have the same UUID. I can manually change this UUID of course but maybe there is a way to do that automatically. 

Rene

Hi Jan,

Thanks. This works!

I did write my own change of the UUID, via fdisk -> x etc. But after reboot the OS was waiting for the old UUID (I forgot to change the 'u-boot-script' with the new UUID).

Rene