To get support here.
I will come back on this with my new router I just ordered 
The GL.iNets are "just" working, I do not need any support for them right now 
Kind regards, thg
Hi,
so the router arrived today, I just put in my SIM-card and it's working as expected with the original system.
I will test the router in this configuration now for some days, until I will open it to flash OpenWrt on it and will void any warranty.
Kind regards,
thg
You won't void anything, since you dont need to open it.
Read the installation instructions in the link provided.
as far as I understand this:
Install Instructions:
Serial + initramfs:
Place OpenWrt initramfs image for the device on a TFTP in the server's root. This example uses Server IP: 192.168.1.3
Connect serial console (115200,8n1) to X8 connector.
Connect TFTP server to RJ-45 port.
Stop in u-Boot and run u-Boot commands:
I have to open the case and I have to soldier some cables to the serial port?
So warranty is lost for sure?
Kind regards, thg
Which device did you get, I thought it was the Spitz ?
If it was the MF286D, then yes, you'll need serial.
no this not would have been a "cheap" solution ...
Yes, this was your first suggestion, so I ordered it unlocked in UK for round about 80 EUR inkl. shiping and taxes.
And it seems to be a fine device, just needs the correct OS
BTW:
With OpenWrt, is there an App, that you can receive SMS/text messages on the router?
Thanks, kind regards, thg
2 Likes
but, does this mean, that I will loose the SMS-functionalty if I replace the GL.iNet-OpenWrt with the original one from this project in some future?
okay, I have to come back to this
I'm connected via serial console and see boot-screen etc., I've installed the tftp-server with static ip and downloaded the two files Factory- and SysUpgrade-image.
But don't know who to continue.
-
Connect TFTP server to RJ-45 port.
Which one, WAN/LAN1 or LAN2 or any other? -
Stop in u-Boot and run u-Boot commands:
How can I stop the u-Boot in the serial console, to be able to enter commands?
And finaly:
- Please make backup of original partitions, if you think about revert to stock.
How this is done?
Thanks a lot,
kind regards, thg
it's usually LAN.
according to the boot log posted at https://openwrt.org/toh/zte/mf286d#oem_bootlog
Press ESC to abort autoboot in 0 seconds
usually, you need to start hitting the abort key before you see the abort message.
if you fail to communicate with the 286, it might be because of the USB TTL "incompatibility" I mentioned earlier.
Okay, seems to be "WAN/LAN1", at least it's tftp-booting from there.
Yes, that worked perfectly, actually it would have been nice, to find this in the install-documentation for the router.
In the guide is nothing mentioned how to do it, but it is explained in the docu for the MF286R: https://openwrt.org/toh/zte/mf286r
It's not identical, but with this information you get it running.
I will write it down in a an extra post, thanks a lot for the hints,
regards thg
So first, I had to open the router and solder the cables for the serial connection.
I did this a little bit different than decribed in the docs:
Advantage, to connect the serial port, I only have to open the backcover, no screws, an just plug in the cable
1 Like
First step, according to the documentation, should be making a backup of the original firmware, because it's not available for download.
There are some difference to the MF286R-description, the mount of the USB-stick does not work automatically, so has to be done manually, it produces error, but seems to works anyway.
admin@(none):~# mount /dev/sda1 /mnt
NTFS signature is missing.
Failed to mount '/dev/sda1': Invalid argument
The device '/dev/sda1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev[ 590.680448] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
/sda, not /dev/sda1)? Or the other way around?
The partition-layout is different to the one, posted for the MF286R:
admin@(none):~# cat /proc/mtd
dev: size erasesize name
mtd0: 000a0000 00020000 "fota-flag"
mtd1: 00080000 00020000 "0:ART"
mtd2: 00080000 00020000 "mac"
mtd3: 000c0000 00020000 "reserved2"
mtd4: 00400000 00020000 "cfg-param"
mtd5: 00400000 00020000 "log"
mtd6: 000a0000 00020000 "oops"
mtd7: 00500000 00020000 "reserved3"
mtd8: 00800000 00020000 "web"
mtd9: 01d00000 00020000 "rootfs"
mtd10: 01900000 00020000 "data"
mtd11: 03200000 00020000 "fota"
mtd12: 00040000 00010000 "0:SBL1"
mtd13: 00020000 00010000 "0:MIBIB"
mtd14: 00060000 00010000 "0:QSEE"
mtd15: 00010000 00010000 "0:CDT"
mtd16: 00010000 00010000 "0:DDRPARAMS"
mtd17: 00010000 00010000 "0:APPSBLENV"
mtd18: 000c0000 00010000 "0:APPSBL"
mtd19: 00050000 00010000 "0:reserved1"
mtd20: 0041e000 0001f000 "kernel"
mtd21: 00ec6000 0001f000 "ubi_rootfs"
Thus the selection of partitions for backup is different:
admin@(none):~# mkdir /mnt/zte-mf286d
admin@(none):~# for i in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21; do cat /dev/mtd$i > /mnt/zte-mf286d/mtd$i; done
admin@(none):~# ls -l /mnt/zte-mf286d/
-rwxr-xr-x 1 admin admin 655360 Apr 22 10:43 mtd0
-rwxr-xr-x 1 admin admin 524288 Apr 22 10:43 mtd1
-rwxr-xr-x 1 admin admin 26214400 Apr 22 10:43 mtd10
-rwxr-xr-x 1 admin admin 52428800 Apr 22 10:44 mtd11
-rwxr-xr-x 1 admin admin 262144 Apr 22 10:44 mtd12
-rwxr-xr-x 1 admin admin 131072 Apr 22 10:44 mtd13
-rwxr-xr-x 1 admin admin 393216 Apr 22 10:44 mtd14
-rwxr-xr-x 1 admin admin 65536 Apr 22 10:44 mtd15
-rwxr-xr-x 1 admin admin 65536 Apr 22 10:44 mtd16
-rwxr-xr-x 1 admin admin 65536 Apr 22 10:44 mtd17
-rwxr-xr-x 1 admin admin 786432 Apr 22 10:44 mtd18
-rwxr-xr-x 1 admin admin 327680 Apr 22 10:44 mtd19
-rwxr-xr-x 1 admin admin 524288 Apr 22 10:43 mtd2
-rwxr-xr-x 1 admin admin 4317184 Apr 22 10:44 mtd20
-rwxr-xr-x 1 admin admin 15491072 Apr 22 10:44 mtd21
-rwxr-xr-x 1 admin admin 786432 Apr 22 10:43 mtd3
-rwxr-xr-x 1 admin admin 4194304 Apr 22 10:43 mtd4
-rwxr-xr-x 1 admin admin 4194304 Apr 22 10:43 mtd5
-rwxr-xr-x 1 admin admin 655360 Apr 22 10:43 mtd6
-rwxr-xr-x 1 admin admin 5242880 Apr 22 10:43 mtd7
-rwxr-xr-x 1 admin admin 8388608 Apr 22 10:43 mtd8
-rwxr-xr-x 1 admin admin 30408704 Apr 22 10:43 mtd9
admin@(none):~# umount /mnt; sync
Probably some of the partitions are identical too, thus, would not have to be saved twice and a lot of the mtd-files just have "FF", but at least some of them do have reasonable content.
Seems to be, that the ZTE-firmware also is based on OpenWrt:
zte-mf286d> strings mtd9 | grep -i open
ARM OpenWrt FIT (Flattened Image Tree)
ARM OpenWrt Linux-3.14.77
ARM OpenWrt qcom-ipq40xx-ap.dkxx device tree blob
...
zte-mf286d> strings mtd18 | grep -i openwrt
arm-openwrt-linux-uclibcgnueabi-gcc (OpenWrt/Linaro GCC 4.8-2014.04 f53cef1+r49254) 4.8.3
Unfortunately I do not know, if the backup really was successful and unfortunately you can not test it an renew it in a case of error, but at least I found some more interesting content in the files:
zte-mf286d> strings mtd4 | grep -i zte
<value>ZTEDM</value>
<value>ZTEDM</value>
<SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\correlator>20240421194939000021deudmweb1</SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\correlator>
<SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\pkgUri>./FUMO/FirmwareUpdate/DownloadAndUpdate</SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\pkgUri>
<SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\account>zxmdmp</SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\account>
<SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\updatePkgPath>/etc_rw/fota/image.zip</SOFTWARE\ZTE\ZDM\FUMO\./FUMO/FirmwareUpdate\updatePkgPath>
ztedm.conf
<value>ZTE</value>
<value>https://dmusa.ztems.com:443/zxmdmp/dm</value>
<value>ZTEPWD</value>
TOINCREMENT,ViewName TEXT,EnableCWMP INT,URL TEXT,Username TEXT,Password TEXT,PeriodicInformEnable INT,PeriodicInformInterval INT,PeriodicInformTime TEXT,ParameterKey TEXT,ConnectionRequestURL TEXT,ConnectionRequestUsername TEXT,ConnectionRequestPassword TEXT,UpgradesManaged INT,X_ZTE_COM_Interface TEXT,X_ZTE_COM_CertificateEnable INT,X_ZTE_COM_CertificateChain TEXT,CWMPRetryMinimumWaitInterval INT,CWMPRetryIntervalMultiplier INT,SupportedConnReqMethods TEXT,ConnReqXMPPConnection TEXT,ConnReqAllowedJabberIDs TEXT,ConnReqJabberID TEXT,Event TEXT,SessionRetryTimes TEXT,KickURL TEXT,InfoStat INT,InfoDescption INT,AcsStat INT,AcsDescption INT,DataModule INT,StringPrefix TEXT,ReqIP TEXT,BoolMode INT,ChkHost INT,ACSType INT,ACSURLRetry INT,ParamTypeCheck INT,VendorParamPrefix TEXT,CurrentWan TEXT,OldConnectionRequestPort TEXT,AliasBasedAddressing INT,InstanceMode TEXT,AutoCreateInstances INT,ConnectionRequestMode INT,ParamMode INT)
dlna_name=ZTE_DLNA
tr069_Manufacturer=ZTE
https_ServiceURL=https://upgrade.ztems.com/UpdateEntry.aspx
must_have_zte=1
zte_remote_syslog=NO
Password=adminZteMf286
tr069_CommonCmdKey=ZTEHOMEGATEWAY
data_card_mode=ZTE_LTE
tcm_server_url=https://ip.ztetcm.cn/cnip/eservlet
https_ReportServiceURL=https://upgrade.ztems.com/UpdateResultReport.aspx
ztedm.conf
...
zte-mf286d> strings mtd11 | grep -i zte
06:22:24 UP>>[update_control.c:2763]zte_send_message ========196614
00:00:20 UP>>[update_control.c:2941]start zte_dm
00:00:20 UP>>[update_control.c:2941]start zte_dm
19:30:55 UP>>[dua_main.c:176]Enter zte_firmware_update!!!
19:30:56 UP>>[dua_main.c:192]ZTE FOTA FW,zdu_DoUpdate reval=-43
...
Okay, hard-coded passwords in the firmware are not "best practice", but I didn't tested out, for what they are needed.
Next step will be, flashing the latest OpenWrt on the router ...
Not yet successful with the upgrade, some errors in the first step, but it was mentioned, that there could be error messages:
root@OpenWrt:/tmp# ubiattach -m 9
[ 407.421752] ubi0: attaching mtd9
[ 407.719903] ubi0: scanning is finished
[ 407.735015] ubi0: attached mtd9 (name "rootfs", size 29 MiB)
[ 407.735071] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 407.739800] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 407.746467] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 407.753307] ubi0: good PEBs: 232, bad PEBs: 0, corrupted PEBs: 0
[ 407.760092] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[ 407.766344] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 676755884
[ 407.773364] ubi0: available PEBs: 52, total reserved PEBs: 180, PEBs reserved for bad PEB handling: 20
[ 407.782340] ubi0: background thread "ubi_bgt0d" started, PID 2689
UBI device number 0, total 232 LEBs (29458432 bytes, 28.0 MiB), available 52 LEBs (6602752 bytes, 6.2 MiB), LEB size 126976 bytes (124.0 KiB)
root@OpenWrt:/tmp# ubirmvol /dev/ubi0 -N ubi_rootfs
root@OpenWrt:/tmp# ubirmvol /dev/ubi0 -N ubi_rootfs_data
ubirmvol: error!: cannot find UBI volume "ubi_rootfs_data"
error 2 (No such file or directory)
It's 3rd try to install the image and it's still not booting, at least I'm still able to load the initramfs with busybox. First try said, that sysupgrade was successful:
root@OpenWrt:/tmp# sysupgrade -n /tmp/openwrt-23.05.2-ipq40xx-generic-zte_mf286d
-squashfs-sysupgrade.bin
[ 517.011617] ubi: mtd9 is already attached to ubi0
ubiattach: error!: cannot attach mtd9
error 17 (File exists)
Tue Nov 14 13:46:41 UTC 2023 upgrade: Commencing upgrade. Closing all shell sessions.
[ 517.467049] ubi: mtd9 is already attached to ubi0
Watchdog handover: fd=3
- watchdog -
Watchdog did not previously reset the system
Tue Nov 14 13:46:41 UTC 2023 upgrade: Sending TERM to remaining processes ...
Tue Nov 14 13:46:46 UTC 2023 upgrade: Sending KILL to remaining processes ...
[ 528.066712] stage2 (2782): drop_caches: 3
Tue Nov 14 13:46:52 UTC 2023 upgrade: Switching to ramdisk...
Tue Nov 14 13:46:54 UTC 2023 upgrade: Performing system upgrade...
verifying sysupgrade tar file integrity
Volume ID 0, size 24 LEBs (3047424 bytes, 2.9 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "kernel", alignment 1
Volume ID 1, size 32 LEBs (4063232 bytes, 3.8 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 19300352
Volume ID 2, size 152 LEBs (19300352 bytes, 18.4 MiB), LEB size 126976 bytes (124.0 KiB), dynamic, name "rootfs_data", alignment 1
sysupgrade successful
umount: can't unmount /dev: Resource busy
umount: can't unmount /tmp: Resource busy
[ 533.565096] reboot: Restarting system
But system is not starting afterwards:
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00126
S - IMAGE_VARIANT_STRING=DAABANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000021
S - Reset status Config, 0x00000000
S - Core 0 Frequency, 0 MHz
B - 261 - PBL, Start
B - 1339 - bootable_media_detect_entry, Start
B - 1679 - bootable_media_detect_success, Start
B - 1693 - elf_loader_entry, Start
B - 5079 - auth_hash_seg_entry, Start
B - 7228 - auth_hash_seg_exit, Start
B - 579359 - elf_segs_hash_verify_entry, Start
B - 697505 - PBL, End
B - 697529 - SBL1, Start
B - 788400 - pm_device_init, Start
D - 7 - pm_device_init, Delta
B - 789866 - boot_flash_init, Start
D - 52882 - boot_flash_init, Delta
B - 846891 - boot_config_data_table_init, Start
D - 3839 - boot_config_data_table_init, Delta - (419 Bytes)
B - 854368 - clock_init, Start
D - 7555 - clock_init, Delta
B - 866072 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:1
B - 869487 - sbl1_ddr_set_params, Start
B - 874584 - cpr_init, Start
D - 2 - cpr_init, Delta
B - 878966 - Pre_DDR_clock_init, Start
D - 4 - Pre_DDR_clock_init, Delta
D - 13177 - sbl1_ddr_set_params, Delta
B - 892282 - pm_driver_init, Start
D - 2 - pm_driver_init, Delta
B - 962761 - sbl1_wait_for_ddr_training, Start
D - 27 - sbl1_wait_for_ddr_training, Delta
B - 978345 - Image Load, Start
D - 153207 - QSEE Image Loaded, Delta - (299560 Bytes)
B - 1131980 - Image Load, Start
D - 1446 - SEC Image Loaded, Delta - (2048 Bytes)
B - 1142273 - Image Load, Start
D - 247754 - APPSBL Image Loaded, Delta - (507011 Bytes)
B - 1390425 - QSEE Execution, Start
D - 60 - QSEE Execution, Delta
B - 1396612 - SBL1, End
D - 701191 - SBL1, Delta
S - Flash Throughput, 2011 KB/s (809038 Bytes, 402212 us)
S - DDR Frequency, 672 MHz
U-Boot 2012.07 [Chaos Calmer 15.05.1,f53cef1+r49254] (Mar 05 2021 - 15:20:47)
smem ram ptable found: ver: 1 len: 3
DRAM: 256 MiB
machid : 0x8010001
NAND: ID = 302012c
Vendor = 2c
Device = 1
ONFI device found
SF: Detected GD25Q16 with page size 4 KiB, total 2 MiB
ipq_spi: page_size: 0x100, sector_size: 0x1000, size: 0x200000
130 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
machid: 8010001
flash_type: 0
Uaztemain: enter into !
ZTE_InitFotaFlashPara: nand_curr_device=0
zte_getHandOffState: read data=0x20 from 0x0
Press ESC to abort autoboot in 0 seconds
Creating 1 MTD partitions on "nand0":
0x000001800000-0x000003500000 : "mtd=0"
UBI: attaching mtd2 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
Nand Flash error. Status = 12336
NAND page read failed. page: 5781 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 57c1 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5801 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5841 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5881 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 58c1 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5901 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5941 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5981 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c1 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 5a01 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c2 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c3 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c4 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c5 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c6 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c7 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c8 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59c9 status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59ca status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59cb status ffffffb6
Nand Flash error. Status = 12336
NAND page read failed. page: 59cc status ffffffb6
UBI error: vtbl_check: bad CRC at record 21: 0x3beac59f, not 0xf116c36b
UBI error: process_lvol: both volume tables are corrupted
UBI error: ubi_init: cannot attach mtd2
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
(IPQ40xx) #
Any ideas?
What is the correct way, to restore the backup, just "dd if=/.../zte-mf286d/mtd0 of /dev/mtd0" for all mtds?
Thanks a lot,
kind regards, thg
@Leo-PL any ideas ?
Run initramfs again and erase the UBI partition before running sysupgrade to install. It'll format the UBI volume during the process. Stock firmware uses UBI as well and it looks like some remnants of it cause OpenWrt to fail when installed on unclean partition.
2 Likes
how I have to delete the UBI-partition?
I tried to start over with the deletion, but get some errors:
root@OpenWrt:/# ubiattach -m 9
[ 160.744288] ubi0: attaching mtd9
[ 160.965702] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 160.966713] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 160.976990] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 160.988459] ubi0 error: 0xc0708b0c: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read 64 bytes
[ 160.998975] CPU: 3 PID: 2550 Comm: ubiattach Not tainted 5.15.137 #0
[ 161.009351] Hardware name: Generic DT based system
[ 161.015778] Function entered at [<c030d3a8>] from [<c0309784>]
[ 161.020377] Function entered at [<c0309784>] from [<c060cd44>]
[ 161.026193] Function entered at [<c060cd44>] from [<c0708b10>]
[ 161.032007] Function entered at [<c0708b10>] from [<c0709164>]
[ 161.037823] Function entered at [<c0709164>] from [<c070e418>]
[ 161.043640] Function entered at [<c070e418>] from [<c0702e28>]
[ 161.049454] Function entered at [<c0702e28>] from [<c070428c>]
[ 161.055270] Function entered at [<c070428c>] from [<c0495184>]
[ 161.061088] Function entered at [<c0495184>] from [<c0300040>]
[ 161.066903] Exception stack(0xc2a3dfa8 to 0xc2a3dff0)
[ 161.072723] dfa0: 00000003 bea59d7c 00000003 40186f40 bea59d7c bea59d50
[ 161.077849] dfc0: 00000003 bea59d7c 0001273f 00000036 bea59d7c 00000003 00000000 00000000
[ 161.086005] dfe0: 00014f88 bea59c20 00011b50 b6f0873c
[ 161.095958] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 170:2048, read only 64 bytes, retry
[ 161.100133] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 170:2048, read only 64 bytes, retry
[ 161.111459] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 170:2048, read only 64 bytes, retry
[ 161.122918] ubi0 error: 0xc0708b0c: error -74 (ECC error) while reading 64 bytes from PEB 170:2048, read 64 bytes
[ 161.133434] CPU: 3 PID: 2550 Comm: ubiattach Not tainted 5.15.137 #0
[ 161.143813] Hardware name: Generic DT based system
[ 161.150238] Function entered at [<c030d3a8>] from [<c0309784>]
[ 161.154837] Function entered at [<c0309784>] from [<c060cd44>]
[ 161.160652] Function entered at [<c060cd44>] from [<c0708b10>]
[ 161.166469] Function entered at [<c0708b10>] from [<c0709164>]
...
[ 180.526341] ubi0 warning: 0xc0707dc4: error -74 while reading data from PEB 199
[ 180.532717] ubi0 error: 0xc070bbd0: too many erroneous eraseblocks (24)
[ 180.540044] ubi0 error: 0xc070bc00: error 2 while moving PEB 199 to PEB 168
[ 180.546635] ubi0 warning: 0xc070a638: switch to read-only mode
[ 180.553546] CPU: 2 PID: 2551 Comm: ubi_bgt0d Not tainted 5.15.137 #0
[ 180.559446] Hardware name: Generic DT based system
[ 180.565959] Function entered at [<c030d3a8>] from [<c0309784>]
[ 180.570558] Function entered at [<c0309784>] from [<c060cd44>]
[ 180.576373] Function entered at [<c060cd44>] from [<c070bc1c>]
[ 180.582189] Function entered at [<c070bc1c>] from [<c070ab78>]
[ 180.588006] Function entered at [<c070ab78>] from [<c070c8d4>]
[ 180.593819] Function entered at [<c070c8d4>] from [<c0342b14>]
[ 180.599639] Function entered at [<c0342b14>] from [<c0300114>]
[ 180.605452] Exception stack(0xc3427fb0 to 0xc3427ff8)
[ 180.611272] 7fa0: 00000000 00000000 00000000 00000000
[ 180.616400] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 180.624557] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 180.632764] ubi0 error: 0xc070aba4: work failed with error code -5
[ 180.639157] ubi0 error: 0xc070c8f8: ubi_bgt0d: work failed with error code -5
root@OpenWrt:/# ubiattach -m 9
[ 218.893319] ubi: mtd9 is already attached to ubi0
ubiattach: error!: cannot attach mtd9
error 17 (File exists)
root@OpenWrt:/# ubirmvol /dev/ubi0 -N ubi_rootfs
ubirmvol: error!: cannot find UBI volume "ubi_rootfs"
error 2 (No such file or directory)
root@OpenWrt:/# ubirmvol /dev/ubi0 -N ubi_rootfs_data
ubirmvol: error!: cannot find UBI volume "ubi_rootfs_data"
error 2 (No such file or directory)
Thanks, kind regards, thg
Mostly same error as before:
root@OpenWrt:/# ubidetach -m 9
[ 762.860173] ubi0: detaching mtd9
[ 762.861664] ubi0: mtd9 is detached
root@OpenWrt:/# ll /tmp/openwrt-23.05.2-ipq40xx-generic-zte_mf286d-squashfs-sysu
pgrade.bin
-rw-r--r-- 1 root root 7014971 Apr 21 2024 /tmp/openwrt-23.05.2-ipq40xx-generic-zte_mf286d-squashfs-sysupgrade.bin
root@OpenWrt:/# sysupgrade -n /tmp/openwrt-23.05.2-ipq40xx-generic-zte_mf286d-sq
uashfs-sysupgrade.bin
->
[ 993.572653] ubi0: attaching mtd9
[ 993.793528] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 993.794544] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 993.804851] ubi0 warning: 0xc0708acc: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read only 64 bytes, retry
[ 993.816378] ubi0 error: 0xc0708b0c: error -74 (ECC error) while reading 64 bytes from PEB 169:2048, read 64 bytes
[ 993.826793] CPU: 3 PID: 2598 Comm: ubiattach Not tainted 5.15.137 #0
[ 993.837181] Hardware name: Generic DT based system
[ 993.843609] Function entered at [<c030d3a8>] from [<c0309784>]
[ 993.848208] Function entered at [<c0309784>] from [<c060cd44>]
[ 993.854023] Function entered at [<c060cd44>] from [<c0708b10>]
[ 993.859840] Function entered at [<c0708b10>] from [<c0709164>]
[ 993.865654] Function entered at [<c0709164>] from [<c070e418>]
...
[ 1013.581452] Hardware name: Generic DT based system
[ 1013.587968] Function entered at [<c030d3a8>] from [<c0309784>]
[ 1013.592568] Function entered at [<c0309784>] from [<c060cd44>]
[ 1013.598382] Function entered at [<c060cd44>] from [<c070bc1c>]
[ 1013.604199] Function entered at [<c070bc1c>] from [<c070ab78>]
[ 1013.610017] Function entered at [<c070ab78>] from [<c070c8d4>]
[ 1013.615831] Function entered at [<c070c8d4>] from [<c0342b14>]
[ 1013.621649] Function entered at [<c0342b14>] from [<c0300114>]
[ 1013.627461] Exception stack(0xc0fc9fb0 to 0xc0fc9ff8)
[ 1013.633280] 9fa0: 00000000 00000000 00000000 00000000
[ 1013.638402] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1013.646559] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 1013.654735] ubi0 error: 0xc070aba4: work failed with error code -5
[ 1013.661176] ubi0 error: 0xc070c8f8: ubi_bgt0d: work failed with error code -5
ubirmvol: error!: cannot UBI remove volume
error 30 (Read-only file system)
ubirmvol: error!: cannot UBI remove volume
error 30 (Read-only file system)
ubirmvol: error!: cannot UBI remove volume
error 30 (Read-only file system)
ubimkvol: error!: UBI device does not have free logical eraseblocks
cannot create kernel volume
[ 1013.696673] reboot: Restarting system