getting "mmcblk0: response CRC error" after reboot

[umiddelb]

Hi

I just managed to get ubuntu up and running on the odroid-c1, but after each reboot I'm getting the following errors:

Code: Select all

/scripts/local-top/c1_init.sh[    3.577040@0] [aml_sdhc_print_err] sd: data CRC error, port=4, Cmd18 Arg 00000b60, xfer_step=3, status=4, cmd25=0, fifo_empty=0, fifo_6
Pinmux: REG2=0x000000f0, REG3=0x00000000, REG4=0x00000300, REG5=0x00000000, REG6=0xfc003e4f, REG8=0x00000000
[    3.604249@0] ***********SDHC_REGS***********
[    3.608561@0] SDHC_ARGU: 0x00000900
[    3.612135@0] SDHC_SEND: 0x000700d2
[    3.615509@0] SDHC_CTRL: 0xe7ffe001
[    3.618981@0] SDHC_STAT: 0x00000028
[    3.622492@0] SDHC_CLKC: 0x0002f010
[    3.625929@0] SDHC_ADDR: 0x3fc80200
[    3.629431@0] SDHC_PDMA: 0x2c43bcf0
[    3.632876@0] SDHC_MISC: 0xe0000150
[    3.636349@0] SDHC_DATA: 0x7470346f
[    3.639841@0] SDHC_ICTL: 0x000030e6
[    3.643297@0] SDHC_ISTA: 0x00000549
[    3.646774@0] SDHC_SRST: 0x00000000
[    3.650266@0] SDHC_ESTA: 0x00000000
[    3.653717@0] SDHC_ENHC: 0x00fe0cff
[    3.657191@0] SDHC_CLK2: 0x0000100f
[    3.660863@0] mmcblk0: response CRC error sending r/w cmd command, card status 0xb00

The uSD card is from Samsung (Samsung Pro 32, MB-MG32D):

Code: Select all

sd: new ultra high speed SDR104 SDHC card at address 0001, clock 94444444, 4-bit-bus-width

This error occurs, regardless of the setting of

Code: Select all

setenv disableuhs "disableuhs"

in /media/boot/boot.ini

Only disconnecting the ODROID-C1 from the power supply and reconnecting it again helps to circumvent this error.

[tobetter]

Hi

I just managed to get ubuntu up and running on the odroid-c1, but after each reboot I'm getting the following errors:

Code: Select all

/scripts/local-top/c1_init.sh[    3.577040@0] [aml_sdhc_print_err] sd: data CRC error, port=4, Cmd18 Arg 00000b60, xfer_step=3, status=4, cmd25=0, fifo_empty=0, fifo_6
Pinmux: REG2=0x000000f0, REG3=0x00000000, REG4=0x00000300, REG5=0x00000000, REG6=0xfc003e4f, REG8=0x00000000
[    3.604249@0] ***********SDHC_REGS***********
[    3.608561@0] SDHC_ARGU: 0x00000900
[    3.612135@0] SDHC_SEND: 0x000700d2
[    3.615509@0] SDHC_CTRL: 0xe7ffe001
[    3.618981@0] SDHC_STAT: 0x00000028
[    3.622492@0] SDHC_CLKC: 0x0002f010
[    3.625929@0] SDHC_ADDR: 0x3fc80200
[    3.629431@0] SDHC_PDMA: 0x2c43bcf0
[    3.632876@0] SDHC_MISC: 0xe0000150
[    3.636349@0] SDHC_DATA: 0x7470346f
[    3.639841@0] SDHC_ICTL: 0x000030e6
[    3.643297@0] SDHC_ISTA: 0x00000549
[    3.646774@0] SDHC_SRST: 0x00000000
[    3.650266@0] SDHC_ESTA: 0x00000000
[    3.653717@0] SDHC_ENHC: 0x00fe0cff
[    3.657191@0] SDHC_CLK2: 0x0000100f
[    3.660863@0] mmcblk0: response CRC error sending r/w cmd command, card status 0xb00

The uSD card is from Samsung (Samsung Pro 32, MB-MG32D):

Code: Select all

sd: new ultra high speed SDR104 SDHC card at address 0001, clock 94444444, 4-bit-bus-width

This error occurs, regardless of the setting of

Code: Select all

setenv disableuhs "disableuhs"

in /media/boot/boot.ini

Only disconnecting the ODROID-C1 from the power supply and reconnecting it again helps to circumvent this error.

Thank you for worth report.
With your MicroSD, is the option disableuhs is commented out?

[umiddelb]

