the 104MiB default come from the NAND version? As there is only 128mb Nand and 32mb NOR.
or is that separate from the emmC image/config?
I think 768MiB would help a lot as current Snapshot builds only have around 30mb Free space.
Especially since most OPKG packages tell WAY to low values for Storage they need.
You cannot directly boot from it,but you can have rootfs from it. Uboot does not yet support pcie controller. If this is supported,kernel can be loaded from there too
Extend software free space, about 100MB to eMMC 8GB.
Completed environment:
ă»Boot from SPI-Nand
ă»eMMC 8GB or nvme for â/overlayâ area.
ă»If expand using this method, there is no problem even if restart the BPI-R3.
There is a benchmark for nvme with âhdparmâ, but no benchmark for SPI-Nand.
nvme benchmark [KP230 Gen3.0 Ă 4]
root@BPI-R3:~# hdparm -t --direct /dev/nvme0n1
/dev/nvme0n1:
Timing O_DIRECT disk reads: 1908 MB in 3.00 seconds = 635.47 MB/sec
Can get a benchmark by booting with an SD card and running âhdparmâ on SPI-Nand, but since are already using to, it may be a little impossible.
But, Iâve used it with both SPI-Nand and eMMC and canât feel any difference.
I donât think there will be any problems in practice.
However, SPI-Nand is probably slower than eMMC in terms of Bus speed specifications.
I have only tested it with eMMC and mvne, but it should work.
Is a ext4 formatted USB memory are visible with âlsusb -tâ?
Is it recognized by âblock infoâ and âblcok detectâ?
Are the following packages installed?
Depending on the startup method(SPI-Nand / eMMC), whether Extroot is possible or not may be different�
It might be better to extend eMMC using the method described in this thread using âpartedâ.
root@OpenWrt:/# resize2fs /dev/loop0
resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Invalid argument while trying to open /dev/loop0
Couldn't find valid filesystem superblock.
Should the command arguments be modified for BPi-R3?
Thanks,
Navi
PS: Using Current stable release - OpenWrt 23.05.0 on BPi-R3, Want to use docker to run Home assistant on the device, but I am running out of space when installing docker. BPi-R3 is booting from emmmc and I have already used cfdisk to repartition the free space of 7.1gb and it shows up in the software pane of open-Wrt.
Since OpenWrt is now 23.05, I actually tried it.
I tried changing various settings, but it didnât work.
It seems to be difficult to boot from eMMC and assign /overlay to the free space on the eMMC.
I decided to boot with SPI-Nand as usual and assign /overlay to the entire eMMC.
P.S.
There is no problem if you use HA with the default entity retention of 10 days, but if you want to retain entities for more over 10 days ago, recommend to assign to NVMe SSD.
If something happens to the eMMC, it cannot be easily replaced.
Thanks for the pointers, I think I am going to first test out the setup on eMMC and then buy and install a M.2 NVMe SSD after I figure out best setup for cooling the SSD. Now for me the next step is to boot from NAND and use resize.f2fs /dev/mmcblk0p66 command to extend the overlay to entire 8GB eMMC. Since I am still new to using Linux CLI commands, I am not sure how to partially extend the overlay using resize.f2fs command or I would have only extended the overlay to 2GB to match the RAM.