Asustor [Topic Avancé] Buffer I/O error on dev mmcblk0pX (Requiert Damien)

[Drthrax74]

Bonjour,

Suite à une vérification des erreurs système via la commande dmesg, j'ai remarquer le problème suivant. Auriez-vous une idée sur ce type d'erreur ? (Lecture / Ecriture)

@dam1: Serais-ce le disque dur contenant la ROM qui pose problème ?

sudo dmesg |grep "I/O\|mmc"
[ 1.249050] APIC: Switch to symmetric I/O mode setup
[ 6.606633] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 6.892855] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[ 7.566321] mmc0: CQHCI version 5.10
[ 7.567447] mmc0: SDHCI controller on PCI [0000:00:1c.0] using ADMA 64-bit
[ 7.567779] mmc1: SDHCI controller on PCI [0000:00:1e.0] using ADMA 64-bit
[ 7.714839] limit mmc HS200 mode
[ 7.737960] mmc0: new HS200 MMC card at address 0001
[ 7.751110] mmcblk0: mmc0:0001 M62704 3.53 GiB
[ 7.764792] mmcblk0boot0: mmc0:0001 M62704 partition 1 2.00 MiB
[ 7.773408] mmcblk0boot1: mmc0:0001 M62704 partition 2 2.00 MiB
[ 7.781411] mmcblk0rpmb: mmc0:0001 M62704 partition 3 512 KiB, chardev (245:0)
[ 7.857164] mmcblk0: p1 p2 p3
[ 9.484719] mmcblk: mmc_blk_ioctl_as_set_lock before set lock=0 flag 100
[ 9.491886] mmcblk: mmc_blk_ioctl_as_set_lock after set lock=0 flag 100
[ 9.534748] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 9.789148] mmcblk: mmc_blk_ioctl_as_set_lock before set lock=0 flag 100
[ 9.797023] mmcblk: mmc_blk_ioctl_as_set_lock after set lock=0 flag 100
[ 11.649862] mmcblk: mmc_blk_ioctl_as_set_lock before set lock=0 flag 100
[ 11.658180] mmcblk: mmc_blk_ioctl_as_set_lock after set lock=0 flag 100
[ 11.689012] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 14.838249] mmcblk: mmc_blk_ioctl_as_set_lock before set lock=0 flag 101
[ 14.845485] mmcblk: mmc_blk_ioctl_as_set_lock after set lock=1 flag 101
[ 23.702787] mmcblk: mmc_blk_ioctl_as_set_lock before set lock=1 flag 101
[ 23.710012] mmcblk: mmc_blk_ioctl_as_set_lock after set lock=1 flag 101
[1324099.671227] rejecting I/O to as-locked device
[1324099.671274] rejecting I/O to as-locked device
[1324099.671280] Buffer I/O error on dev mmcblk0p1, logical block 496, async page read
[1324099.671554] rejecting I/O to as-locked device
[1324099.671577] rejecting I/O to as-locked device
[1324099.671580] Buffer I/O error on dev mmcblk0p2, logical block 62448, async page read
[1324099.671813] rejecting I/O to as-locked device
[1324099.671833] rejecting I/O to as-locked device
[1324099.671835] Buffer I/O error on dev mmcblk0p3, logical block 62448, async page read
[1324112.157201] rejecting I/O to as-locked device
[1324112.157269] rejecting I/O to as-locked device
[1324112.157274] Buffer I/O error on dev mmcblk0p1, logical block 496, async page read
[1324112.157549] rejecting I/O to as-locked device
[1324112.157572] rejecting I/O to as-locked device
[1324112.157575] Buffer I/O error on dev mmcblk0p2, logical block 62448, async page read
[1324112.157809] rejecting I/O to as-locked device
[1324112.157829] rejecting I/O to as-locked device
[1324112.157832] Buffer I/O error on dev mmcblk0p3, logical block 62448, async page read

Note : /volume0/usr/builtin/sbin/smartctl

 

[Dami1]

Le message du log signifie qu'un processus tente d'accéder à la partition eMMC qui est verrouillée en permanence, à l'exception de l'utilisateur qui procède à la mise à niveau d'ADM.
Normalement, les apps/services ne devraient pas accéder à la partition eMMC, mais d'après mon expérience, c'est tout à fait normal, vous pouvez en fait trouver ce type de message dans certains dossiers de santé du NAS.
ça peut être ignoré à mon sens.