Gl.inet Velica (B2200) missing storage

I have a gl.inet B2200 ( I Flashed it to version OpenWrt 22.03.5 r20134-5f15225c1e.
When I check the size of the storage, it only gives about 512MB

root@OnzeB2200:~# parted /dev/mmcblk0 print
Model: MMC 8GTF4R (sd/mmc)
Disk /dev/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name         Flags
128     17.4kB  1049kB  1031kB                            bios_grub
 1      1049kB  34.6MB  33.6MB               0:HLOS       hidden, legacy_boot
 2      34.6MB  169MB   134MB                rootfs       hidden
 3      169MB   706MB   537MB   f2fs         rootfs_data

That's the same as in the documentation.

How can I increase the storage to the 8GB.

The first question would be, do you need that much on your overlay?
…or would it suffice to add a data partition with the rest of the disk (add another partition, format and use blockd to mount it somewhere, e.g. /srv/ or /opt/, whatever you're looking for - non-overlapping with the normal rootfs)?

The wiki has a guide to extend/ resize the overlay for x86 systems, the same approach probably applies here, but if you don't need to change the partitioning (which comes with a considerable risk), it's better to leave it.

At the end of the day, it's still a router and ~32 MB kernel + ~134 MB rootfs + ~537 MB overlay is plenty, especially with OpenWrt - I can't imagine that much that could fill that up (it's not a file server, after all).

How did you flash your B2200? I understand there are more details to that, as explained here in post #2 and post #7.
I have Velica myself, but still haven't gotten around to flashing it with OpenWrt...

I don't need the full 8G, but I run a step-ca on it, and Telegraf for monitoring. Both are large binaries, and the step DB keeps growing too.

Just adding an extra partition like slh suggests is more future-proof. You can still use the default OpenWrt images, no need to start tinkering with your DTS, building your own images etc.

If your hardware has USB I'd rather put your database on external storage if it sees frequent writes. Last thing you want is to wear out your internal storage.

1 Like

This is exactly how the mount points look like on Velica with OEM setup: