Netgear R7000 128MB flash, only 19mb available for OPKG?!

working on reformatting this for easier viewing.

Today I installed OpenWRT OpenWrt 21.02.0-rc2 r16122-c2139eef27 on a Netgear R7000. I notice I only have 19mb available for use with the opkg package manager. I know the R7000 isn't exactly popular around these parts, however I hope I can re-claim the issing space.

For reference, Fresh Tomato 2021.2 has around 90MB free space for OPKG.

Here is a list of terminal printouts for your general information. Let me know if any of you need more info.

 **FDISK PRINTOUT**
root@OpenWrt_R7000:/tmp/opkg-lists# fdisk -l
Disk /dev/mtdblock0: 512 KiB, 524288 bytes, 1024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock1: 1.5 MiB, 1572864 bytes, 3072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock2: 32 MiB, 33554432 bytes, 65536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock3: 4 MiB, 4193792 bytes, 8191 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock4: 28 MiB, 29360128 bytes, 57344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock5: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock6: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock7: 1.5 MiB, 1572864 bytes, 3072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock8: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock9: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock10: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock11: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock12: 256 KiB, 262144 bytes, 512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mtdblock13: 90.75 MiB, 95158272 bytes, 185856 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/ubiblock0_0: 2.3 MiB, 2412544 bytes, 4712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/zram0: 123 MiB, 128974848 bytes, 31488 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

          **MOUNT PRINTOUT**
root@OpenWrt_R7000:/tmp/opkg-lists# mount
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
/dev/ubi0_1 on /overlay type ubifs (rw,noatime,assert=read-only,ubi=0,vol=1)
overlayfs:/overlay on / type overlay (rw,noatime,lowerdir=/,upperdir=/overlay/upper,workdir=/overlay/work)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,mode=600,ptmxmode=000)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,noatime,mode=700)
     **BLKID PRINTOUT**
root@OpenWrt_R7000:/tmp/opkg-lists# blkid
/dev/ubi0_1: UUID="238b6081-acfd-4275-9ac4-1252056cac33" TYPE="ubifs"
/dev/ubi0_0: TYPE="squashfs"
/dev/mtdblock4: UUID="982985851" TYPE="ubi"
/dev/ubiblock0_0: TYPE="squashfs"
/dev/zram0: TYPE="swap"

      **LSPCI PRINTOUT**
root@OpenWrt_R7000:/tmp/opkg-lists# lspci
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 8012 (rev 01)
0000:01:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 8012 (rev 01)
0001:01:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter (rev 03)

            **DF -H PRINTOUT**
root@OpenWrt_R7000:/dev# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                 2.5M      2.5M         0 100% /rom
tmpfs                   123.5M   1012.0K    122.5M   1% /tmp
/dev/ubi0_1              18.5M      4.2M     13.3M  24% /overlay
overlayfs:/overlay       18.5M      4.2M     13.3M  24% /
tmpfs                   512.0K         0    512.0K   0% /dev
2 Likes

Can format your post to allow easy reading.

What is the output of

df -h

My apologies. Ive got the Dyslexia and adult ADHD so it's often really hard to not ramble when I post things. I will try to Re-Format to make it better.

1 Like

Not too sure what they are doing... maybe using mtd13...

Either way... with USB ports... there is extra setup involved... but using extroot-overlay is the simplest way to gain installable area without having to make major OS changes...

[wulfy23] in freshtomato as well as asusmerlin you just press a format button in the gui with the mouse and it formats the empty space on the flash with jffs and then its good. https://wiki.freshtomato.org/doku.php/jffs although they list a typical install on a 128mb device as having 64mb space for jffs and consiquently, opkg, i have found its is literally 90mb on multiple devices. thanks for the suggestion about extroot. It may be easier then begging any more for info on how to sucessfully access the empty free space on my device as it seems like developers in the know are not keen helping :confused:

In fact this is not the first time I have asked on these forums for help accessing unavailable space on a device running OpenWRT. I also inquired about a R6230 I have that also has a 128mbit flash chip and like the R7000 which has 20mb of space, the R6230 at least had 30mb of space available and nearly 100mb inaccessible to opkg. Never got a successful resolution to that either. :confused: :confused: :confused: :confused:

suppenkasper0815, I initially had to use nmrpflash to flash 21.02-rc1 as it was the only way I could get openwrt to load. Any other method errored out. have sence used the gui up upgrade to 21.02-rc2 and that works fine, still only 20mb available for opkg though. there is no wifi performance to speak of, no wifi drivers or related software come pre installed for r7000. thats ok i only wanted to use it for a wired router to use with my 12/60 adsl with vpn for which is works beautifully. I have a quartet of ethernetted AC68U's on Fresh Tomato for wireless access.

Ive seen that suggestion too about flashing back to stock before going to another 3rd party router os. i have flashed many routers in my day between dd merlin, tomato padavan openwrt never found a need to go back to stock before switching. Flashed many models spanning broadcom based hardware mediatek hardware marvell hardware etc I honestly dont know why its recommended to flash to stock before switching to another 3rd party os.

1 Like