Hello.
I’m trying to test Volumio on x86 system. Version: volumio-2.411-2018-06-15-x86.img
IMG size is 4 089 446 400 bytes. It’s a little bit more than 4Gb SD card size (which is 3 965 190 144 bytes).
I’ve read already that size of IMG is because of how updater mechanism working.
But can’t it be really just a bit smaller to fit 4Gb SD card?
Is it possible to shrink some of partitions inside IMG without breaking everything?
If no - can I somehow (and how?) to build image myself without updater mechanism?
A newly flashed image size is not 4Gb to start with.
On first boot, the 3rd partition is resized to the maximum of the medium it has been flashed to.
So, in principle, a 4Gb SD card should not be a problem, unless your card was not the one you flashed to image to.
So, to be able to help, could you please explain, what problem you ran into and how?
@gkkpch: the latest downloadable image size for x86 IS larger than 4 GBytes. The zipped file is 647.427.091 bytes, but the unzipped .img file is 4.089.446.400 bytes BEFORE expansion, so it doesn’t fit in a 4 GBytes SD card.
oops, you’re absolutely right, I stand corrected 
I’ll have a look at this issue, I presume the initial data partition can be reduced a little.
Testing in my dev environment as we speak.
When OK, a link to a new version will be published here and hopefully released before the end of coming weekend.
- Gé -
here we go
Standard version (to be released soon) volumio-2.415-2018-07-08
For those who rather use a dev version with kernel 4.16: [link removed, a new version will be published soon in Volumio Development/Development Talks/“Next X86” section.