This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Getting EMMC Errors....
#1
Exclamation 
Getting these errors on the EMMC? What to do ?  Sad

Jan 24 19:55:28 domotica kernel: [102900.131461] mmcblk1: error -110 transferring data, sector 10246376, nr 8, cmd response 0x900, card status 0xb00
Jan 24 19:55:28 domotica kernel: [102900.138811] mmcblk1: retrying using single block read
Jan 24 19:56:07 domotica kernel: [102939.801131] mmcblk1: error -110 transferring data, sector 10246440, nr 8, cmd response 0x900, card status 0x0
Jan 24 19:56:07 domotica kernel: [102939.808621] mmcblk1: retrying using single block read
Jan 24 19:59:52 domotica kernel: [103164.089378] mmcblk1: error -110 transferring data, sector 10246784, nr 8, cmd response 0x900, card status 0x0
Jan 24 19:59:52 domotica kernel: [103164.096863] mmcblk1: retrying using single block read
Jan 24 20:02:02 domotica kernel: [103293.938322] mmcblk1: error -110 transferring data, sector 10246992, nr 8, cmd response 0x900, card status 0x0
Jan 24 20:02:02 domotica kernel: [103293.941668] mmcblk1: retrying using single block read
Jan 24 20:02:02 domotica kernel: [103293.978398] mmcblk1: error -110 transferring data, sector 10246992, nr 8, cmd response 0x900, card status 0x0
Jan 24 20:02:02 domotica kernel: [103293.981483] blk_update_request: I/O error, dev mmcblk1, sector 10246992
Jan 24 20:09:01 domotica kernel: [103713.827627] IPVS: Creating netns size=1496 id=59
Jan 24 20:09:01 domotica kernel: [103713.831696] IPVS: ftp: loaded support on port[0] = 21
Jan 24 20:24:59 domotica kernel: [104671.648226] mmcblk1: error -110 transferring data, sector 10249152, nr 8, cmd response 0x900, card status 0x0
Jan 24 20:24:59 domotica kernel: [104671.656511] mmcblk1: retrying using single block read
Jan 24 20:39:01 domotica kernel: [105513.111141] IPVS: Creating netns size=1496 id=60
Jan 24 20:39:01 domotica kernel: [105513.120976] IPVS: ftp: loaded support on port[0] = 21
Jan 24 20:51:51 domotica kernel: [106283.786518] mmcblk1: error -110 transferring data, sector 10251672, nr 8, cmd response 0x900, card status 0xb00
Jan 24 20:51:51 domotica kernel: [106283.794770] mmcblk1: retrying using single block read
Jan 24 21:09:02 domotica kernel: [107313.953443] IPVS: Creating netns size=1496 id=61
Jan 24 21:09:02 domotica kernel: [107313.966951] IPVS: ftp: loaded support on port[0] = 21
Jan 24 21:15:15 domotica kernel: [107687.246389] mmcblk1: error -110 transferring data, sector 10253872, nr 8, cmd response 0x900, card status 0xb00
Jan 24 21:15:15 domotica kernel: [107687.250679] mmcblk1: retrying using single block read
Jan 24 21:15:57 domotica kernel: [107729.786050] mmcblk1: error -110 transferring data, sector 10253936, nr 8, cmd response 0x900, card status 0x0
Reply
#2
In addition no bad blocks are found:

badblocks -v /dev/mmcblk1 > badsectors.txt
Controleren van blokken 0 tot 15388671
Zoeken naar slechte blokken (alleen-lezen-test): voltooid
Controle is voltooid; 0 slechte blokken gevonden (0/0/0 fouten).

translate (english)
Checking of blocks 0 to 15388671
Searching after badblocks (ready only test): finished
Control is finished; 0 badblocks founded (0/0/0 faults).


EDIT: (bootup log of EMMC)
Code:
[    0.000000] Kernel command line: earlyprintk console=tty1 rw init=/sbin/init uboot_version=2017.07-g8c31a11215 root=/dev/mmcblk1p2
[    1.981882] of_get_named_gpiod_flags: parsed 'gpio' property of node '/sdmmc-regulator[0]' - status (0)
[    3.426010] of_get_named_gpiod_flags: can't parse 'maskrom_gpio' property of node '/dwmmc@ff0c0000[0]'
[    3.426028] dwmmc_rockchip ff0c0000.dwmmc: IDMAC supports 32-bit address mode.
[    3.426079] dwmmc_rockchip ff0c0000.dwmmc: Using internal DMA controller.
[    3.426094] dwmmc_rockchip ff0c0000.dwmmc: Version ID is 270a
[    3.426125] dwmmc_rockchip ff0c0000.dwmmc: DW MMC controller at irq 29,32 bit host data width,256 deep fifo
[    3.426149] dwmmc_rockchip ff0c0000.dwmmc: 'clock-freq-min-max' property was deprecated.
[    3.426234] dwmmc_rockchip ff0c0000.dwmmc: GPIO lookup for consumer cd
[    3.426240] dwmmc_rockchip ff0c0000.dwmmc: using device tree for GPIO lookup
[    3.426245] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/dwmmc@ff0c0000[0]'
[    3.426249] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/dwmmc@ff0c0000[0]'
[    3.426253] dwmmc_rockchip ff0c0000.dwmmc: using lookup tables for GPIO lookup
[    3.426258] dwmmc_rockchip ff0c0000.dwmmc: lookup for GPIO cd failed
[    3.426264] dwmmc_rockchip ff0c0000.dwmmc: GPIO lookup for consumer wp
[    3.426268] dwmmc_rockchip ff0c0000.dwmmc: using device tree for GPIO lookup
[    3.426272] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0c0000[0]'
[    3.426276] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0c0000[0]'
[    3.426280] dwmmc_rockchip ff0c0000.dwmmc: using lookup tables for GPIO lookup
[    3.426283] dwmmc_rockchip ff0c0000.dwmmc: lookup for GPIO wp failed
[    3.445402] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    3.465426] dwmmc_rockchip ff0c0000.dwmmc: 1 slots initialized
[    3.466691] of_get_named_gpiod_flags: can't parse 'maskrom_gpio' property of node '/dwmmc@ff0d0000[0]'
[    3.466699] dwmmc_rockchip ff0d0000.dwmmc: IDMAC supports 32-bit address mode.
[    3.466744] dwmmc_rockchip ff0d0000.dwmmc: Using internal DMA controller.
[    3.466758] dwmmc_rockchip ff0d0000.dwmmc: Version ID is 270a
[    3.466790] dwmmc_rockchip ff0d0000.dwmmc: DW MMC controller at irq 30,32 bit host data width,256 deep fifo
[    3.466812] dwmmc_rockchip ff0d0000.dwmmc: 'clock-freq-min-max' property was deprecated.
[    3.466844] dwmmc_rockchip ff0d0000.dwmmc: No vmmc regulator found
[    3.466855] dwmmc_rockchip ff0d0000.dwmmc: No vqmmc regulator found
[    3.466870] dwmmc_rockchip ff0d0000.dwmmc: GPIO lookup for consumer wp
[    3.466874] dwmmc_rockchip ff0d0000.dwmmc: using device tree for GPIO lookup
[    3.466878] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0d0000[0]'
[    3.466882] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0d0000[0]'
[    3.466887] dwmmc_rockchip ff0d0000.dwmmc: using lookup tables for GPIO lookup
[    3.466891] dwmmc_rockchip ff0d0000.dwmmc: lookup for GPIO wp failed
[    3.467205] of_get_named_gpiod_flags: parsed 'maskrom_gpio' property of node '/dwmmc@ff0f0000[0]' - status (0)
[    3.477230] dwmmc_rockchip ff0f0000.dwmmc: set maskrom gpio to enable emmc
[    3.477244] dwmmc_rockchip ff0f0000.dwmmc: IDMAC supports 32-bit address mode.
[    3.477278] dwmmc_rockchip ff0f0000.dwmmc: Using internal DMA controller.
[    3.477292] dwmmc_rockchip ff0f0000.dwmmc: Version ID is 270a
[    3.477319] dwmmc_rockchip ff0f0000.dwmmc: DW MMC controller at irq 31,32 bit host data width,256 deep fifo
[    3.477341] dwmmc_rockchip ff0f0000.dwmmc: 'clock-freq-min-max' property was deprecated.
[    3.477370] dwmmc_rockchip ff0f0000.dwmmc: No vmmc regulator found
[    3.477381] dwmmc_rockchip ff0f0000.dwmmc: No vqmmc regulator found
[    3.477394] dwmmc_rockchip ff0f0000.dwmmc: GPIO lookup for consumer wp
[    3.477398] dwmmc_rockchip ff0f0000.dwmmc: using device tree for GPIO lookup
[    3.477402] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0f0000[0]'
[    3.477406] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0f0000[0]'
[    3.477410] dwmmc_rockchip ff0f0000.dwmmc: using lookup tables for GPIO lookup
[    3.477415] dwmmc_rockchip ff0f0000.dwmmc: lookup for GPIO wp failed
[    3.495395] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    3.516400] dwmmc_rockchip ff0f0000.dwmmc: 1 slots initialized
[    3.588904] mmc1: MAN_BKOPS_EN bit is not set
[    3.592721] mmc_host mmc1: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[    3.755942] dwmmc_rockchip ff0f0000.dwmmc: Successfully tuned phase to 211
[    3.757532] mmc1: new HS200 MMC card at address 0001
[    3.757973] mmcblk1: mmc1:0001 HAG4a2 14.7 GiB
[    3.758192] mmcblk1boot0: mmc1:0001 HAG4a2 partition 1 4.00 MiB
[    3.758427] mmcblk1boot1: mmc1:0001 HAG4a2 partition 2 4.00 MiB
[    3.758650] mmcblk1rpmb: mmc1:0001 HAG4a2 partition 3 4.00 MiB
[    3.759281]  mmcblk1: p1 p2
[    7.328714] of_get_named_gpiod_flags: can't parse 'maskrom_gpio' property of node '/dwmmc@ff0d0000[0]'
[    7.328767] dwmmc_rockchip ff0d0000.dwmmc: IDMAC supports 32-bit address mode.
[    7.346212] dwmmc_rockchip ff0d0000.dwmmc: Using internal DMA controller.
[    7.348372] dwmmc_rockchip ff0d0000.dwmmc: Version ID is 270a
[    7.350511] dwmmc_rockchip ff0d0000.dwmmc: DW MMC controller at irq 30,32 bit host data width,256 deep fifo
[    7.352693] dwmmc_rockchip ff0d0000.dwmmc: 'clock-freq-min-max' property was deprecated.
[    7.354863] dwmmc_rockchip ff0d0000.dwmmc: No vmmc regulator found
[    7.356997] dwmmc_rockchip ff0d0000.dwmmc: No vqmmc regulator found
[    7.359125] dwmmc_rockchip ff0d0000.dwmmc: GPIO lookup for consumer wp
[    7.359129] dwmmc_rockchip ff0d0000.dwmmc: using device tree for GPIO lookup
[    7.359134] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0d0000[0]'
[    7.359139] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0d0000[0]'
[    7.359144] dwmmc_rockchip ff0d0000.dwmmc: using lookup tables for GPIO lookup
[    7.359148] dwmmc_rockchip ff0d0000.dwmmc: lookup for GPIO wp failed
[    7.359297] dwmmc_rockchip ff0d0000.dwmmc: allocated mmc-pwrseq
[    7.375399] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    7.395416] dwmmc_rockchip ff0d0000.dwmmc: 1 slots initialized
[    7.449146] mmc_host mmc2: Bus speed (slot 0) = 49500000Hz (slot req 50000000Hz, actual 49500000HZ div = 0)
[    7.484563] mmc2: new high speed SDIO card at address 0001
[    7.506512] EXT4-fs (mmcblk1p2): couldn't mount as ext3 due to feature incompatibilities
[    7.511000] EXT4-fs (mmcblk1p2): couldn't mount as ext2 due to feature incompatibilities
[    7.519680] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    8.193871] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[    8.629503] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Reply
#3
Quote:Getting these errors on the EMMC? What to do ?

