# Unable to extend internal memory

**URL:** <https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353>\
**Category:** Access Issues\
**Created:** [18 June 2023 01:58 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353 "2023-06-18T01:58:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shoobledoops](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@Shoobledoops](https://syncloud.discourse.group/u/Shoobledoops)\
**Post date:** [18 June 2023 01:58 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/1 "2023-06-18T01:58:22Z")

</div>

Hi there,

I’ve freshly installed syncloud-amd64-uefi-23.06.img.xz to my server using Etcher, activated it, and installed updates.

I’ve referenced this wiki page: [Home · syncloud/platform Wiki · GitHub](https://github.com/syncloud/platform/wiki/Boot-from-SATA) but when I try to use the Extend button in the Internal Memory menu the loading screen pops up and then just goes away and still shows: `Partition - 3G`.

I’ve also tried using the `/snap/platform/current/bin/boot_extend.sh` command over SSH, but I get the following output:

```auto
/snap/platform/current/bin/boot_extend.sh
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 227099469 blocks) or continue with the current setting? 
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 227099469 blocks) or continue with the current setting? 
/snap/platform/current/bin/boot_extend.sh: line 13: awk: command not found
GPT PMBR size mismatch (7342178 != 234441647) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.

Welcome to fdisk (util-linux 2.33.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

GPT PMBR size mismatch (7342178 != 234441647) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.

Command (m for help): 

Command (m for help): 
Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: ADATA SP550     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8948DE21-EA63-40ED-8B30-7965616EEE40

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 7342080 6291457 3G Linux filesystem

Command (m for help): Partition number (1,2, default 2): 
Partition 2 has been deleted.

Command (m for help): Disk /dev/sda: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: ADATA SP550     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8948DE21-EA63-40ED-8B30-7965616EEE40

Device Start End Sectors Size Type
/dev/sda1 2048 1050623 1048576 512M EFI System

Command (m for help): Partition number (2-128, default 2): Value out of range.
Partition number (2-128, default 2): First sector (1050624-234441614, default 1050624): Last sector, +/-sectors or +/-size{K,M,G,T,P} (1050624-234441614, default 234441614): Value out of range.
Last sector, +/-sectors or +/-size{K,M,G,T,P} (1050624-234441614, default 234441614): Last sector, +/-sectors or +/-size{K,M,G,T,P} (1050624-234441614, default 234441614): Last sector, +/-sectors or +/-size{K,M,G,T,P} (1050624-234441614, default 234441614): Last sector, +/-sectors or +/-size{K,M,G,T,P} (1050624-234441614, default 234441614): 
Created a new partition 2 of type 'Linux filesystem' and of size 111.3 GiB.
Partition #2 contains a ext4 signature.

Command (m for help): 
Warning: Not all of the space available to /dev/sda appears to be used, you can fix the GPT to use all of the space (an extra 227099469 blocks) or continue with the current setting? 
resize2fs 1.44.5 (15-Dec-2018)
The filesystem is already 786432 (4k) blocks long. Nothing to do!

```

Is there something I’ve missed, or misconfigured?

Any help would be appreciated 🙂

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [18 June 2023 20:47 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/2 "2023-06-18T20:47:27Z")

</div>

> [@Shoobledoops](#):
>
> ` awk: command not found`

looks like our latest image lost awk tool, as a workaround could you install it and see if that helps?

```auto
apt install awk

```

Then run extend again:

```auto
/snap/platform/current/bin/boot_extend.sh

```

---

<div class="post-metadata">

**Author:** ![Shoobledoops](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@Shoobledoops](https://syncloud.discourse.group/u/Shoobledoops)\
**Post date:** [19 June 2023 08:06 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/3 "2023-06-19T08:06:45Z")

</div>

Apt install gave me options for original-awk, mawk, and gawk. I went with gawk, and that seems to have worked.

Thank you for the help 🙂

---

<div class="post-metadata">

**Author:** ![boris](https://avatars.discourse-cdn.com/v4/letter/b/74df32/32.png) [@boris](https://syncloud.discourse.group/u/boris)\
**Post date:** [19 June 2023 08:19 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/4 "2023-06-19T08:19:56Z")

</div>

Yes sorry I realised it is a bit more broken than I thought, just published a fixed image, could you try that?  
[https://github.com/syncloud/image/releases/download/23.06.1/syncloud-amd64-uefi-23.06.1.img.xz](https://github.com/syncloud/image/releases/download/23.06.1/syncloud-amd64-uefi-23.06.1.img.xz)

---

<div class="post-metadata">

**Author:** ![Shoobledoops](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@Shoobledoops](https://syncloud.discourse.group/u/Shoobledoops)\
**Post date:** [19 June 2023 08:22 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/5 "2023-06-19T08:22:31Z")

</div>

Sure thing. I won’t be able to tonight, but I’ll try to get to it in the next couple days.

---

<div class="post-metadata">

**Author:** ![Shoobledoops](https://avatars.discourse-cdn.com/v4/letter/s/96bed5/32.png) [@Shoobledoops](https://syncloud.discourse.group/u/Shoobledoops)\
**Post date:** [20 June 2023 04:01 UTC](https://syncloud.discourse.group/t/unable-to-extend-internal-memory/353/6 "2023-06-20T04:01:15Z")

</div>

That new build seems to be working well. I was able to get it installed, extended, and updated through the UI without any issues.
