# emonSD 8 GB

**URL:** <https://community.openenergymonitor.org/t/emonsd-8-gb/22756>\
**Category:** emonSD\
**Created:** [5 February 2023 10:25 UTC](https://community.openenergymonitor.org/t/emonsd-8-gb/22756 "2023-02-05T10:25:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Robert.Wall](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/robert.wall/32/38246_2.png) [@Robert.Wall](https://community.openenergymonitor.org/u/Robert.Wall)\
**Post date:** [5 February 2023 13:17 UTC](https://community.openenergymonitor.org/t/emonsd-8-gb/22756/2 "2023-02-05T13:17:38Z")

</div>

I’ve shrunk it to fit an 8 GB card, and written it up - somewhere. It’s tortuous and while 8 GB and for that matter 16 GB cards are hard to find, I can’t understand why the image has to be made for a specific size of card, as it’s a whole lot easier to expand the image than shrink it.

Here’s what I did - it was on a Staff-only topic:

I followed

> <https://askubuntu.com/questions/1174487/re-size-the-img-for-smaller-sd-card-how-to-shrink-a-bootable-sd-card-image>

from the heading:

### Shrinking images on Linux

to the bottom. Where it states:

> Now notice a few things:
> 
> - There is one partition.
> - The partition allocates the entire disk/device/image.

that’s not correct, it showed all the usual partitions. At that stage, I used GParted to resize the 10 GB partition only down to not very much (i.e. so that the total was well below 8 GB, then finally, when it was on the 8 GB SD card, expanded it again with GParted to fill the card).

Those who study the details will warn that the card will wear faster because there’s less free space where wear-levelling can take place, so this is something to bear in mind. If you value your data (rather than just testing/experimenting), then I’d suggest go with the type of card we use in The Shop.

---

_[View the full topic](https://community.openenergymonitor.org/t/emonsd-8-gb/22756)._