Need advise on how to properly expand ext4 setup of OpenWrt

Installing and Using OpenWrt
1

Ok, an OpenWrt install failing after two weeks of running perfectly,
I have done a re install using the latest ISO, and upgraded it.
I am using a Raspberry Pi4B with 8Gb ram and 64Gb SD Card.
OpenWrt 25.12.2 r32802-f505120278 / LuCI openwrt-25.12 branch 26.112.70337~8405d22
And a backup made usin Luci.

I do not know why my last install on this device failed, am only guessing
that maybe adguardhome filled the drive with logs to the extent the OS
could not run.
All I had was boot cycling from the looks of what I saw on a monitor connected
to the Pi.

Could someone tell me what is the correct way to expand the filesystem and partitions in order to make room for adguardhome or any other application to run and write to logs without another disaster happening.
Any expanding or moidications also needs to survive reboots.

Last time I followed the official OpenWrt way of doing it, all went to plan,
but I need to be sure I missed nothing regarding how or what adguardhomes requirements add to the picture.

IMG_20260422_221818
IMG_20260422_2218181920×2567 999 KB

2

If you're not using the 100MB it ships with, leave it as it is, see if it still crashes?

AFAIK AGH doesn't log anything to disk, unless specifically told to.

3

When I saw this using gparted to have a look, 6m of 6m used, it concerned me.

THIS WAS FROM A PREVIOUS INSTALL, that install just stopped working for no apparant reason.

This is why am asking questions regarding expanding the file system and partitions.
This has got to be a problem.

disc-
disc-431×535 30.9 KB

4

/media/abc isn't a default folder in Openwrt, that's something you've created and redirected the logs (or whatever) to.

Or is this where you mounted the disk from the Pi ?

5

As OpenWrt would not boot or at least allow me to log in via Luci or ssh,
I had no option other than put the sd card with OpenWrt into a card reader,
that was the result.
The below was also noted from the command line, all used up 6 of 6
That was after two weeks of solid trouble free operation, and me restarting
adguardhome every four days, this seemed to remove the logs as none were
shown in adguardhomes GUI, I did this to avoid logs building up.

df -H /dev/sda2
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 6.1M 6.1M 0 100% /media/abc/disk

6

Post fdisk -l /dev/sda.

7 
root@OpenWrt:~# fdisk -l /dev/sdafdisk: cannot open /dev/sda: No such file or directory
9

root@OpenWrt:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 59.5G 0 disk
├─mmcblk0p1 179:1 0 64M 0 part /boot
└─mmcblk0p2 179:2 0 104M 0 part /
root@OpenWrt:~#

10

mmcblk0 <> sda, you're comparing apples and oranges.

mmcblk0 matches the default Openwrt layout.

11

My last post showed the partitions on my new fresh install, the one I want to expand correctly in order to avoid future failures.

The other commands are from yesterday, as I stated, from the failed openwrt install,

I put that card in a card reader, and the code posted is what resulted.

No comparing anything except pointing out my old install for some reason had a 6mb

partiton that was full, 100%, this is not good, and could have been the reason for that

openwrt installs failure.

12

Well, we can't help you with that, since it's not the default layout.

Your past failure wasn't because of insufficient disk space, but because of a config error.

If you make the same config error again, it'll only take longer for the same problem to reappear with the extended flash space.

13

I made no config changes, never even logged into the router in two weeks.

It was working, I left home for a few hours, came back to find my phone was not

connected to the router, like it had been doing for two weeks since install.

I touched nothing, was not even there when whatever went wrong did so,

and the router could not update as I had my phone with me so no means to do so,

so it was not an update that caused whatever went wrong.

14

So it took it 2 weeks to fill the space you had, is than an impossible theory ?

Again, you were not running an official OpenWrt image or you had made changes to it.
All bets are off.

15

I was running an official openwrt install. I did install adguardhome, and this is why

I made a thread yesterday seeking input into what could have gone wrong.

I have a GL.inex AX1800 router which also runs openwrt, adguardhome is also

installed on it, and am concerned it too will flounder, because no one seems to know

if or where log files for adguardhome are saved to, and so I have no idea if such files

broke anything or not.

I have a fresh install now, and not wanting to break that.

16

This is from my failed adguard install yesterday, does this look normal, the card was in a reader at the time I took this screenshot.

gparted-3-
gparted-3-899×370 40.4 KB

17

It doesn't look sane, since /boot have been resized for no reason, but the layout looks OK.

18

Yes, I can not explain it at all, I followed the openwrt official intructions to expand the file system and partitions, there were only a few commands and all of them executed with no errors.

Thought I was good to go.

19

Am only after a fresh install, and the below is what I have, is this the default layout

or has something mysteriously changed.

root@OpenWrt:~# lsblk
NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
mmcblk0     179:0    0 59.5G  0 disk 
├─mmcblk0p1 179:1    0   64M  0 part /boot
└─mmcblk0p2 179:2    0  104M  0 part /
root@OpenWrt:~#
21

Seems I'm wrong about /boot on the RPi, this is also 64MB, so I guess it's larger than on x86, for whatever reason.

So it's probably correct.

22

what is the output of:

ubus call system board
df -h
mount