Check point L-50 only 96mb storage after install

as the title suggests I have just installed openwrt on a check point L-50 and only have 96mb storage available after the install!!

I followed a guide on this forum that differed slightly from the main install

One thing I didn't do prior to starting out was to do a factory reset on the unit could that be whats caused this???

Here is my boot log

U-Boot 2020.04 (Feb 12 2023 - 23:48:25 +0000)
Check Point L-50

SoC:   Kirkwood 88F6281_A1
Model: Check Point L-50
DRAM:  512 MiB
NAND:  512 MiB
MMC:
Loading Environment from NAND... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet-controller@72000, eth1: ethernet-controller@76000
Hit any key to stop autoboot:  0
ubi0: attaching mtd3
ubi0: scanning is finished
ubi0: attached mtd3 (name "ubi", size 121 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 968, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 993455977
ubi0: available PEBs: 0, total reserved PEBs: 968, PEBs reserved for bad PEB handling: 80
No size specified -> Using max size (2709504)
Read 2709504 bytes from volume kernel to 00800000
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   ARM OpenWrt Linux-5.10.161
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2680716 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.161 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r20028-43d71ad93e) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 Tue Jan 3 00:24:21 2023
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Check Point L-50
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: console=ttyS0,115200
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 510164K/524288K available (5986K kernel code, 599K rwdata, 928K rodata, 1024K init, 211K bss, 14124K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000010] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000045] Switching to timer-based delay loop, resolution 5ns
[    0.000215] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000244] pid_max: default: 32768 minimum: 301
[    0.000439] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000465] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001409] CPU: Testing write buffer coherency: ok
[    0.002624] Setting up static identity map for 0x100000 - 0x10003c
[    0.002890] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.003123] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
[    0.006818] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.006851] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.006972] pinctrl core: initialized pinctrl subsystem
[    0.008788] NET: Registered protocol family 16
[    0.009222] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.010306] thermal_sys: Registered thermal governor 'step_wise'
[    0.010416] cpuidle: using governor ladder
[    0.010740] Feroceon L2: Enabling L2
[    0.010790] Feroceon L2: Cache support initialised.
[    0.023963] No ATAGs?
[    0.073835] SCSI subsystem initialized
[    0.075497] usbcore: registered new interface driver usbfs
[    0.075554] usbcore: registered new interface driver hub
[    0.075605] usbcore: registered new device driver usb
[    0.081764] clocksource: Switched to clocksource orion_clocksource
[    0.082595] NET: Registered protocol family 2
[    0.082837] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.083658] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.083715] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.083771] TCP bind hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.083823] TCP: Hash tables configured (established 4096 bind 4096)
[    0.083911] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.083938] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.084125] NET: Registered protocol family 1
[    0.084160] PCI: CLS 0 bytes, default 32
[    0.089260] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.093268] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.093287] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.094398] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.095881] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.097203] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    0.097251] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    0.097279] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.097298] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.097503] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    0.097524] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.097539] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    0.097552] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.097563] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.097682] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[    0.099182] PCI: bus0: Fast back to back transfers disabled
[    0.099201] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.100496] PCI: bus1: Fast back to back transfers enabled
[    0.100516] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.100701] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.101178] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.102916] printk: console [ttyS0] disabled
[    0.103016] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    0.637650] printk: console [ttyS0] enabled
[    0.642525] Loading iSCSI transport class v2.0-870.
[    0.652363] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xdc
[    0.658755] nand: Samsung NAND 512MiB 3,3V 8-bit
[    0.663431] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.671047] Scanning device for bad blocks
[    0.965998] Bad eraseblock 3824 at 0x00001de00000
[    0.991392] 10 fixed-partitions partitions found on MTD device orion_nand
[    0.998221] Creating 10 MTD partitions on "orion_nand":
[    1.003483] 0x000000000000-0x0000000c0000 : "u-boot"
[    1.011164] 0x0000000c0000-0x000000100000 : "bootldr-env"
[    1.017233] 0x000000100000-0x000007a00000 : "ubi"
[    1.024301] 0x000007a00000-0x000008200000 : "kernel-2"
[    1.030070] 0x000008200000-0x00000f300000 : "rootfs-2"
[    1.037499] 0x00000f300000-0x000016c00000 : "default_sw"
[    1.043910] 0x000016c00000-0x000018400000 : "logs"
[    1.050643] 0x000018400000-0x000018500000 : "preset_cfg"
[    1.056590] 0x000018500000-0x000018600000 : "adsl"
[    1.063284] 0x000018600000-0x000020000000 : "storage"
[    1.088245] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2
[    1.240560] mv88e6085 f1072004.mdio-bus-mii:11: switch 0x1710 detected: Marvell 88E6171, revision 2
[    1.387503] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    2.152550] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:1c:7f:25:44:ac
[    2.161819] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 00:1c:7f:25:44:ad
[    2.170805] i2c /dev entries driver
[    2.181303] orion_wdt: Initial timeout 21 sec
[    2.197764] marvell-cesa f1030000.crypto: CESA device successfully registered
[    2.205858] NET: Registered protocol family 10
[    2.212717] Segment Routing with IPv6
[    2.216478] NET: Registered protocol family 17
[    2.220999] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    2.234295] 8021q: 802.1Q VLAN Support v1.8
[    2.246733] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2
[    3.471799] random: crng init done
[    4.216660] mv88e6085 f1072004.mdio-bus-mii:11 lan3 (uninitialized): PHY [mv88e6xxx-1:00] driver [Generic PHY] (irq=POLL)
[    4.237878] mv88e6085 f1072004.mdio-bus-mii:11 lan8 (uninitialized): PHY [mv88e6xxx-1:01] driver [Generic PHY] (irq=POLL)
[    4.261404] mv88e6085 f1072004.mdio-bus-mii:11 lan4 (uninitialized): PHY [mv88e6xxx-1:02] driver [Generic PHY] (irq=POLL)
[    4.285237] mv88e6085 f1072004.mdio-bus-mii:11 dmz (uninitialized): PHY [mv88e6xxx-1:03] driver [Generic PHY] (irq=POLL)
[    4.300799] mv88e6085 f1072004.mdio-bus-mii:11: configuring for fixed/rgmii-txid link mode
[    4.317236] mv88e6085 f1072004.mdio-bus-mii:11: Link is Up - 1Gbps/Full - flow control off
[    4.335937] mv88e6085 f1072004.mdio-bus-mii:10 lan5 (uninitialized): PHY [mv88e6xxx-2:00] driver [Generic PHY] (irq=POLL)
[    4.357114] mv88e6085 f1072004.mdio-bus-mii:10 lan1 (uninitialized): PHY [mv88e6xxx-2:01] driver [Generic PHY] (irq=POLL)
[    4.383294] mv88e6085 f1072004.mdio-bus-mii:10 lan6 (uninitialized): PHY [mv88e6xxx-2:02] driver [Generic PHY] (irq=POLL)
[    4.404905] mv88e6085 f1072004.mdio-bus-mii:10 lan2 (uninitialized): PHY [mv88e6xxx-2:03] driver [Generic PHY] (irq=POLL)
[    4.429777] mv88e6085 f1072004.mdio-bus-mii:10 lan7 (uninitialized): PHY [mv88e6xxx-2:04] driver [Generic PHY] (irq=POLL)
[    4.443560] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-txid link mode
[    4.454345] mv88e6085 f1072004.mdio-bus-mii:10: configuring for fixed/rgmii-id link mode
[    4.464915] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[    4.474047] DSA: tree 0 setup
[    4.477439] UBI: auto-attach mtd2
[    4.480783] ubi0: attaching mtd2
[    4.488584] mv88e6085 f1072004.mdio-bus-mii:10: Link is Up - 1Gbps/Full - flow control off
[    4.639144] ubi0: scanning is finished
[    4.654589] ubi0: attached mtd2 (name "ubi", size 121 MiB)
[    4.660114] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    4.667047] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    4.673795] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    4.680612] ubi0: good PEBs: 968, bad PEBs: 0, corrupted PEBs: 0
[    4.686659] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[    4.693922] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 993455977
[    4.703016] ubi0: available PEBs: 0, total reserved PEBs: 968, PEBs reserved for bad PEB handling: 80
[    4.712606] ubi0: background thread "ubi_bgt0d" started, PID 594
[    4.719706] block ubiblock0_1: created from ubi0:1(rootfs)
[    4.725253] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[    4.738967] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    4.749076] Freeing unused kernel memory: 1024K
[    4.753933] Run /sbin/init as init process
[    5.074039] init: Console is alive
[    5.077680] init: - watchdog -
[    5.670678] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    5.766146] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.779478] ehci-fsl: Freescale EHCI Host controller driver
[    5.790116] ehci-orion: EHCI orion driver
[    5.794367] orion-ehci f1050000.ehci: EHCI Host Controller
[    5.799923] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    5.807769] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    5.841791] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    5.848452] hub 1-0:1.0: USB hub found
[    5.852880] hub 1-0:1.0: 1 port detected
[    5.862524] ehci-platform: EHCI generic platform driver
[    5.883340] rtc-s35390a 0-0030: registered as rtc0
[    5.889933] rtc-s35390a 0-0030: setting system clock to 2023-02-17T17:38:44 UTC (1676655524)
[    5.914343] mvsdio f1090000.mvsdio: Got CD GPIO
[    5.949731] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    5.967399] init: - preinit -
[    6.271816] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    6.534552] hub 1-1:1.0: USB hub found
[    6.539335] hub 1-1:1.0: 4 ports detected
[    7.324610] mv643xx_eth_port mv643xx_eth_port.1 eth1: link up, 1000 Mb/s, full duplex, flow control disabled
[    7.335629] mv88e6085 f1072004.mdio-bus-mii:10 lan1: configuring for phy/gmii link mode
[    7.346192] 8021q: adding VLAN 0 to HW filter on device lan1
[    7.351950] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    8.422288] mv88e6085 f1072004.mdio-bus-mii:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[    8.431236] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
[   11.583309] UBIFS (ubi0:2): default file-system created
[   11.589415] UBIFS (ubi0:2): Mounting in unauthenticated mode
[   11.620515] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 803
[   11.681884] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[   11.689761] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   11.699738] UBIFS (ubi0:2): FS size: 106315776 bytes (101 MiB, 824 LEBs), journal size 5289984 bytes (5 MiB, 41 LEBs)
[   11.710423] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[   11.717091] UBIFS (ubi0:2): media format: w5/r0 (latest is w5/r0), UUID 88D12379-D446-4FDE-9C37-4A5082FCC02D, small LPT model
[   11.730416] mount_root: overlay filesystem has not been fully initialized yet
[   11.738317] mount_root: switching to ubifs overlay
[   11.752312] urandom-seed: Seed file not found (/etc/urandom.seed)
[   11.896081] mv88e6085 f1072004.mdio-bus-mii:10 lan1: Link is Down
[   11.910245] procd: - early -
[   11.913841] procd: - watchdog -
[   12.560732] procd: - watchdog -
[   12.644115] procd: - ubus -
[   12.814124] procd: - init -
Please press Enter to activate this console.
[   13.681693] kmodloader: loading kernel modules from /etc/modules.d/*
[   13.691132] urngd: v1.0.2 started.
[   13.978303] Loading modules backported from Linux version v5.15.81-0-ge4a7232c917c
[   13.985952] Backport generated by backports.git v5.15.81-1-0-ge1867d55
[   14.140645] PPP generic driver version 2.4.2
[   14.147822] NET: Registered protocol family 24
[   14.200821] kmodloader: done loading kernel modules from /etc/modules.d/*
[   34.505131] mv643xx_eth_port mv643xx_eth_port.1 eth1: link up, 1000 Mb/s, full duplex, flow control disabled
[   34.578109] mv88e6085 f1072004.mdio-bus-mii:10 lan1: configuring for phy/gmii link mode
[   34.608639] 8021q: adding VLAN 0 to HW filter on device lan1
[   34.642098] br-lan: port 1(lan1) entered blocking state
[   34.647366] br-lan: port 1(lan1) entered disabled state
[   34.700212] device lan1 entered promiscuous mode
[   34.704899] device eth1 entered promiscuous mode
[   35.073599] mv88e6085 f1072004.mdio-bus-mii:10 lan2: configuring for phy/gmii link mode
[   35.090869] 8021q: adding VLAN 0 to HW filter on device lan2
[   35.127163] br-lan: port 2(lan2) entered blocking state
[   35.132462] br-lan: port 2(lan2) entered disabled state
[   35.157097] device lan2 entered promiscuous mode
[   35.255679] mv88e6085 f1072004.mdio-bus-mii:11 lan3: configuring for phy/gmii link mode
[   35.278079] 8021q: adding VLAN 0 to HW filter on device lan3
[   35.301492] br-lan: port 3(lan3) entered blocking state
[   35.306788] br-lan: port 3(lan3) entered disabled state
[   35.328397] device lan3 entered promiscuous mode
[   35.403124] mv88e6085 f1072004.mdio-bus-mii:11 lan4: configuring for phy/gmii link mode
[   35.427148] 8021q: adding VLAN 0 to HW filter on device lan4
[   35.460890] br-lan: port 4(lan4) entered blocking state
[   35.466198] br-lan: port 4(lan4) entered disabled state
[   35.489730] device lan4 entered promiscuous mode
[   35.572442] mv88e6085 f1072004.mdio-bus-mii:10 lan5: configuring for phy/gmii link mode
[   35.594275] 8021q: adding VLAN 0 to HW filter on device lan5
[   35.622208] br-lan: port 5(lan5) entered blocking state
[   35.627468] br-lan: port 5(lan5) entered disabled state
[   35.649891] device lan5 entered promiscuous mode
[   35.732429] mv88e6085 f1072004.mdio-bus-mii:10 lan6: configuring for phy/gmii link mode
[   35.754403] 8021q: adding VLAN 0 to HW filter on device lan6
[   35.786211] br-lan: port 6(lan6) entered blocking state
[   35.791474] br-lan: port 6(lan6) entered disabled state
[   35.805242] device lan6 entered promiscuous mode
[   35.870293] mv88e6085 f1072004.mdio-bus-mii:10 lan7: configuring for phy/gmii link mode
[   35.880934] 8021q: adding VLAN 0 to HW filter on device lan7
[   35.903141] br-lan: port 7(lan7) entered blocking state
[   35.908400] br-lan: port 7(lan7) entered disabled state
[   35.922812] device lan7 entered promiscuous mode
[   35.987513] mv88e6085 f1072004.mdio-bus-mii:11 lan8: configuring for phy/gmii link mode
[   36.000490] 8021q: adding VLAN 0 to HW filter on device lan8
[   36.024977] br-lan: port 8(lan8) entered blocking state
[   36.030236] br-lan: port 8(lan8) entered disabled state
[   36.047468] device lan8 entered promiscuous mode
[   36.132644] mv88e6085 f1072004.mdio-bus-mii:11 dmz: configuring for phy/gmii link mode
[   36.147998] 8021q: adding VLAN 0 to HW filter on device dmz
[   36.177841] br-lan: port 9(dmz) entered blocking state
[   36.183053] br-lan: port 9(dmz) entered disabled state
[   36.217640] device dmz entered promiscuous mode
[   37.780861] mv88e6085 f1072004.mdio-bus-mii:10 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[   37.812747] br-lan: port 1(lan1) entered blocking state
[   37.818022] br-lan: port 1(lan1) entered forwarding state
[   37.963350] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready

Looking at this, it seems me that OpenWrt lives completely in mtd2 "ubi". The bootloader loads the kernel from there, and seeing the bootlog

[    4.654589] ubi0: attached mtd2 (name "ubi", size 121 MiB)
...
[    4.719706] block ubiblock0_1: created from ubi0:1(rootfs)
[    4.725253] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
...
[   11.583309] UBIFS (ubi0:2): default file-system created
[   11.589415] UBIFS (ubi0:2): Mounting in unauthenticated mode
...
[   11.730416] mount_root: overlay filesystem has not been fully initialized yet
[   11.738317] mount_root: switching to ubifs overlay

the rootfs and overlay are both in the same "ubi" partition.
I think this is by design. As you can see in the partition table

[    0.998221] Creating 10 MTD partitions on "orion_nand":
[    1.003483] 0x000000000000-0x0000000c0000 : "u-boot"
[    1.011164] 0x0000000c0000-0x000000100000 : "bootldr-env"
[    1.017233] 0x000000100000-0x000007a00000 : "ubi"
[    1.024301] 0x000007a00000-0x000008200000 : "kernel-2"
[    1.030070] 0x000008200000-0x00000f300000 : "rootfs-2"
[    1.037499] 0x00000f300000-0x000016c00000 : "default_sw"
[    1.043910] 0x000016c00000-0x000018400000 : "logs"
[    1.050643] 0x000018400000-0x000018500000 : "preset_cfg"
[    1.056590] 0x000018500000-0x000018600000 : "adsl"
[    1.063284] 0x000018600000-0x000020000000 : "storage"

"ubi" is as big as "kernel-2" + "rootfs-2". So I suppose it replaces the stock "kernel-1" + "rootfs-1". And I also suppose it's still possible to boot the stock firmware from "kernel-2" + "rootfs-2", if you know how to tell u-boot to do so. To use more of the flash you'd need a different partition table. The partition is defined in the dts file written by the implementer of OpenWrt on this box.
I don't know what a Check point L-50 is, but it is possible that one or more of the partitions after "rootfs-2" contains firmware needed by hardware components, and so simply using them might cripple your box.

So you are saying this is a normal amount to expect on this hardware then?

This is the first and only one of these I have used so I have nothing else to compare it with it just seemed a bit low given there's 500mb total.

what does fdisk say ?
is there plenty of free space available ?

I don't know what you mean by that, i'm just a novice.
What command do I need to run and in what environment?

No. I'm saying this is the amount to expect using this implementation of OpenWrt, where you can still boot the original firmware. By enlarging the "ubi" partition by adding "kernel-2" + "rootfs-2" to it, the free size would be around 200MB, but it would overwrite the old firmware. Growing to around 480MB might be possible, depending on the current content of "default_sw" and further partitions. If one of them contains firmware needed for some components, it should be moved to the end as part of the install instructions.
In any case it means that the patches to create the OpenWrt for this box should be adapted. Not a novice task.

Maybe you could put a filesystem like yaffs on "storage" and/or "rootfs-2" when it doesn't contain anything critical, and mount that for extra storage space (for what?). That has as extra advantage that it will survive an upgrade of OpenWrt, as in it's current form it doesn't touch that partitions.

Yes that does sound like something I don't want to attempt.
I just wanted to be sure I wasn't missing some step and have ended up with less than the expected amount of free space is all which as you say it seems like I have got the expected amount.
Thanks

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.