SD cards CRC errors

boot2k3 · March 10, 2018 at 8:35 AM

I have CRC errors on all of my SD, microsd cards in LE

One of them, during boot process:

Code

Mar 10 09:48:04 LibreELEC kernel: aml_sd_emmc_data_thread : 2586
Mar 10 09:48:04 LibreELEC kernel: mmcblk1: response CRC error sending r/w cmd command, card status 0x900
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568698
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568706
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568714
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568722
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568730
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568738
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568746
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568754
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568762
Mar 10 09:48:04 LibreELEC kernel: end_request: I/O error, dev mmcblk1, sector 9568770

Display More

and repeated error:

Code

Mar 10 09:48:04 LibreELEC kernel: [aml_sd_emmc_irq] sd: warning... data crc, vstat:0xe1ff0008, virqc:3fff
Mar 10 09:48:04 LibreELEC kernel: [aml_sd_emmc_irq] @ cmd 18 with ffffffc0a0923170; stop 0, status 4
Mar 10 09:48:04 LibreELEC kernel: [aml_host_bus_fsm_show] sd: err: wait for irq service, bus_fsm:0x8
Mar 10 09:48:04 LibreELEC kernel: aml_sd_emmc_data_thread 2639 sd: cmd:18
Mar 10 09:48:04 LibreELEC kernel: [aml_sd_emmc_data_thread] aml_sd_emmc_data_thread() 2655: set 1st retry!
Mar 10 09:48:04 LibreELEC kernel: aml_sd_emmc_data_thread : 2586
Mar 10 09:48:04 LibreELEC kernel: sd: req failed (CMD18): -84, retrying...

I don't believe what all my cards have bad blocks, some of them are new one.

Also fsck doesn't show any errors

Are any solution available for this errors?

Tim_Taylor · March 10, 2018 at 9:17 AM

Quote from boot2k3

I don't believe what all my cards have bad blocks, some of them are new one.

I believe it´s caused by internal card reader.

You can try USB pen or buy a new box(best choice)

bubblegum57 · March 10, 2018 at 9:38 AM

You could try a low level format, eg Low Level Format and zero-filling

boot2k3 · March 10, 2018 at 10:00 AM

Quote from Tim_Taylor

I believe it´s caused by internal card reader.

You can try USB pen or buy a new box(best choice)

Quote from bubblegum57

You could try a low level format, eg Low Level Format and zero-filling

Thank you, I will try to perform both of your advice later.

To change the box is not a good idea. It works very well. Just this issue with card I have last month.

boot2k3 · March 10, 2018 at 10:14 AM

Quote from bubblegum57

You could try a low level format, eg Low Level Format and zero-filling

This utility mark my 32 gb micro-sd card with bad blocks approximately after 33%

what is wrong?

**S80_UK** · March 10, 2018 at 10:40 AM

My suggestion - try H2testw on your cards - it's a thorough tester that will find out if your cards are not being truthful about their capacity. The utility will write the enire card and then check the data. In the checking it can tell if the data is coming from the right place. Could be the cards are fakes...

German site here... H2testw | heise Download

Softpedia here... H2testw Download

boot2k3 · March 10, 2018 at 2:04 PM

The reason was in my micro-sd to usb adapter, I used it for image burning and some reconfiguration. So it doesn't work correctly with micro-sd card more than 8 Gb, after 10 Gb it works incorrectly.

Now I did a fresh install via card reader and backup restore via SD slot ~~and no more CRC errors~~.

Thank you all for your help.

boot2k3 · March 10, 2018 at 3:28 PM

After some time and reboot the same crc errors

micro-SD tested - no errors

bubblegum57 · March 10, 2018 at 3:54 PM

What are you using to create the image?

i use rufus

boot2k3 · March 10, 2018 at 4:23 PM

LibreELEC.USB-SD.Creator.Win32

I don't think that the problem is in image program

bubblegum57 · March 10, 2018 at 4:46 PM

maybe not, but you have nothing to lose.

boot2k3 · March 10, 2018 at 5:39 PM

of course. Also I ordered new micro sd to usb adapter, I will try it too after receive.

boot2k3 · March 11, 2018 at 6:46 AM

I tried rufus, no changes, still the same errors.

But if I change my card location in usb card reader, than no more crc error, but device boots slower

And from dmesg I see internal SD card reader response timeout during boot process:

Code

[   34.415882@0] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff
[   34.415907@6] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8
[   34.416043@6] aml_sd_emmc_data_thread 2639 sdio: cmd:52
[   34.417219@0] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff
[   34.417225@6] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8
[   34.417313@6] aml_sd_emmc_data_thread 2639 sdio: cmd:52
[   34.422289@0] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa3ff2800,virqc:3fff
[   34.422298@6] [aml_host_bus_fsm_show] sdio: err: wait for irq service, bus_fsm:0x8
[   34.422380@6] aml_sd_emmc_data_thread 2639 sdio: cmd:8
[   34.451211@7] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[   34.454445@4] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[   34.457655@4] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[   34.463325@4] sdio: queuing unknown CIS tuple 0x80 (7 bytes)
[   34.561810@4] sdio: clk 200000000 SDR mode tuning start
[   34.562464@4] sdio: rx_tuning_result[0] = 10
[   34.563088@4] sdio: rx_tuning_result[1] = 10
[   34.563711@4] sdio: rx_tuning_result[2] = 10
[   34.566590@4] sdio: rx_tuning_result[3] = 10
[   34.566684@4] sdio: best_win_start =0, best_win_size =4
[   34.566709@4] sdio: sd_emmc_regs->gclock=0x1000245,sd_emmc_regs->gadjust=0x22000
[   34.566744@4] sdio: gclock =0x1000245, gdelay=0x0, gadjust=0x22000
[   34.576913@7] sdio: queuing unknown CIS tuple 0x91 (3 bytes)
[   34.577022@7] sdio: new ultra high speed SDR104 SDIO card at address 0001
[   34.577047@5] sdio: clock 200000000, 4-bit-bus-width
...
[   35.884018@2] ======== Card detection to detect SDIO card! ========
[   35.884022@2] sdio_reset_comm():
[   35.912173@7] sdio: queuing unknown CIS tuple 0x80 (2 bytes)
[   35.914779@4] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[   35.917372@4] sdio: queuing unknown CIS tuple 0x80 (3 bytes)
[   35.922006@7] sdio: queuing unknown CIS tuple 0x80 (7 bytes)
[   36.014682@7] sdio: clk 200000000 SDR mode tuning start
[   36.014913@7] sdio: rx_tuning_result[0] = 10
[   36.015123@7] sdio: rx_tuning_result[1] = 10
[   36.015332@7] sdio: rx_tuning_result[2] = 10
[   36.015557@4] sdio: rx_tuning_result[3] = 10
[   36.015587@4] sdio: best_win_start =0, best_win_size =4
[   36.015594@4] sdio: sd_emmc_regs->gclock=0x1000245,sd_emmc_regs->gadjust=0x22000
[   36.015602@4] sdio: gclock =0x1000245, gdelay=0x0, gadjust=0x22000
[   36.015608@4] [sdio_reinit] finish

Display More

Is it internal SD reader problem or can be driver config issue?

Tim_Taylor · March 11, 2018 at 7:40 AM

Quote from boot2k3

Is it internal SD reader problem or can be driver config issue?

I don´t believe a driver issue.

As I said before - internal card reader isn´t working properly

**chewitt** · March 11, 2018 at 7:47 AM Official Post

Some card readers don't like super-fast SD cards. See if you can find and retest with an old/slow SD card.