Добрый день!
Контроллер был настроен и работал на объекте, спустя некоторое время после различных работы перестал загружаться. Возможно, из-за периодического включения и выключения питания электромонтажником - не уверен. Прикрепляю вывод дебажной консоли.
[com COM4] (2025-12-29_121806) COM4 (Устройство с последовательным интерфейсом USB (COM4)).log (41,3 КБ)
Вот основные ошибки. После последней контроллер ждёт перезагрузки по watchdog и перезагружается:
Перепрошивать еще не пробовал. Хочу понять причину сбоя и, если возможно, восстановить контроллер с выполненными настройками. Подскажите, пожалуйста, наиболее грамотные действия для восстановления.
Добрый день.
Вполне возможно. Если многократно прерывать выполнение восстановления ФС при загрузке - да, может быть.
Ну, я бы рекомендовал запустить проверку ФС на ошибки, как и рекомендуется в выводе.
То есть e2fsck -D в однопользовательском режиме.
То есть Wiren Board 6…8: Восстановление пароля пользователя root — Wiren Board по 3 пункт включительно.
Запустил. Вот такой вывод (просто информация, как пользоваться):
Запустил вот в таком виде, ругается на отсутствие mtab файла:
e2fsck /dev/mmcblk0p2
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/mmcblk0p2 is mounted.
e2fsck: Device or resource busy while trying to open /dev/mmcblk0p2
Filesystem mounted or opened exclusively by another program?
Добрый день!
Команда e2fsck -f -y /dev/mmcblk0p2 верна, однако ее нельзя запускать на примонтированном разделе. Так как это корневой раздел, его невозможно размонтировать в обычном режиме работы.
Я уточню у коллег, как правильно войти в emergency mode для выполнения проверки.
1 лайк
Уточнил вам потребуется данная ссылка для размонтирования раздела, а далее выполнить проверку.
пробую в разных вариантах. Если после пункта 3 я сразу перехожу к пункту 9, то вывод следующий:
sync
umount /mnt/data
umount: /mnt/data: not mounted.
umount /
e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/mmcblk0p2 is mounted.
e2fsck: Device or resource busy while trying to open /dev/mmcblk0p2
Filesystem mounted or opened exclusively by another program?
Если пробую еще выполнить пункт 5 (смонтировать раздел), то получаю по-прежнему ошибку файловой системы.
mount -n -o remount,rw /dev/mmcblk0p2 /
[ 8.034344] EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
[ 8.044317] EXT4-fs (mmcblk0p2): re-mounted e7c1a723-b0d7-48ac-aa23-ae5513445077 r/w. Quota mode: none.
e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/mmcblk0p2 is mounted.
e2fsck: Device or resource busy while trying to open /dev/mmcblk0p2
Filesystem mounted or opened exclusively by another program?
[ 33.762126] dcdc4: disabling
sync
umount /
[ 49.343641] EXT4-fs (mmcblk0p2): re-mounted e7c1a723-b0d7-48ac-aa23-ae5513445077 ro. Quota mode: none.
e2fsck -f -y /dev/mmcblk0p2
e2fsck 1.46.2 (28-Feb-2021)
ext2fs_check_if_mount: Can’t check if filesystem is mounted due to missing mtab file while determining whether /dev/mmcblk0p2 is mounted.
e2fsck: Device or resource busy while trying to open /dev/mmcblk0p2
Filesystem mounted or opened exclusively by another program?
Попробовать какой-то другой вариант?
Я бы посоветовал сейчас просто скопировать нужное, то есть конфиги, скрипты.
Ну и починить ФС потом.
Тут просто про то что отсутствует /etc/mtab и не может быть проверен том на то что смонтирован.
А как их скопировать через дебаг? есть инструкция? Или можно как-то загрузить систему с внешнего устройства?
Попробую все же перепрошить со сбросом, отпишу результат
Сброс тоже корректно не выполняется.
Действовал согласно инструкции Обновление прошивки контроллера Wiren Board 8 — Wiren Board
Пробовал сначала перепрошить через Debug Network - не появлялся накопитель WB UPDATE.
Записал файл прошивки на флешку. Длинный продолжительный звук, четыре сигнала о подтверждении, процесс пошел и снова ошибки с ФС:
Factory reset is confirmed!
===============================================================================
Tue Dec 30 10:21:34 UTC 2025: started update from /disk/wb_update_FACTORYRESET.fit
Description: WirenBoard firmware update
Compatible device: wirenboard,wirenboard-8xx
Firmware version: 202512290931
Firmware compatible: +single-rootfs +fit-factory-reset +force-repartition +repartition-ramsize-fix +fit-immutable-support +wb8-debug-network-update-fix +wrong-ab-layout-fix +update-from-cloud
Release name: wb-2507
Release suite: stable
Release target: wb8/bullseye
Release repo prefix:
Time of creation: Mon Dec 29 09:32:11 UTC 2025
Checking SHA1 hash of install
PROGRESS: 0%
SHA1 hash of install ok
Requested factory reset will be performed by firmware itself
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.00556717 s, 2.9 MB/s
Firmware seems to be compatible with this controller
Extracting install script
Running install script
Console logging enabled; tempfile /tmp/tmp.6FOTFF, final file /disk/wb-console.log will be written on exit
Reading uboot env offset/size from device tree…
Could not read uboot-env-offset from device tree. Keeping old fw_env.config from rootfs
Extend tmpfs size to whole RAM
Remount tmpfs in /tmp with size=3934M
Maybe update factoryreset.fit to fix tmpfs size issue at 512M RAM (with emmc update)
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.0056095 s, 2.9 MB/s
Firmware seems to be compatible with this controller
Wiping data partition (factory reset)
[ 17.988932] EXT4-fs (mmcblk0p6): recovery complete
[ 17.994124] EXT4-fs (mmcblk0p6): mounted filesystem 39c4c404-f354-4163-bd3c-657fcd83db1d r/w with ordered data mode. Quota mode: none.
[ 19.077601] random: crng init done
[ 19.168593] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591301: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[ 19.183490] EXT4-fs error (device mmcblk0p6): htree_dirblock_to_tree:1082: inode #1591301: comm rsync: Directory block failed checksum
[ 19.195885] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591301: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[ 19.210747] EXT4-fs error (device mmcblk0p6): ext4_empty_dir:3090: inode #1591301: comm rsync: Directory block failed checksum
rsync: [generator] readdir(“/mnt/data/root/.npm/_cacache/content-v2/sha512/a7/6b”): Bad message (74)
cannot delete non-empty directory: root/.npm/_cacache/content-v2/sha512/a7/6b
cannot delete non-empty directory: root/.npm/_cacache/content-v2/sha512/a7
cannot delete non-empty directory: root/.npm/_cacache/content-v2/sha512/a7
cannot delete non-empty directory: root/.npm/_cacache/content-v2/sha512
cannot delete non-empty directory: root/.npm/_cacache/content-v2/sha512
cannot delete non-empty directory: root/.npm/_cacache/content-v2
cannot delete non-empty directory: root/.npm/_cacache/content-v2
cannot delete non-empty directory: root/.npm/_cacache
cannot delete non-empty directory: root/.npm/cacache
cannot delete non-empty directory: root/.npm
cannot delete non-empty directory: root/.npm
[ 19.805687] EXT4-fs error (device mmcblk0p6): htree_dirblock_to_tree:1082: inode #1590931: comm rsync: Directory block failed checksum
[ 19.817988] EXT4-fs error (device mmcblk0p6): ext4_empty_dir:3090: inode #1590931: comm rsync: Directory block failed checksum
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/type/ts-types/prototype”): Bad message (74)
cannot delete non-empty directory: root/.node-red/node_modules/type/ts-types/prototype
cannot delete non-empty directory: root/.node-red/node_modules/type/ts-types
cannot delete non-empty directory: root/.node-red/node_modules/type/ts-types
cannot delete non-empty directory: root/.node-red/node_modules/type
cannot delete non-empty directory: root/.node-red/node_modules/type
[ 20.188886] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591303: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
[ 20.203855] EXT4-fs error (device mmcblk0p6): htree_dirblock_to_tree:1082: inode #1591303: comm rsync: Directory block failed checksum
[ 20.216131] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591303: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
rsync: [generato[ 20.230994] EXT4-fs error (device mmcblk0p6): ext4_empty_dir:3090: inode #1591303: comm rsync: Directory block failed checksum
r] readdir(“/mnt/data/root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub/node_modules/.bin”): Bad message (74)
cannot delete non-empty directory: root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub/node_modules/.bin
cannot delete non-empty directory: root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub/node_modules
cannot delete non-empty directory: root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub/node_modules
cannot delete non-empty directory: root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub
cannot delete non-empty directory: root/.node-red/node_modules/node-red-contrib-mqtt-dynamicsub
[ 20.823529] EXT4-fs error (device mmcblk0p6): ext4_lookup:1855: inode #1591022: comm rsync: iget: checksum invalid
rsync: [generato[ 20.834860] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591002: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
r] readlink_stat[ 20.850495] EXT4-fs error (device mmcblk0p6): htree_dirblock_to_tree:1082: inode #1591002: comm rsync: Directory block failed checksum
("/mnt/data/root[ 20.864148] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591002: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
/.node-red/node[ 20.880139] EXT4-fs error (device mmcblk0p6): ext4_empty_dir:3090: inode #1591002: comm rsync: Directory block failed checksum
modules/es5-ext/[ 20.893563] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591000: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
boolean") failed[ 20.909040] EXT4-fs error (device mmcblk0p6): htree_dirblock_to_tree:1082: inode #1591000: comm rsync: Directory block failed checksum
: Bad message (7[ 20.922553] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1591000: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
rsync: [generator] readdir(“[ 20.940995] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1590996: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
/mnt/data/root/.[ 20.956393] EXT4-fs warning (device mmcblk0p6): ext4_dirblock_csum_verify:405: inode #1590996: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.
node-red/node_modules/es5-ext/string/raw”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/string/from-code-point”): Bad message (74)
rsync: [generator] readlink_stat(“/mnt/data/root/.node-red/node_modules/es5-ext/string/#/ends-with”) failed: Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/string/#/repeat”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/roo@iterator/.node-red/node_modules/es5-ext/string/#/code-point-at”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/string/#/@@iterator”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/reg-exp/#”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/promise/#/finally”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/object/set-prototype-of”): Bad message (74)
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/raw
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/from-code-point
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/#/repeat
cannot delete n@iteratorn-empty directory: root/.node-red/node_modules/es5-ext/string/#/code-point-at
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/#/@@iterator
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/string
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/reg-exp/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/reg-exp
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/reg-exp
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/promise/#/finally
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/promise/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/promise/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/promise
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/promise
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/object/set-prototype-of
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/number/#”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/math/tanh”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/math/log1p”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/math/log10”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/json”): Bad message (74)
rsync: [generator] readdir(“/mnt/data/root/.node-red/node_modules/es5-ext/error/#”): Bad message (74)
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/object
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/object
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/number/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/number
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/number
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/math/tanh
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/math/log1p
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/math/log10
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/math
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/math
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/json
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/error/#
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/error
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext/error
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext
cannot delete non-empty directory: root/.node-red/node_modules/es5-ext
cannot delete non-empty directory: root/.node-red/node_modules
cannot delete non-empty directory: root/.node-red/node_modules
cannot delete non-empty directory: root/.node-red
cannot delete non-empty directory: root/.node-red
cannot delete non-empty directory: root
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3]
Looking for update .fit on /dev/mmcblk1p1…
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.
sh: can’t access tty; job control turned off
~ # [ 33.757610] dcdc4: disabling
Прошу уточнить серийный номер контроллера.
Давайте мы бесплатно поменяем вам оборудование. Курьер привезёт новое оборудование, старое возвращать не нужно:
WB-8 - 1 шт.
Для замены напишите, пожалуйста, отдельное письмо на info@wirenboard.com.
В письме укажите:
1 лайк
Добрый день.
Прошу прощения, поправлю коллегу:
читать как “Курьер привезёт новое оборудование, заберет старое”
1 лайк
