Just had this issue. Had just kept the original CHR image size and my dude database filled up all the space.
If you had read the previous posts, you would see that they are trying to resize a non-CHR install of RouterOS that had been installed as a virtual guest of some unspecified hypervisor. CHR is licensed differently than standard x86 RouterOS (since it is expected that you will virtualize it!), so your procedure works fine for CHR. But it will not
work for standard RouterOS.
Standard x86 RouterOS Soft-ID is generated based on disk specs, seemingly including things like make, model, geometry (and/or LBA count), partition table, and filesystem (although MikroTik understandably has never publicly said specifically how this is generated and what particular components are variables in their algorithm). If you change any of these things, the license is void. Standard x86 (non-Routerboard) RouterOS license is permanently bound to the disk it is installed on, and this is to prevent things like somebody attempting to clone a license and re-use it multiple times on multiple machines. But you can remove the disk from one machine and put it in a newer, beefier machine without risking the license. All components can be changed out except for the disk.
Hey, at least it is less finicky than Windows activation!