# Module Partitioning **URL:** \ **Category:** WP Series\ **Created:** [September 24, 2019, 2:51pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648 "2019-09-24T14:51:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![jla2040](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jla2040](https://forum.sierrawireless.com/u/jla2040)\ **Post date:** [September 24, 2019, 2:51pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648/1 "2019-09-24T14:51:22Z")
I have a module that’s partitioned as 20 different MTD devices. How do I format a CWE to re-partition and increase the size of MTD 13, UBI device 0, and UBI volume 0\_0 in order to increase the size of the root filesystem? MTD devices being populated at boot: > [0.478822] msm\_nand\_bam\_init: msm\_nand\_bam\_init: BAM device registered: bam\_handle 0xdde0c800 > [0.479065] sps:BAM 0x07984000 (va:0xe0bc0000) enabled: ver:0x19, number of pipes:7 > [0.481695] msm\_nand\_parse\_smem\_ptable: Parsing partition table info from SMEM > [0.481736] msm\_nand\_parse\_smem\_ptable: SMEM partition table found: ver: 4 len: 20 > [0.481761] msm\_nand\_version\_check: nand\_major:1, nand\_minor:5, qpic\_major:1, qpic\_minor:5 > [0.481798] msm\_nand\_scan: NAND Id: 0x2690ac98 Buswidth: 8Bits Density: 512 MByte > [0.481808] msm\_nand\_scan: pagesize: 4096 Erasesize: 262144 oobsize: 256 (in Bytes) > [0.481816] msm\_nand\_scan: BCH ECC: 8 Bit > [0.481830] msm\_nand\_scan: CFG0: 0x290409c0, CFG1: 0x08045d5c > [0.481830] RAWCFG0: 0x2b8401c0, RAWCFG1: 0x0005055d > [0.481830] ECCBUFCFG: 0x00000203, ECCBCHCFG: 0x42040d10 > [0.481830] RAWECCCFG: 0x42000d11, BAD BLOCK BYTE: 0x00000175 > [0.481849] Creating 20 MTD partitions on “7980000.nand”: > [0.481870] 0x000000000000-0x000000280000 : “sbl” > [0.482563] 0x000000280000-0x000000500000 : “mibib” > [0.483161] 0x000000500000-0x000001b80000 : “efs2” > [0.483744] 0x000001b80000-0x000001c80000 : “tz” > [0.484359] 0x000001c80000-0x000001d40000 : “rpm” > [0.484979] 0x000001d40000-0x000001e40000 : “aboot” > [0.485529] 0x000001e40000-0x000002880000 : “boot” > [0.486087] 0x000002880000-0x000002900000 : “scrub” > [0.486660] 0x000002900000-0x000006fc0000 : “modem” > [0.487248] 0x000006fc0000-0x000007140000 : “misc” > [0.487842] 0x000007140000-0x000007bc0000 : “recovery” > [0.488440] 0x000007bc0000-0x000007c80000 : “fota\_none” > [0.489057] 0x000007c80000-0x000009340000 : “recoveryfs” > [0.489663] 0x000009340000-0x000011bc0000 : “system” > [0.490322] 0x000011bc0000-0x000012b40000 : “pad1” > [0.490902] 0x000012b40000-0x000013f80000 : “userrw” > [0.491474] 0x000013f80000-0x000017a40000 : “hdata” > [0.492061] 0x000017a40000-0x00001f000000 : “fota” > [0.492671] 0x00001f000000-0x00001f8c0000 : “cust” lsmtd: > DEVICE MAJ:MIN NAME TYPE SIZE > mtd0 90:0 sbl nand 2.5M > mtd1 90:2 mibib nand 2.5M > mtd2 90:4 efs2 nand 22.5M > mtd3 90:6 tz nand 1M > mtd4 90:8 rpm nand 768K > mtd5 90:10 aboot nand 1M > mtd6 90:12 boot nand 10.3M > mtd7 90:14 scrub nand 512K > mtd8 90:16 modem nand 70.8M > └─ubi1 239:0 68.5M > └─ubi1\_0 239:1 modem dynamic 57.9M > mtd9 90:18 misc nand 1.5M > mtd10 90:20 recovery nand 10.5M > mtd11 90:22 fota\_none nand 768K > mtd12 90:24 recoveryfs nand 22.8M > mtd13 90:26 system nand 136.5M > └─ubi0 240:0 132.2M > ├─ubi0\_0 240:1 rootfs dynamic 90.1M > ├─ubi0\_1 240:2 usrfs dynamic 29.3M > └─ubi0\_2 240:3 cachefs dynamic 2.1M > mtd14 90:28 pad1 nand 15.5M > mtd15 90:30 userrw nand 20.3M > └─ubi2 238:0 19.6M > └─ubi2\_0 238:1 userrw dynamic 8.9M > mtd16 90:32 hdata nand 58.8M > └─ubi3 237:0 56.9M > └─ubi3\_0 237:1 hdata dynamic 50.1M > mtd17 90:34 fota nand 117.8M > mtd18 90:36 cust nand 8.8M > mtd19 90:38 persist nand 7.3M > └─ubi4 236:0 7M > └─ubi4\_0 236:1 persist dynamic 4.1M ---
**Author:** ![anon56110884](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@anon56110884](https://forum.sierrawireless.com/u/anon56110884)\ **Post date:** [September 26, 2019, 6:56pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648/2 "2019-09-26T18:56:38Z")
Hi @jla2040, if you’re using WP76 modems, currently it is not possible. A new AT command is being added to allow customers to resize partitions. Timeline is a few months, depending on which carrier you’re planning to release with. New firmware cannot be used commercially until it is certified with carriers. In the meantime, please reach out to your distributor or Sierra support person and we can certainly work out a solution for you. Thanks. ---
**Author:** ![simon.naegele](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@simon.naegele](https://forum.sierrawireless.com/u/simon.naegele)\ **Post date:** [August 11, 2022, 1:14pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648/3 "2022-08-11T13:14:46Z")
Are there any updates on that? We’d also like to change the size of `lefwkro` on our wp76 devices. Thanks ---
**Author:** ![Patrick.Maheral](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Patrick.Maheral](https://forum.sierrawireless.com/u/Patrick.Maheral)\ **Post date:** [October 13, 2023, 1:45pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648/4 "2023-10-13T13:45:44Z")
I’m in the same position of needing to repartition a WP7607. This is necessary to accommodate the gstreamer packages and a couple others. I’m running Release 17 Generic, but the AT!APPPARTCHG? command just returns error Has there been any movement on this issue in the past year? (EDIT: oops…didn’t realize this was a zombie thread. Should I open a new one?) ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [October 13, 2023, 2:22pm UTC](https://forum.sierrawireless.com/t/module-partitioning/17648/5 "2023-10-13T14:22:07Z")
You need to contact distributor to get a tool to resize partition You might see this to check whether you can have more space for rootfs > [@WP76xx How to Disable UBIFS in R17 Yocto Build](https://forum.sierrawireless.com/t/wp76xx-how-to-disable-ubifs-in-r17-yocto-build/30579/9): > > does it work if you do “make” after “make clean” in order to have a clean build? how about just modifying mdm9x28-image.inc but not modifying swi-mdm9x28.conf? If i just modify mdm9x28-image.inc, the compilation is working on my side.