BPI-R2 EMMC demaged

After installing OS (Stretch from Frank-FW - boot from SD, root FS on 1 partition emmc /f2fs/) on emmc, and a few hours of operation, emmc was destroyed. There was a message about the wo file system, and after reboot emmc is not detected (it is not in / dev) there is only a message in dmsg:

mmc1: error -110 whilst initialising MMC card.

Something can be done?

regards

mt_werty

Can you access it from sdcard or uboot?

What do you mean with /f2fs/,a filesystem? Why not ext4 for rootfs?

SD is working. Message:

mmc1: error -110 whilst initialising MMC card

i get when OS working from SD (boot from SD mmcblk0p1, root FS mmcblk0p2 /f2fs/)

F2FS? Experiment. Subjectively it is faster - I did not make measurements, but on an SD card (also on R.I.P. EMMC it was so) it works noticeably faster. I didn’t care about reliability - I don’t have anything to care about in the event of a breakdown. I didn’t expect a complete EMMC failure - at most problems with FS.

PS and to tell you the truth, I think f2fs is not the cause here - it has been working for several weeks on the SD card as rootfs.

F2FS is a good filesystem to use on flash storage. And I don’t think your eMMC problems are caused/related to F2FS. It’s more probable that you just been hit by Murphy’s law - your eMMC failed because everything fails from time to time. Still it’d be good idea to show us your kernel messages log (dmesg), at least parts related to mmc* - there might be some more messages hiding there you missed out, who knows? Nevertheless if it’s really the case of failed eMMC chip - it is possible to fix by replacing chip. Look for component level repair shops near your location (i.e. guys who repair motherboards, videocards or mobile phones) and ask them for help. It is like a 15 minutes task for experienced person to replace eMMC chip using bottom heater + hot air soldering gun and eMMC chips are dirt cheap if we’re talking about small storage capacities like 8 or 16GBs.

I think so too. but I paste:

# dmesg|grep mmc
> [    0.000000] Kernel command line: board=bpi-r2 console=earlyprintk console=tty1 fbcon=map:0 console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=f2fs rootwait vmalloc=496M debug=7 initcall_debug=0 video=1280x1024
> 
> [    5.013733] mtk-msdc 11240000.mmc: GPIO lookup for consumer cd
> 
> [    5.019545] mtk-msdc 11240000.mmc: using device tree for GPIO lookup
> 
> [    5.025934] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/mmc@11240000[0]' - status (0)
> [    5.035412] mtk-msdc 11240000.mmc: Got CD GPIO
> 
> [    5.039832] mtk-msdc 11240000.mmc: GPIO lookup for consumer wp
> 
> [    5.045659] mtk-msdc 11240000.mmc: using device tree for GPIO lookup
> 
> [    5.051994] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@11240000[0]'
> 
> [    5.060724] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@11240000[0]'
> 
> [    5.069381] mtk-msdc 11240000.mmc: using lookup tables for GPIO lookup
> 
> [    5.075880] mtk-msdc 11240000.mmc: lookup for GPIO wp failed
> 
> [    5.142558] mtk-msdc 11230000.mmc: GPIO lookup for consumer wp
> 
> [    5.148374] mtk-msdc 11230000.mmc: using device tree for GPIO lookup
> 
> [    5.154757] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@11230000[0]'
> 
> [    5.163508] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@11230000[0]'
> 
> [    5.172166] mtk-msdc 11230000.mmc: using lookup tables for GPIO lookup
> 
> 
> [    5.178651] mtk-msdc 11230000.mmc: lookup for GPIO wp failed
> 
> [    5.228806] mmc0: host does not support reading read-only switch, assuming write-enable
> 
> [    5.239126] mmc0: new high speed SDHC card at address 0007
> 
> [    5.291156] mmcblk0: mmc0:0007 SD32G 29.0 GiB
> 
> [    5.297160]  mmcblk0: p1 p2
> 
> [    8.357693] F2FS-fs (mmcblk0p2): orphan cleanup on readonly fs
> 
> [    8.383593] F2FS-fs (mmcblk0p2): Mounted with checkpoint version = 1178
> 
> [    8.831677] mmc1: error -110 whilst initialising MMC card
> 
> [   12.071539] mmc1: error -110 whilst initialising MMC card
> 
> [   13.245596] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. 
> Please run fsck.
> 
> [   15.331807] mmc1: error -110 whilst initialising MMC card
> 
> [   18.501538] mmc1: error -110 whilst initialising MMC card

it’s after systems crash

Thanks for sharing. Error -110 is ETIMEDOUT thus I’m afraid it’s probably eMMC chip died on you. Or it might be some other hardware problem like cracked solder joint, e.t.c. Replacing eMMC chip with a new one is your best bet for this case.

Thank you very much for help. :slight_smile: