OpenWrt One - can't not mount rootfs after upgrade firmware

I have try to download the snapshot firmware from OpenWrt Firmware Selector, is runing well, but I found that it doesn't have luci...

I want build the firmware from the source, which I can do some custom modification in the future. I have separately tried to download the source code from main branch and OpenWrt-One-sources-dd58ad968a, I haven't changed any code yet. They both have same error result.

upgrade the firmware by serial.

sysupgrade openwrt-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb

then I drop into an endless kernel panic

[    0.915636] spi-nor spi0.0: w25q128 (16384 Kbytes)
[    0.921316] 4 fixed-partitions partitions found on MTD device spi0.0
[    0.927677] Creating 4 MTD partitions on "spi0.0":
[    0.932498] 0x000000000000-0x000000040000 : "bl2-nor"
[    0.938326] 0x000000040000-0x000000100000 : "factory"
[    0.944138] 0x000000100000-0x000000180000 : "fip-nor"
[    0.949607] 0x000000180000-0x000000e00000 : "recovery"
[    0.963064] spi-nand spi1.1: calibration result: 0x3
[    0.968137] spi-nand spi1.1: Winbond SPI NAND was found.
[    0.973470] spi-nand spi1.1: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128
[    0.982039] 2 fixed-partitions partitions found on MTD device spi1.1
[    0.988646] Creating 2 MTD partitions on "spi1.1":
[    0.993479] 0x000000000000-0x000000100000 : "bl2"
[    0.999322] 0x000000100000-0x000008000000 : "ubi"
[    1.081121] ubi0: default fastmap pool size: 50
[    1.085653] ubi0: default fastmap WL pool size: 25
[    1.090453] ubi0: attaching mtd5
[    1.936740] ubi0: scanning is finished
[    1.940572] ubi0 error: ubi_read_volume_table: the layout volume was not found
[    1.947961] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd5, error -22
[    2.091069] OF: /soc/ethernet@15100000/mac@1: #nvmem-cell-cells = 1 found 0
[    2.098071] OF: /soc/ethernet@15100000/mac@1: #nvmem-cell-cells = 1 found 0
[    2.105049] mtk_soc_eth 15100000.ethernet: generated random MAC address 65:74:68:25:64:00
[    2.182115] mtk_soc_eth 15100000.ethernet eth0: mediatek frame engine at 0xffffffc081600000, irq 78
[    2.192065] mtk_soc_eth 15100000.ethernet eth1: mediatek frame engine at 0xffffffc081600000, irq 78
[    2.201885] i2c_dev: i2c /dev entries driver
[    2.208929] mtk-wdt 1001c000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
[    2.217980] NET: Registered PF_INET6 protocol family
[    2.223942] Segment Routing with IPv6
[    2.227625] In-situ OAM (IOAM) with IPv6
[    2.231633] NET: Registered PF_PACKET protocol family
[    2.236924] 8021q: 802.1Q VLAN Support v1.8
[    2.263116] phy phy-soc:usb-phy@11e10000.1: type_sw - reg 0x218, index 0
[    2.270681] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[    2.278012] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[    2.284332] mtk-pcie-gen3 11280000.pcie:      MEM 0x0020000000..0x002fffffff -> 0x0020000000
[    2.629813] mtk-pcie-gen3 11280000.pcie: PCIe link down, current LTSSM state: detect.quiet (0x1)
[    2.638639] mtk-pcie-gen3: probe of 11280000.pcie failed with error -110
[    2.646970] UBI: auto-attach mtd5
[    2.650328] ubi0: default fastmap pool size: 50
[    2.654848] ubi0: default fastmap WL pool size: 25
[    2.659626] ubi0: attaching mtd5
[    3.279806] random: crng init done
[    3.506612] ubi0: scanning is finished
[    3.510441] ubi0 error: ubi_read_volume_table: the layout volume was not found
[    3.517829] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd5, error -22
[    3.524957] UBI error: cannot attach mtd5
[    3.529078] clk: Disabling unused clocks
[    3.533570] /dev/root: Can't open blockdev
[    3.537671] VFS: Cannot open root device "" or unknown-block(0,0): error -6
[    3.544635] Please append a correct "root=" boot option; here are the available partitions:
[    3.552987] 1f00             256 mtdblock0
[    3.552993]  (driver?)
[    3.559509] 1f01             768 mtdblock1
[    3.559513]  (driver?)
[    3.566040] 1f02             512 mtdblock2
[    3.566044]  (driver?)
[    3.572564] 1f03           12800 mtdblock3
[    3.572569]  (driver?)
[    3.579083] 1f04            1024 mtdblock4
[    3.579087]  (driver?)
[    3.585608] 1f05          130048 mtdblock5
[    3.585613]  (driver?)
[    3.592131] List of all bdev filesystems:
[    3.596127]  ext3
[    3.596129]  ext2
[    3.598042]  ext4
[    3.599969]  squashfs
[    3.601883]  f2fs
[    3.604144]
[    3.607535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    3.615782] SMP: stopping secondary CPUs
[    3.619693] Kernel Offset: disabled
[    3.623167] CPU features: 0x0,00000000,00000000,1000400b
[    3.628467] Memory Limit: none
[    3.633742] pstore: backend (ramoops) writing error (-28)
[    3.639131] Rebooting in 1 seconds..

I have lose here many days, hope anyone can help me out.

click the tiny arrow and request build using the URL you posted, the new image will have luci.

as for crashing after you've made customizations, how would we know ?
you made the changes, not us.

I have not change anything. Just build from souce code, try to check it if can run
normally.

Click on the REQUEST BUILD button

and download the firmware images afterwards

that's exactly what OP was told to do 45 mins ago ? :slight_smile:

Visuals FTW :slight_smile:

2 Likes

Its expected to work, firmware selector uses the same source code.

if it doesn't work for you, can you create a new ticket https://github.com/openwrt/openwrt/issues/new/choose ? The form contains bunch of questions and guidelines, please don't ignore them and provide all the information.

1 Like

Thanks!!! New Skills learned. It have upgraded successfully and luci is running now.
But I also want to build from source code. I don't know why my firmware have different behaviour :cry:. I'm trying rebuild again, Hope it work. If not, I will create new ticket in github, and sync information in here. Thank you again.

Forum search is your friend! Covered here already.

It builds fine here as of 20 minutes ago.
34210620 Nov 27 07:03 openwrt-one---build-004-r28200+5-c857145e03-11-27-2024-snapshot-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb

it applies to all snapshots though, not really device specific :slight_smile:

@HIDE-r: https://openwrt.org/releases/snapshot

don't think building's the issue, but running it ..

2 Likes

Thank for your reply. I have seen that ticket, But I not saw any mention about kernel panic. So I create it.

The kernel panic problem seem like is my WSL build environment, because I can successfully bootup the firmware which use my linux environment to build.