Проблема с eMMC или microSD?

1

Добрый день.

Есть WB8.5 (8.4.4A/4G 1.2B-4G/1).
WB-2501, из стороннего только докер и SprutHub в докере. И то, и то на microSD-карте.

Содержимое /etc/fstab:

/dev/mmcblk0p2       /                    auto       discard,errors=remount-ro,noatime                                      0          1
/dev/mmcblk0p5       none                 swap       noatime,discard,errors=remount-ro                                      0          0
/dev/mmcblk0p6       /mnt/data            auto       noatime,discard,nofail                                                 0          2
/dev/mmcblk1p1       /mnt/sdcard          auto       noatime,nofail,x-systemd.automount,x-systemd.device-timeout=2          0          2
/mnt/data/var/log    /var/log             none       bind                                                                   0          0
configfs             /sys/kernel/config   configfs   defaults                                                               0          0

Раз в неделю в логи сыпется грустное (иногда ошибок больше, иногда меньше):

Feb 10 00:09:42 wirenboard-A6MED3CD systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Feb 10 00:09:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 10 00:09:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 10 00:09:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
... удалено 225 строк ...
Feb 10 00:09:55 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 10 00:09:56 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 10 00:09:56 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 10 00:09:56 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Feb 10 00:09:56 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Feb 10 00:10:12 wirenboard-A6MED3CD fstrim[991337]: /mnt/sdcard: 54.9 GiB (58902347776 bytes) trimmed on /dev/mmcblk1p1
Feb 10 00:10:12 wirenboard-A6MED3CD fstrim[991337]: /mnt/data: 52.6 GiB (56453656576 bytes) trimmed on /dev/mmcblk0p6
Feb 10 00:10:12 wirenboard-A6MED3CD fstrim[991337]: /: 295.8 MiB (310206464 bytes) trimmed on /dev/mmcblk0p2
Feb 10 00:10:12 wirenboard-A6MED3CD systemd[1]: fstrim.service: Succeeded.
Feb 10 00:10:12 wirenboard-A6MED3CD systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Feb 10 00:10:12 wirenboard-A6MED3CD systemd[1]: fstrim.service: Consumed 1.898s CPU time.

...

Feb 17 01:12:42 wirenboard-A6MED3CD systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Feb 17 01:12:42 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 17 01:12:43 wirenboard-A6MED3CD fstrim[2167883]: /mnt/sdcard: 162.7 MiB (170651648 bytes) trimmed on /dev/mmcblk1p1
Feb 17 01:12:43 wirenboard-A6MED3CD fstrim[2167883]: /mnt/data: 0 B (0 bytes) trimmed on /dev/mmcblk0p6
Feb 17 01:12:43 wirenboard-A6MED3CD fstrim[2167883]: /: 0 B (0 bytes) trimmed on /dev/mmcblk0p2
Feb 17 01:12:43 wirenboard-A6MED3CD systemd[1]: fstrim.service: Succeeded.
Feb 17 01:12:43 wirenboard-A6MED3CD systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.

...

Feb 24 01:34:02 wirenboard-A6MED3CD systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Feb 24 01:34:02 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 24 01:34:02 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Feb 24 01:34:02 wirenboard-A6MED3CD fstrim[3316378]: /mnt/sdcard: 52 MiB (54534144 bytes) trimmed on /dev/mmcblk1p1
Feb 24 01:34:02 wirenboard-A6MED3CD fstrim[3316378]: /mnt/data: 0 B (0 bytes) trimmed on /dev/mmcblk0p6
Feb 24 01:34:02 wirenboard-A6MED3CD fstrim[3316378]: /: 0 B (0 bytes) trimmed on /dev/mmcblk0p2
Feb 24 01:34:02 wirenboard-A6MED3CD systemd[1]: fstrim.service: Succeeded.
Feb 24 01:34:02 wirenboard-A6MED3CD systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.

Вопрос, кто виноват и что делать?
microSD вот эта Промышленная карта памяти TS64GUSD460T - Wiren Board установлена.

2

Добрый день.
При выполнении штатной периодической уборки

контроллер занимается ей и ядро ругается. В обще не вижу повода переживать.

5

Игнорирование симптомов, ожидаемо привело к проблеме:

