I am trying to resize and SD card image following the method here http://www.aoakley.com/articles/2015-10 ... images.php
I am using an Ubuntu VM in Virtual Box on Win10.
On the Pi, booted from an 8G SD card, I purged a few things as suggested and 'du --summarize -BM' run from / reports 3398M.
The VM cannot see the card reader so I created the image using Win32DiskImager.
The issue occurs in gparted.
It reports a 7.34GiB partition with 3.54GiB used, 3.61GiB unused and 194MiB unallocated, which all seem credible.
From the gparted menu, Partition->Resize says maximum size is 7513MiB and Minimum size 3771MiB which is a bit larger than the used figure but seems reasonable.
So I set the new size to gparted's own recommended minimum size (I have also tried setting it slightly bigger) and apply the chane. It fails during resize2fs, with the error shown in the log:
resize2fs -p /dev/loop0 3861504K 00:00:00 ( ERROR )
resize2fs: New size smaller than minimum (1237247)
This minimum is the same as reported by resize2fs when run from the command line:
$ sudo resize2fs -P /dev/loop0
resize2fs 1.42.13 (17-May-2015)
Estimated minimum size of the filesystem: 1237346
But 1237346 4K blocks is 4949384K, much larger than the actual used size reported by du and gparted
If I use resize2fs from the command line, using the minimum size it reports, and then proceed with the remaining steps in the original article to edit the partition table, etc., I end up with an image that is 5G according to windows but it does not boot when written to an SD card and used in the Pi
Can anyone see what the problem is?