Only disconnecting the ODROID-C1 from the power supply and reconnecting it again helps to circumvent this error.

Thank you for worth report.
With your MicroSD, is the option disableuhs is commented out?

actually yes, but even if I remove the '#'' at the beginning of the line the error occurs in the same way.

Maybe the shutdown procedure could be modified slightly in order to do a proper uSD card reset:

Code: Select all

 * Will now halt
[30712.868881@0] Power down.
[30712.868910@0] Restarting Linux version 3.10.65-44 (root@xu3-b2) (gcc version5
[30712.868910@0] 
QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC037EBCBFA4
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.
clear pinmux reg10[31]=0
clear pinmux reg10[19]=0
out reg=c8100024,value=bfdf1fc7
set output en 0xc8100024[13]=0
set output val 0xc8100024[13]=0
a
b

There is no penalty time at system startup related to uSD card initialization. Interestingly, the uSD card is recognized as eMMC ...

Code: Select all

QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC037EBCBFA4
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.


U-boot-00000-ge7d4447-dirty(odroidc@e7d4447d) (Jan 20 2015 - 16:59:08)

DRAM:  1 GiB
relocation Offset is: 2ff1c000
MMC:   SDCARD: 0, eMMC: 1
IR init is done!
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
mode = 6  vic = 4
set HDMI vic: 4
mode is: 6
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK
There is no valid bmp file at the given address
============================================================
Vendor: Man 1b534d Snr 2a450cce Rev: 1.0 Prod: 00000
            Type: Removable Hard Disk
            Capacity: 30526.5 MB = 29.8 GB (62518272 x 512)
------------------------------------------------------------
Partition     Start Sector     Num Sectors     Type
    1                 2048          262144       b
    2               264192        62254080      83
============================================================
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
Hit Enter key to stop autoboot -- :  0 
exit abortboot: 0
reading boot.ini

2292 bytes read
Loading boot.ini from mmc0:1 (vfat)
Executing the script...
setenv m "1080p"                # 1080P@60Hz
setenv vout_mode "hdmi"
setenv m_bpp "32"
setenv vpu "0"
setenv hdmioutput "0"
...

[tobetter]

Only disconnecting the ODROID-C1 from the power supply and reconnecting it again helps to circumvent this error.

Thank you for worth report.
With your MicroSD, is the option disableuhs is commented out?

actually yes, but even if I remove the '#'' at the beginning of the line the error occurs in the same way.

Maybe the shutdown procedure could be modified slightly in order to do a proper uSD card reset:

Code: Select all

 * Will now halt
[30712.868881@0] Power down.
[30712.868910@0] Restarting Linux version 3.10.65-44 (root@xu3-b2) (gcc version5
[30712.868910@0] 
QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC037EBCBFA4
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.
clear pinmux reg10[31]=0
clear pinmux reg10[19]=0
out reg=c8100024,value=bfdf1fc7
set output en 0xc8100024[13]=0
set output val 0xc8100024[13]=0
a
b

There is no penalty time at system startup related to uSD card initialization. Interestingly, the uSD card is recognized as eMMC ...

Code: Select all

QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1;
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC037EBCBFA4
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.


U-boot-00000-ge7d4447-dirty(odroidc@e7d4447d) (Jan 20 2015 - 16:59:08)

DRAM:  1 GiB
relocation Offset is: 2ff1c000
MMC:   SDCARD: 0, eMMC: 1
IR init is done!
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
mode = 6  vic = 4
set HDMI vic: 4
mode is: 6
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK
There is no valid bmp file at the given address
============================================================
Vendor: Man 1b534d Snr 2a450cce Rev: 1.0 Prod: 00000
            Type: Removable Hard Disk
            Capacity: 30526.5 MB = 29.8 GB (62518272 x 512)
------------------------------------------------------------
Partition     Start Sector     Num Sectors     Type
    1                 2048          262144       b
    2               264192        62254080      83
============================================================
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
Hit Enter key to stop autoboot -- :  0 
exit abortboot: 0
reading boot.ini

2292 bytes read
Loading boot.ini from mmc0:1 (vfat)
Executing the script...
setenv m "1080p"                # 1080P@60Hz
setenv vout_mode "hdmi"
setenv m_bpp "32"
setenv vpu "0"
setenv hdmioutput "0"
...

Thank for update, and...let...me try...to fix...the problem............

[umiddelb]

Thank for update, and...let...me try...to fix...the problem............

Thank you. Just let me know, if you need more information.

[flubba86]

Im having the same problem (or a very similar one.)

Code: Select all

[    6.434577@1] [aml_sdhc_print_err] sd: data CRC error, port=4, Cmd18 Arg 00000080, xfer_step=3, status=4, cmd25=0, fifo_empty=0, fifo_full=0, timeout=0, Xfer 4096 Bytes, SEND=0x700d2, iSTA=0x549, STAT=0x22
[    6.434577@1] Pinmux: REG2=0x000000f0, REG3=0x00000000, REG4=0x00000300, REG5=0x00000000, REG6=0xfc003e4f, REG8=0x00000000
[    6.434590@1] ***********SDHC_REGS***********
[    6.434592@1] SDHC_ARGU: 0x00000900
[    6.434593@1] SDHC_SEND: 0x000700d2
[    6.434595@1] SDHC_CTRL: 0xe7ffe001
[    6.434596@1] SDHC_STAT: 0x00000024
[    6.434598@1] SDHC_CLKC: 0x0002f010
[    6.434599@1] SDHC_ADDR: 0x3ec80200
[    6.434601@1] SDHC_PDMA: 0x2c43bcf0
[    6.434602@1] SDHC_MISC: 0xe0000150
[    6.434603@1] SDHC_DATA: 0xef182ee1
[    6.434605@1] SDHC_ICTL: 0x000030e6
[    6.434606@1] SDHC_ISTA: 0x00004549
[    6.434608@1] SDHC_SRST: 0x00000000
[    6.434609@1] SDHC_ESTA: 0x00000000
[    6.434610@1] SDHC_ENHC: 0x00fe0cff
[    6.434612@1] SDHC_CLK2: 0x0000100f
[    6.434734@1] mmcblk0: response CRC error sending r/w cmd command, card status 0xb00

Just that repeating infinitely.

Using a brand new Samsung 16GB card.

This was on first boot, it was not caused by a reboot.

EDIT:
This is my bootup message, just like OP, it is recognising the card as eMMC, instead of SD.

Code: Select all

-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC0349CD6854
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.


U-boot-00000-ge7d4447-dirty(odroidc@e7d4447d) (Jan 20 2015 - 16:59:08)

DRAM:  1 GiB
relocation Offset is: 2ff1c000
MMC:   SDCARD: 0, eMMC: 1
IR init is done!
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
mode = 6  vic = 4
set HDMI vic: 4
mode is: 6
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK
There is no valid bmp file at the given address
============================================================
Vendor: Man 1b534d Snr 190f14cf Rev: 1.0 Prod: 00000
            Type: Removable Hard Disk
            Capacity: 14992.0 MB = 14.6 GB (30703616 x 512)
------------------------------------------------------------
Partition     Start Sector     Num Sectors     Type
    1                 2048          262144       c
    2               264192        30439424      83
============================================================
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
Hit Enter key to stop autoboot -- :  0 
exit abortboot: 0
reading boot.ini

[tobetter]

Im having the same problem (or a very similar one.)

Code: Select all

[    6.434577@1] [aml_sdhc_print_err] sd: data CRC error, port=4, Cmd18 Arg 00000080, xfer_step=3, status=4, cmd25=0, fifo_empty=0, fifo_full=0, timeout=0, Xfer 4096 Bytes, SEND=0x700d2, iSTA=0x549, STAT=0x22
[    6.434577@1] Pinmux: REG2=0x000000f0, REG3=0x00000000, REG4=0x00000300, REG5=0x00000000, REG6=0xfc003e4f, REG8=0x00000000
[    6.434590@1] ***********SDHC_REGS***********
[    6.434592@1] SDHC_ARGU: 0x00000900
[    6.434593@1] SDHC_SEND: 0x000700d2
[    6.434595@1] SDHC_CTRL: 0xe7ffe001
[    6.434596@1] SDHC_STAT: 0x00000024
[    6.434598@1] SDHC_CLKC: 0x0002f010
[    6.434599@1] SDHC_ADDR: 0x3ec80200
[    6.434601@1] SDHC_PDMA: 0x2c43bcf0
[    6.434602@1] SDHC_MISC: 0xe0000150
[    6.434603@1] SDHC_DATA: 0xef182ee1
[    6.434605@1] SDHC_ICTL: 0x000030e6
[    6.434606@1] SDHC_ISTA: 0x00004549
[    6.434608@1] SDHC_SRST: 0x00000000
[    6.434609@1] SDHC_ESTA: 0x00000000
[    6.434610@1] SDHC_ENHC: 0x00fe0cff
[    6.434612@1] SDHC_CLK2: 0x0000100f
[    6.434734@1] mmcblk0: response CRC error sending r/w cmd command, card status 0xb00

Just that repeating infinitely.

Using a brand new Samsung 16GB card.

This was on first boot, it was not caused by a reboot.

EDIT:
This is my bootup message, just like OP, it is recognising the card as eMMC, instead of SD.

Code: Select all

-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : HKC13C0001
S/N : HKC1CC0349CD6854
0x0000009f
check SD_boot_type:0x1   card_type:0x1
Loading U-boot...success.


U-boot-00000-ge7d4447-dirty(odroidc@e7d4447d) (Jan 20 2015 - 16:59:08)

DRAM:  1 GiB
relocation Offset is: 2ff1c000
MMC:   SDCARD: 0, eMMC: 1
IR init is done!
vpu clk_level = 3
set vpu clk: 182150000Hz, readback: 182150000Hz(0x701)
mode = 6  vic = 4
set HDMI vic: 4
mode is: 6
viu chan = 1
config HPLL
config HPLL done
reconfig packet setting done
MMC read: dev # 0, block # 33984, count 12288 ... 12288 blocks read: OK
There is no valid bmp file at the given address
============================================================
Vendor: Man 1b534d Snr 190f14cf Rev: 1.0 Prod: 00000
            Type: Removable Hard Disk
            Capacity: 14992.0 MB = 14.6 GB (30703616 x 512)
------------------------------------------------------------
Partition     Start Sector     Num Sectors     Type
    1                 2048          262144       c
    2               264192        30439424      83
============================================================
Net:   Meson_Ethernet
init suspend firmware done. (ret:0)
Hit Enter key to stop autoboot -- :  0 
exit abortboot: 0
reading boot.ini

The issue is very ridiculous, since some uses say this issue happens on reboot even if we add disableuhs option, some users meet the same on the first boot. I am still investigating the issue but not able to catch the root cause yet. And if you are saying eMMC is recognized eMMC since MMC: SDCARD: 0, eMMC: 1, it's just an index number of the cards. If your C1 boot from eMMC, it will say MMC: eMMC: 0, SDCARD: 1.

[flubba86]

Sorry, ignore my post. I was stupid. I just tried to comment out (#) disableuhs in boot.ini and it fixed it.

[flubba86]

And yet another update. I was able to reproduce OP's problem after reboot, even with disableuhs commented I ran into the same problem.
To fix, I loaded the sd card into my PC, mounted it, unmounted it, then did "eject /dev/sdx" which I guess resets the card. Placed it back in the C1 and it boots again.

[pdenhaan]

Just a one-liner to add that I've got the same problem using a Sandisk Extreme 16GB uSD. A reboot causes CRC errors to be logged regardless of UHS-1 status. After a halt and power cycling, the card works flawlessly in UHS-1 mode (or with UHS-1 disabled, for that matter).

[joelnet]

I am now seeing this error after soft reboot. cycling the power seems to fix.

My card: Samsung 16GB EVO Class 10 Micro SDHC with Adapter up to 48MB/s (MB-MP16DA/AM)

[tobetter]

I am now seeing this error after soft reboot. cycling the power seems to fix.

My card: Samsung 16GB EVO Class 10 Micro SDHC with Adapter up to 48MB/s (MB-MP16DA/AM)

This is a kinda compatible issue and no solution except power cycle reset to work properly. Power cycle boot would make it work very normal if you do not have boot issue.

[umiddelb]

This is a kinda compatible issue and no solution except power cycle reset to work properly. Power cycle boot would make it work very normal if you do not have boot issue.

Do you provide a list of compatible SD cards for the C1 known to survive a reboot without power cycle?

[odroid]

Refer this thread.
http://forum.odroid.com/viewtopic.php?f=115&t=7743

We strongly recommend the Sandisk UHS-1 cards.

[umiddelb]

Refer this thread.
http://forum.odroid.com/viewtopic.php?f=115&t=7743

We strongly recommend the Sandisk UHS-1 cards.

Wouldn't it be better to have a consolidated compatibility status of uSD cards, e.g.
model, spec, size, odroid device, boots(y/n), slow boot(y/n), reboot with power cycle(y/n), speed read, speed write, reported by, verified by

[pamarinp]

Hello,

I bought recently 4 odroids C1+ and 4 microSDHC 8GB HAMA C10 r/w: 22mb/s. The problem is that I have exactly the same problem, CRC error in first time of boot and I am not able to fix it even disabling the UHS compatibility in boot.ini

I try with different screens and resolutions but nothing change. Could you tell me what steps I have to do in order to start the OS properly?

[odroid]

Which OS image did you flashed?
Do you see the CRC error only in the reboot process?

[pamarinp]

I use the last version ubuntu-14.04.3lts-lubuntu-odroid-c1-20151020.img (v1.6).

I flash the OS in the micrSDHC HAMA 10 class, put on the odroid c1+ and connect the screen. After that the OS never starts, only after 5 min this screen appears. The blue led blink periodically like heartbeat.

Thank you in advance.

[odroid]

I think the SD card seems not to be compatible with C1+.
I've searched the same card in our local market to double-check, but I couldn't.
Is it a local brand?
Can you try other card?

[pamarinp]

I bought in POLLIN in Germany
This store: http://www.pollin.de/shop/index.html in germany
The item:
http://www.pollin.de/shop/dt/MjgzNjcyOT ... _8_GB.html
It is a pity but the seller doesn't reply me.

[odroid]

We will try to buy a couple of samples to test it.

[pamarinp]

I bought from Spain Sandisk microSDHC ultra 8Gb and works perfectly. Now you can update the cards that don't work properly with c1/c1+

[privader]

I bought a year ago this cards (intenso 8 GB) from pollin and they work, of course only with disableuhs!

The same cards I just now bought don't work, they make the problems in booting odroid you are mentioning. On my notebook or a PC USB adapter they can be written, but not be booted on odroid.

!! This must be a revision thing !!

But also with the old cards there are more problems: Some of the old cards mostly working (only with disableuhs) they have sometimes another problem: I can write an image to them in my notebook or an PC USB adapter, and modify them (with chroot and qemu). Everything works great, also booting works fine in odroid. If I enter them into odroid and mount them there read write and write something, I sometimes get the following errors (also disableuhs is active!):

My question is: if my notebook and PC USB adapter can write any SD Cards without problems, why is it not possible to make the odroid to be able to do the same?

root@odroidc1-001e0610657e:~# apt-get install openvpn bridge-utils vlan
[...]
Setting up bridge-utils (1.5-9) ...
Setting up openvpn (2.3.4-5+deb8u1) ...
[ 307.629013@1] mmcblk0: r/w command failed, status = 0x80000b00
[ 307.629316@1] end_request: I/O error, dev mmcblk0, sector 15564792
[ 307.635702@1] Buffer I/O error on device mmcblk0, logical block 1945599
[ 307.642371@0] systemd-gpt-auto-generator[1097]: Failed to probe /dev/mmcblk0: Input/output error
[ 307.998867@1] mmcblk0: r/w command failed, status = 0x80000b00
[ 307.999168@1] end_request: I/O error, dev mmcblk0, sector 15564792
[ 308.005546@1] Buffer I/O error on device mmcblk0, logical block 1945599
[ 308.015361@3] systemd-gpt-auto-generator[1116]: Failed to probe /dev/mmcblk0: Input/output error
Restarting virtual private network daemon.:.
[ 309.283675@1] mmcblk0: r/w command failed, status = 0x80000b00
[ 309.283990@1] end_request: I/O error, dev mmcblk0, sector 15564792
[ 309.290208@1] Buffer I/O error on device mmcblk0, logical block 1945599
[ 309.296912@1] systemd-gpt-auto-generator[1144]: Failed to probe /dev/mmcblk0: Input/output error
[ 309.823837@1] mmcblk0: r/w command failed, status = 0x80000b00
[ 309.824150@1] end_request: I/O error, dev mmcblk0, sector 15564792
[ 309.830661@1] Buffer I/O error on device mmcblk0, logical block 1945599
[ 309.837058@2] systemd-gpt-auto-generator[1163]: Failed to probe /dev/mmcblk0: Input/output error
Setting up easy-rsa (2.2.2-1) ...
Setting up opensc (0.14.0-2) ...
Setting up vlan (1.9-3.2) ...
Processing triggers for libc-bin (2.19-18+deb8u1) ...
Processing triggers for systemd (215-17+deb8u2) ...
[ 312.765441@1] mmcblk0: r/w command failed, status = 0x80000b00
[ 312.765759@1] end_request: I/O error, dev mmcblk0, sector 15564792
[ 312.772310@1] Buffer I/O error on device mmcblk0, logical block 1945599
[ 312.778679@0] systemd-gpt-auto-generator[1185]: Failed to probe /dev/mmcblk0: Input/output error
root@odroidc1-001e0610657e:~#