New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#3313 - ath79/mikrotik: initramfs image is missing the nand-utils #8176
Comments
rogerpueyo: However, locally-built initramfs images, generated by only selecting these options:
Target System (Atheros ATH79 (DTS)) ---> Subtarget (MikroTik devices) ---> Target Profile (MikroTik RouterBOARD SXT 5nD r2 (SXT Lite5)) --->
do include the nand-utils package:
root@OpenWrt:/# ls -la /usr/sbin/n*
-rwxr-xr-x 1 root root 20501 Aug 31 09:19 /usr/sbin/nanddump
-rwxr-xr-x 1 root root 8213 Aug 31 09:19 /usr/sbin/nandtest
-rwxr-xr-x 1 root root 24597 Aug 31 09:19 /usr/sbin/nandwrite
lrwxrwxrwx 1 root root 17 Aug 31 09:19 /usr/sbin/ntpd -> ../../bin/busybox
-rwxr-xr-x 1 root root 45 Aug 31 09:19 /usr/sbin/ntpd-hotplug
root@OpenWrt:/# sysupgrade -v -n /tmp/openwrt-ath79-mikrotik-mikrotik_routerboar
d-sxt-5nd-r2-squashfs-sysupgrade.bin
Commencing upgrade. Closing all shell sessions.
Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
Sending TERM to remaining processes ... hostapd wpa_supplicant netifd odhcpd ntpd dnsmasq ubusd urngd logd
Sending KILL to remaining processes ...
Performing system upgrade...
Unlocking kernel ...
Erasing kernel ...
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
Writing data to block 18 at offset 0x240000
[ 69.068982] ubi0: attaching mtd2
[ 69.725009] ubi0: scanning is finished
[ 69.728911] ubi0: empty MTD device detected
[ 69.756713] ubi0: attached mtd2 (name "ubi", size 124 MiB)
[ 69.762455] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 69.769575] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 69.776505] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[ 69.783520] ubi0: good PEBs: 991, bad PEBs: 1, corrupted PEBs: 0
[ 69.789730] ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
[ 69.797197] ubi0: max/mean erase counter: 0/0, WL threshold: 4096, image sequence number: 121828761
[ 69.806548] ubi0: available PEBs: 968, total reserved PEBs: 23, PEBs reserved for bad PEB handling: 19
[ 69.816209] ubi0: background thread "ubi_bgt0d" started, PID 1694
UBI device number 0, total 991 LEBs (127862784 bytes, 121.9 MiB), available 968 LEBs (124895232 bytes, 119.1 MiB), LEB size 129024 bytes (126.0 KiB)
Volume ID 0, size 19 LEBs (2451456 bytes, 2.3 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "none", alignment 1
Volume ID 1, size 21 LEBs (2709504 bytes, 2.5 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1
Set volume size to 119734272
Volume ID 2, size 928 LEBs (119734272 bytes, 114.1 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
[ 74.130939] reboot: Restarting systemt
�
so there might be some problem with the builds system. |
Issue still exists in 22.03. The whole rabbit hole I went down to find this issue: |
rogerpueyo:
The initramfs-kernel.bin image for the ath79/mikrotik mikrotik,routerboard-sxt-5nd-r2 device (SXT Lite 5) is missing the nand-utils package. Therefore, when booting via TFTP (e.g., to install OpenWrt for the first time), the sysupgrade image can not be flashed:
[...] successful boot from TFTP, sysupgrade image uploaded via SCP root@OpenWrt:/# cat /tmp/sysinfo/board_name mikrotik,routerboard-sxt-5nd-r2 root@OpenWrt:/# ls -la /usr/sbin/nand* ls: /usr/sbin/nand*: No such file or directory root@OpenWrt:/# sysupgrade -v -n /tmp/openwrt-ath79-mikrotik-mikrotik_routerboar d-sxt-5nd-r2-squashfs-sysupgrade.bin Commencing upgrade. Closing all shell sessions. Watchdog handover: fd=3 - watchdog - killall: telnetd: no process killed Sending TERM to remaining processes ... hostapd wpa_supplicant netifd odhcpd ntpd dnsmasq ubusd urngd logd Sending KILL to remaining processes ... Performing system upgrade... Unlocking kernel ... Erasing kernel ... /lib/upgrade/do_stage2: line 25: nandwrite: not found tar: write error: Broken pipe removing ubiblock0_1 [ 301.377800] block ubiblock0_1: released Volume ID 0, size 19 LEBs (2451456 bytes, 2.3 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "none", alignment 1 Volume ID 1, size 21 LEBs (2709504 bytes, 2.5 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1 Set volume size to 119734272 Volume ID 2, size 928 LEBs (119734272 bytes, 114.1 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 [ 303.837785] reboot: Restarting systemt �
so the device can't boot, as nothing has been written to NAND.
The text was updated successfully, but these errors were encountered: