Why is Ubi loading unsuccessful

ggsn · 2025-04-05T15:33:46.920Z

My startup log is as follows:

`[    2.018753] ubi0: default fastmap pool size: 95
[    2.023339] ubi0: default fastmap WL pool size: 47
[    2.028326] ubi0: attaching mtd4
[    3.599766] ubi0: scanning is finished
[    3.619005] ubi0: attached mtd4 (name "rootfs", size 239 MiB)
[    3.624812] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    3.631820] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    3.638689] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    3.645674] ubi0: good PEBs: 1908, bad PEBs: 4, corrupted PEBs: 0
[    3.651817] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[    3.659099] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 1727162148
[    3.668281] ubi0: available PEBs: 0, total reserved PEBs: 1908, PEBs reserved for bad PEB handling: 36
[    3.677833] ubi0: background thread "ubi_bgt0d" started, PID 479
[    3.685292] clk: Disabling unused clocks
[    3.691370] UBIFS (ubi0:0): Mounting in unauthenticated mode
[    3.698006] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 481
[    3.831719] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    3.839237] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    3.849205] UBIFS (ubi0:0): FS size: 235540480 bytes (224 MiB, 1855 LEBs), max 2048 LEBs, journal size 9023488 bytes (8 MiB, 72 LEBs)
[    3.861263] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
[    3.867141] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID 0C2A00B3-98B0-4612-BF7E-F8F84F0437E1, small LPT model
[    3.880055] VFS: Mounted root (ubifs filesystem) on device 0:13.
[    3.888563] Freeing unused kernel image (initmem) memory: 1024K
[    3.894853] Run /sbin/init as init process
[    4.072749] init: Console is alive
[    4.076825] init: - watchdog -
[    4.322715] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    4.392802] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    4.413287] init: - preinit -
[    5.114378] Generic PHY 20b4000.ethernet-1:01: attached PHY driver (mii_bus:phy_addr=20b4000.ethernet-1:01, irq=POLL)
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
[    7.358629] mount_root: mounting /dev/root
[    7.387155] mount_root: loading kmods from internal overlay
[    7.414157] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    7.422918] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    7.463493] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    7.575316] block: attempting to load /etc/config/fstab
[    7.589070] block: extroot: not configured
[    7.714316] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    7.771837] mtdblock: MTD device 'kernel' is NAND, please consider using UBI block devices instead.
[    7.880029] mtdblock: MTD device 'boot' is NAND, please consider using UBI block devices instead.
[    7.890108] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    7.901274] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    7.911748] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[    8.036407] mtdblock: MTD device 'dtb' is NAND, please consider using UBI block devices instead.
[    8.062623] mtdblock: MTD device 'env' is NAND, please consider using UBI block devices instead.
[    8.252775] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    8.310244] mtdblock: MTD device 'kernel' is NAND, please consider using UBI block devices instead.
[    8.417946] mtdblock: MTD device 'boot' is NAND, please consider using UBI block devices instead.
[    8.427994] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    8.439117] blk_update_request: I/O error, dev mtdblock0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    8.449593] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[    8.570656] mtdblock: MTD device 'dtb' is NAND, please consider using UBI block devices instead.
[    8.596885] mtdblock: MTD device 'env' is NAND, please consider using UBI block devices instead.
mount: can't find /boot in /etc/fstab
umount: can't unmount /boot: Invalid argument
[    8.725938] urandom-seed: Seeding with /etc/urandom.seed
[    8.790246] procd: - early -
[    8.794530] procd: - watchdog -
[    9.188407] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.277145] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.364603] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.457647] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.545373] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.633684] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.660835] procd: - watchdog -
[    9.670490] procd: - ubus -
[    9.735188] procd: - init -
Please press Enter to activate this console.
[    9.783722] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[    9.970749] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   10.142125] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   10.295058] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   10.457597] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   10.660830] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   11.022910] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   11.210543] kmodloader: loading kernel modules from /etc/modules.d/*
[   11.319486] can: controller area network core
[   11.324216] NET: Registered PF_CAN protocol family
[   11.348751] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   11.361423] can: broadcast manager protocol
[   11.388981] CAN device driver interface
[   11.419809] can: netlink gateway - max_hops=1
[   11.658456] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   11.946092] PPP generic driver version 2.4.2
[   11.978336] NET: Registered PF_PPPOX protocol family
[   12.003732] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   12.050775] kmodloader: done loading kernel modules from /etc/modules.d/*
[   12.199527] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   12.368018] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   12.527877] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   12.689800] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   12.857839] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   13.017945] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   13.206687] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   13.442850] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   13.708305] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   14.032185] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   14.358626] mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.
[   14.607581] urngd: v1.0.2 started.`

Why print mtdblock: MTD device 'rootfs' is NAND, please consider using UBI block devices instead.， And there are no files in/overlay.
the ubi is mounted:
mount|grep ubi
ubi0:rootfs on / type ubifs (rw,noatime,assert=read-only,ubi=0,vol=0)

brada4 · 2025-04-05T17:06:14.265Z

ubus call system board

Did you upgrade (from ...)
or
Fresh install following guide )link...(

ggsn · 2025-04-06T01:58:50.353Z

ubus call system board
{
        "kernel": "5.15.167",
        "hostname": "OpenWrt",
        "system": "ARMv7 Processor rev 5 (v7l)",
        "model": "Test Myboard",
        "board_name": "test,myboard",
        "rootfs_type": "ubifs",
        "release": {
                "distribution": "OpenWrt",
                "version": "23.05.3",
                "revision": "r23809-234f1a2efa",
                "target": "imx/cortexa7",
                "description": "OpenWrt 23.05.3 r23809-234f1a2efa"
        }
}

brada4 · 2025-04-06T03:30:37.401Z

That is not openwrt. Go somewhere else.

psherman · 2025-04-06T03:35:23.416Z

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

psherman · 2025-04-06T15:00:42.677Z

This topic was automatically closed after 11 hours. New replies are no longer allowed.