Failed to write to partition

General Discussions
1

I upgraded my fleet with a new artifact with success but for one of our devices, i got the following error.
Do someone knows if i can do anything or consider this device “non upgradable” ?
Thanks

2021-12-17 07:59:48 +0000 UTC info: Running Mender client version: 2.4.1
2021-12-17 07:59:48 +0000 UTC info: State transition: update-fetch [Download_Enter] -> update-store [Download_Enter]
2021-12-17 07:59:53 +0000 UTC info: No public key was provided for authenticating the artifact
2021-12-17 07:59:53 +0000 UTC info: Opening device "/dev/mmcblk0p3" for writing
2021-12-17 07:59:53 +0000 UTC info: Native sector size of block device /dev/mmcblk0p3 is 512 bytes. Mender will write in chunks of 1048576 bytes
2021-12-17 08:16:47 +0000 UTC error: Failed to read a full frame of size: &{%!d(string=read) %!d(string=/dev/mmcblk0p3) 5} from the block-device
2021-12-17 08:16:47 +0000 UTC error: Failed to write 3012215468 bytes to the new partition
2021-12-17 08:17:59 +0000 UTC error: Failed to read a full frame of size: &{%!d(string=read) %!d(string=/dev/mmcblk0p3) 5} from the block-device
2021-12-17 08:17:59 +0000 UTC info: The optimized block-device writer wrote a total of 1068 frames, where 1004 frames did need to be rewritten (i.e., skipped)
2021-12-17 08:18:00 +0000 UTC error: Artifact install failed: Payload: can not install Payload: rootfs.img: read /dev/mmcblk0p3: input/output error
2021-12-17 08:18:00 +0000 UTC info: State transition: update-store [Download_Enter] -> cleanup [Error]
2021-12-17 08:18:00 +0000 UTC info: State transition: cleanup [Error] -> update-status-report [none]
2

What does the kernel log say?

3

@oleorhagen Indeed, i have the following errors

[869761.211849] mmc0: SDHBCT 0x00000200
[869761.211854] mmc0: SDHBLC 0x00000001
[869761.211859] mmc0: ===========================================
[869761.211970] mmcblk0: error -110 transferring data, sector 15926117, nr 3, cmd response 0x900, card status 0x0
[869761.211986] print_req_error: I/O error, dev mmcblk0, sector 15926117
[869771.450124] mmc0: timeout waiting for hardware interrupt.
[869771.450139] [c1a6165d] FCM> 91da98d0 0
[869771.450147] [c1a6165d] CMD  11 200
[869771.450155] [c1a6165e] REQ> 91da98d0 0
[869771.450163] [01a6165e] IRQ< 1 0
[869771.450170] [01a6165e] IRQD 91da99b0 1
[869771.450178] [01a6165f] XFP< 91da99b0 1
[869771.450186] [01a61c8f] XFP> 91da99b0 1

[869771.452177] mmc0: SDHBLC 0x00000001
[869771.452182] mmc0: ===========================================
[869771.452304] mmcblk0: error -110 transferring data, sector 15926118, nr 2, cmd response 0x900, card status 0x0
[869771.452327] print_req_error: I/O error, dev mmcblk0, sector 15926118
[869781.690433] mmc0: timeout waiting for hardware interrupt.
[869781.690447] [01a61cad] XFP< 91da99b0 1
4

I’m not fully sure how to go further with this.

The problem could be mechanical, as in your SD card is wearing out, but could also be a driver issue.

But considering all the other devices succeeded, and I’m guessing they’re using the same cards, and the same software, then maybe if you are unlucky, the SD card has had too many writes.

But then again, I’m in deep water here.

5

Thanks for your time. I’m gonna replace the SD card

1 Like