OpenWrt v21.02.0

[admin]

Found an error in my first v21.02.x builds?
During sysupgrade process:

Code: Select all

Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sun Feb 20 13:10:29 UTC 2022 upgrade: Sending TERM to remaining processes ... logd rpcd odhcpd vdsl_cpe_contro uhttpd ubusd urngd netifd/lib/upgrade/stage2: line 93: can't open /proc/6624/cmdline: no such file
 udhcpc dnsmasq ntpd
Sun Feb 20 13:10:32 UTC 2022 upgrade: Sending KILL to remaining processes ...
[43010.000428] sh (7004): drop_caches: 3
Sun Feb 20 13:10:33 UTC 2022 upgrade: Switching to ramdisk...
Sun Feb 20 13:10:36 UTC 2022 upgrade: Performing system upgrade...
Unlocking kernel ...

Writing from <stdin> to kernel ...
[43017.998804] ubi0: attaching mtd3
[43018.164553] ubi0: scanning is finished
[43018.167120] ubi0 error: 0x803d12c0: the layout volume was not found
[43018.173621] ubi0 error: 0x803d5174: failed to attach mtd3, error -22
ubiattach: error!: cannot attach mtd3
           error 22 (Invalid argument)
ubiformat: mtd3 (nand), size 130678784 bytes (124.6 MiB), 997 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 996 -- 100 % complete
ubiformat: 997 eraseblocks have valid erase counter, mean value is 1
ubiformat: formatting e[43027.289064] ubi0: attaching mtd3
ubiformat: formatting eraseblock 961 -- 96 % comple[43027.455831] ubi0: scanning is finished
ubiformat: formatting eraseblock [43027.472038] ubi0: attached mtd3 (name "ubi", size 124 MiB)
[43027.477046] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[43027.483883] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[43027.490596] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[43027.497394] ubi0: good PEBs: 997, bad PEBs: 0, corrupted PEBs: 0
[43027.503393] ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
[43027.510622] ubi0: max/mean erase counter: 2/2, WL threshold: 4096, image sequence number: 2005002240
[43027.519775] ubi0: available PEBs: 973, total reserved PEBs: 24, PEBs reserved for bad PEB handling: 20
[43027.529209] ubi0: background thread "ubi_bgt0d" started, PID 7594
ubiformat: formatting eraseblock 996 -- 100 % complete
UBI device number 0, total 997 LEBs (128636928 bytes, 122.6 MiB), available 973 LEBs (125540352 bytes, 119.7 MiB), LEB size 129024 bytes (126.0 KiB)
Volume ID 0, size 158 LEBs (20385792 bytes, 19.4 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 105154560
Volume ID 1, size 815 LEBs (105154560 bytes, 100.2 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[43032.401164] reboot: Re

Resulting in the following boot-errors:

Code: Select all

[   12.041364] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[   12.367308] __nand_correct_data: uncorrectable ECC error
[   12.371163] __nand_correct_data: uncorrectable ECC error
[   12.376538] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   12.387698] __nand_correct_data: uncorrectable ECC error
[   12.392754] __nand_correct_data: uncorrectable ECC error
[   12.398118] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   12.408738] Buffer I/O error on dev mtdblock2, logical block 694, async page read
[   12.567797] UBIFS (ubi0:1): default file-system created
[   12.572560] UBIFS (ubi0:1): Mounting in unauthenticated mode
...
[   12.857103] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[   12.863607] UBIFS (ubi0:1): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[   12.873485] UBIFS (ubi0:1): FS size: 103735296 bytes (98 MiB, 804 LEBs), journal size 5160960 bytes (4 MiB, 40 LEBs)
[   12.883995] UBIFS (ubi0:1): reserved for root: 4899673 bytes (4784 KiB)
[   12.890623] UBIFS (ubi0:1): media format: w5/r0 (latest is w5/r0), UUID 02C624B7-11D3-4B77-84EF-72BD9E5285CC, small LPT model
[   12.998610] __nand_correct_data: uncorrectable ECC error
[   13.002464] __nand_correct_data: uncorrectable ECC error
[   13.007849] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   13.018988] __nand_correct_data: uncorrectable ECC error
[   13.024059] __nand_correct_data: uncorrectable ECC error
[   13.029416] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[   13.040048] Buffer I/O error on dev mtdblock2, logical block 694, async page read
...
[   16.791382] kmodloader: done loading kernel modules from /etc/modules.d/*
[   67.384653] __nand_correct_data: uncorrectable ECC error
[   67.388531] __nand_correct_data: uncorrectable ECC error
[   67.394005] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x80700 phys_se                g 1 prio class 0
[   67.405887] __nand_correct_data: uncorrectable ECC error
[   67.410276] __nand_correct_data: uncorrectable ECC error
[   67.415572] blk_update_request: I/O error, dev mtdblock2, sector 5552 op 0x0:(READ) flags 0x0 phys_seg 1                 prio class 0
[   67.426161] Buffer I/O error on dev mtdblock2, logical block 694, async page read
[   72.856988] device eth0 entered promiscuous mode

Now testing new 21.02.2 version...
Also on new version these errors are there.
Weird.
Is it the P2812-F1 or the code?

DG.

[admin]

Another (failed) device is now missing it's NAND ?
After UART & running the .asc file we see the following:

Code: Select all

********************************

U-Boot 2013.10-openwrt5 (Nov 18 2014 - 19:54:58) P-2812HNU-Fx

Board: ZyXEL P-2812HNU-Fx
SoC:   Lantiq VRX288 v1.1
CPU:   125 MHz
IO:    125 MHz
BUS:   125 MHz
BOOT:  UART w/o EEPROM
DRAM:  256 MiB
NAND:  0 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ltq-eth
P-2812HNU-Fx # nand
nand - NAND sub-system

Usage:
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off|partition size
nand write - addr off|partition size
    read/write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
nand read.raw - addr off|partition [count]
nand write.raw - addr off|partition [count]
    Use read.raw/write.raw to avoid ECC and access the flash as-is.
nand erase[.spread] [clean] off size - erase 'size' bytes from offset 'off'
    With '.spread', erase enough for given file size, otherwise,
    'size' includes skipped bad blocks.
nand erase.part [clean] partition - erase entire mtd partition'
nand erase.chip [clean] - erase entire chip'
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub [-y] off size | scrub.part partition | scrub.chip
    really clean NAND erasing bad blocks (UNSAFE)
nand markbad off [...] - mark bad block(s) at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
P-2812HNU-Fx # nand info

P-2812HNU-Fx # nand device

no devices available
P-2812HNU-Fx #

This looks not good at all.
We have to test another device.

DG.

[admin]

3rd F1 box (was running v21.02.0) could nicely be updated to 21.02.2
So my new code has no issues.


Running with Tor 4.6.10 and Privoxy 3.0.33

The other 2 F1's had already hardware issues (no WAN, no Wifi) have to see if we can fix them, hardware replacements.

DG.