Closed theGOTOguy closed 1 month ago
It looks like the partition table isn't getting adjusted on first boot in your case.
Is your image skipping firstboot in some way?
I don't believe so: you can see from the screenshot that resize2fs_once actually ran. It just didn't do anything.
I did try manually running resize2fs from the CLI, and it said "nothing to do," even though it in fact had plenty to do.
Running raspi-config --expand-rootfs
did correctly resize the root fs.
Note that firstboot is not resize2fs_once. I saw that resize2fs ran, but that's exactly how it would behave if firstboot didn't.
Think of the partition as a container and the filesystem as the content. firstboot edits the partition table to expand the partition table. Then resize2fs_once expands the filesystem to fill the partition. If the partition has not been expanded, there is nowhere for the filesystem to expand into. You can use sudo fdisk -l /dev/mmcblk0
to confirm this.
Oh, that's a good point. I will have to produce a new image to confirm.
Apologies, I produced a vanilla Raspbian Lite build from head and was unable to reproduce this issue.
It must be something specific to my custom build causing firstboot to fail.
Closing unable to reproduce.
I'm not sure when this got broken, but it did correctly work at 9249e146d2e3987adf2ea0e5e19e295d37f3f886 and does not work at dca93d24c7dfb943d84601d2bc4a089f9b66b87f.
Service actually runs, but doesn't detect that a resize needs to happen.
The file system didn't get resized:
Running
raspi-config --expand-rootfs
does correctly resize the root file system, though.