Check if Armbian has fixed those problems? I don't recall seing them.
https://www.armbian.com/tinkerboard/

Try kernel 4.4.y and 5.4.y ... they are very different in low level support with many fixes on top of Tinker (4.4.y only) kernel.
Armbian. Lightweight Debian Stretch or Ubuntu Bionic for Tinker Board.
Reply
#4
Will test it, buth i have 23 Thinkerboard S running wich al show these problems after updating them.
Before i didn't notice something buth now i have 3 Thinkerboards wich are running in to this problem...
Reply
#5
Its also possible that its hardware failure. Flash media just die once ... and again with Armbian, due to many optimisations which saves eMMC/SD life, flash will live much much longer.
Armbian. Lightweight Debian Stretch or Ubuntu Bionic for Tinker Board.
Reply
#6
Hmmm. hardware faillure on all the devices at once (installed at different dates).

Wich version of armbian do you advise, we run Google Assitant, Amazon Alexa, MQTT, Homekit and a NodeJS server, an apache server (thinking about NGINX), 2 SHH Tunnels (24/7) and a MYSQL Server. No need of an UI, CLI is fine
Reply
#7
(01-26-2020, 12:38 PM)JornHermans Wrote: Hmmm. hardware faillure on all the devices at once (installed at different dates).

Yeah, that looks more like a sw issue. Probably eMMC driver itself.


If you are good with TinkerOS, Armbian Buster will be the same on software compatibility level. Also safe is Bionic but there you get packages from Ubuntu. Which can be an advantage or calling for troubles. Depends on your specific use case - I don't deal with things you have, so its hard to say.


Also kernel 5.4.y should cover this, but low level things - if you use any - might be setup different way.
Armbian. Lightweight Debian Stretch or Ubuntu Bionic for Tinker Board.
Reply
#8
Installing Armbian Buster solves the problem i have the idea it is runing smoother also...

Question is what to do with the 23 other devices wich are already deployed with tinkeros on them.
I don't know a way of flashing them remotely en setting them up al over again.

Is there a way to fix this software issue on de tinkeros, so that i can reflash them when we are i the opertunity and nearby the device with the old tinkeros on it.
Reply
#9
Quote:Question is what to do with the 23 other devices wich are already deployed with tinkeros on them.

Install Armbian the same way as you did for failed ones. Going from demo OS to a proper actively developed and supported Linux distribution is a huge step.

Quote:I don't know a way of flashing them remotely en setting them up al over again.

You expect a lot from freely available software. Even Armbian does not provide remote clean OS re-flashing / OTA upgrade, but anything is possible to develop if resources are available.

Quote:Is there a way to fix this software issue on de tinkeros, so that i can reflash them when we are i the opertunity and nearby the device with the old tinkeros on it.

Sure, you (somebody) just need to start maintaining it. Which is not cheap, especially if you do it for yourself only - Armbian maintaining costs are currently around 3.000 EUR / day (not just Tinkerboard) and we have no desire to add maintaining yet another & outdated (Tinker)OS to the costs.
Armbian. Lightweight Debian Stretch or Ubuntu Bionic for Tinker Board.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)