Mar 10 00:18:31 wirenboard-A6MED3CD systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: data error, sending stop command
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: sunxi-mmc 4020000.mmc: send stop command failed
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: I/O error, dev mmcblk1, sector 109101040 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: Buffer I/O error on dev mmcblk1p1, logical block 13633534, lost async page write
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:31 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
70 lines skipped...
Mar 10 00:18:35 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:35 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:35 wirenboard-A6MED3CD kernel: mmc_erase: group start error -110, status 0x0
Mar 10 00:18:35 wirenboard-A6MED3CD fstrim[2886545]: /mnt/sdcard: 3.3 GiB (3560656896 bytes) trimmed on /dev/mmcblk1p1
Mar 10 00:18:35 wirenboard-A6MED3CD fstrim[2886545]: /mnt/data: 116.2 MiB (121827328 bytes) trimmed on /dev/mmcblk0p6
Mar 10 00:18:35 wirenboard-A6MED3CD fstrim[2886545]: /: 0 B (0 bytes) trimmed on /dev/mmcblk0p2
Mar 10 00:18:35 wirenboard-A6MED3CD systemd[1]: fstrim.service: Succeeded.
Mar 10 00:18:35 wirenboard-A6MED3CD systemd[1]: Finished Discard unused blocks on filesystems from /etc/fstab.
Mar 10 00:18:52 wirenboard-A6MED3CD kernel: Aborting journal on device mmcblk1p1-8.
Mar 10 00:18:52 wirenboard-A6MED3CD kernel: EXT4-fs error (device mmcblk1p1) in ext4_reserve_inode_write:5738: IO failure
Mar 10 00:18:52 wirenboard-A6MED3CD kernel: EXT4-fs error (device mmcblk1p1): ext4_dirty_inode:5942: inode #3440108: comm C1 CompilerThre: mark_inode_dirty error
Mar 10 00:18:52 wirenboard-A6MED3CD kernel: EXT4-fs error (device mmcblk1p1) in ext4_dirty_inode:5943: IO failure
Mar 10 00:18:56 wirenboard-A6MED3CD kernel: EXT4-fs error (device mmcblk1p1): ext4_journal_check_start:84: comm VM Periodic Tas: Detected aborted journal
Mar 10 00:18:56 wirenboard-A6MED3CD kernel: EXT4-fs (mmcblk1p1): Remounting filesystem read-only

Mar 10 00:22:19 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:22:19.318027270+03:00" level=error msg="Handler for GET /containers/65e3c0ba2bea1ee3fb30d86b6fc8b46a8806cb12386ab335380ce94f0dea64b3/json returned error: open /mnt/sdcard/srv/.docker/overlay2/cba801051a8ec7b5aec8bb32e70212672c5b846bff78c2e638ae3a352918d376/lower: input/output error"
Mar 10 00:22:19 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:22:19.762019457+03:00" level=error msg="invalid image access: \"sha256:7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548\", error: \"failed to get digest sha256:7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548: open /mnt/sdcard/srv/.docker/image/overlay2/imagedb/content/sha256/7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548: input/output error\""
Mar 10 00:22:19 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:22:19.762751552+03:00" level=error msg="invalid image access: \"sha256:432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f\", error: \"failed to get digest sha256:432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f: open /mnt/sdcard/srv/.docker/image/overlay2/imagedb/content/sha256/432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f: input/output error\""
Mar 10 00:27:18 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:27:18.946432498+03:00" level=error msg="Handler for GET /containers/65e3c0ba2bea1ee3fb30d86b6fc8b46a8806cb12386ab335380ce94f0dea64b3/json returned error: open /mnt/sdcard/srv/.docker/overlay2/cba801051a8ec7b5aec8bb32e70212672c5b846bff78c2e638ae3a352918d376/lower: input/output error"
Mar 10 00:27:18 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:27:18.957223044+03:00" level=error msg="invalid image access: \"sha256:432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f\", error: \"failed to get digest sha256:432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f: open /mnt/sdcard/srv/.docker/image/overlay2/imagedb/content/sha256/432c20300d34720a7e036f7c582967ccb771bb77f11b40322b0843fcd236148f: input/output error\""
Mar 10 00:27:18 wirenboard-A6MED3CD dockerd[3643]: time="2025-03-10T00:27:18.957557091+03:00" level=error msg="invalid image access: \"sha256:7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548\", error: \"failed to get digest sha256:7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548: open /mnt/sdcard/srv/.docker/image/overlay2/imagedb/content/sha256/7a3ad5b9909685d04bdedaa5155016e8d34ba7f08d8f549d2ab2fc851f3c4548: input/output error\""

В итоге сегодня утром microSD-карта оказалась в RO-режиме (а по факту вообще не читалась, IO failure появлялись при попытке прочитать любой файл). И только ребут исправил ситуацию.

Вопрос. Как убрать эти ошибки и сделать так, чтобы еженедельный discard не приводил к отключению карточки?
На карточке живёт SprutHub в докере и он умер ночью во время этого discard’а.