eMMC failure?

Hi,
After 2 days of really light usage (only some doker fun), my fs collapsed...
Is this soma HW failure? - I mean is there any chance that my eMMC is DOA?

Code:

[32m[182445.282483] [0m[33mIPv6[0m: ADDRCONF(NETDEV_UP): veth8c4ca86: link is not ready
[32m[182445.466635] [0m[33meth0[0m: renamed from vethfc1102d
[32m[182445.490100] [0m[33mIPv6[0m: ADDRCONF(NETDEV_CHANGE): veth8c4ca86: link becomes ready
[32m[182445.490149] [0m[33mdocker0[0m: port 2(veth8c4ca86) entered forwarding state
[32m[182445.490166] [0m[33mdocker0[0m: port 2(veth8c4ca86) entered forwarding state
[32m[182460.529799] [0m[33mdocker0[0m: port 2(veth8c4ca86) entered forwarding state
[32m[182578.873293] [0m[33msdhci[0m: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
[32m[182588.885696] [0m[33mmmc0[0m[31m: Timeout waiting for hardware interrupt.[0m
[32m[182588.908875] [0m[1m------------[ cut here ]------------[0m
[32m[182588.908920] [0m[33mWARNING[0m[1m: CPU: 3 PID: 0 at /build/linux-W6HB68/linux-4.4.0/drivers/mmc/host/sdhci.c:1017 sdhci_send_command+0x714/0xc30 [sdhci]()[0m
[32m[182588.908934] [0m[33mModules linked in[0m[1m: xt_nat xt_tcpudp nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc fscache veth ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs hid_generic ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_rapl snd_hda_intel intel_powerclamp coretemp snd_hda_codec kvm_intel snd_hda_core kvm joydev irqbypass input_leds snd_hwdep punit_atom_debug snd_pcm snd_timer lpc_ich snd shpchp soundcore mei_txe mei tpm_crb 8250_fintek dw_dmac dwc3 dw_dmac_core udc_core i2c_designware_platform pwm_lpss_platform i2c_designware_core ulpi[0m
[32m[182588.909396] [0m[1m 8250_dw spi_pxa2xx_platform pwm_lpss mac_hid soc_button_array cdc_acm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_logitech_hidpp i915 mmc_block hid_logitech_dj i2c_algo_bit crct10dif_pclmul crc32_pclmul drm_kms_helper ghash_clmulni_intel syscopyarea sysfillrect aesni_intel sysimgblt aes_x86_64 lrw gf128mul r8169 glue_helper usbhid ablk_helper fb_sys_fops cryptd mii hid drm ahci libahci sdhci_acpi fjes video sdhci pinctrl_cherryview[0m
[32m[182588.909782] [0m[33mCPU[0m[1m: 3 PID: 0 Comm: swapper/3 Tainted: G        W       4.4.0-62-generic #83-Ubuntu[0m
[32m[182588.909794] [0m[33mHardware name[0m[1m: SECO UDOO x86/UDOO x86, BIOS 1.01 02/20/2017[0m
[32m[182588.909807] [0m[1m 0000000000000086 ebcdf14d67db22bb ffff88017fd83d28 ffffffff813f7c63[0m
[32m[182588.909827] [0m[1m 0000000000000000 ffffffffc003a460 ffff88017fd83d60 ffffffff810812d2[0m
[32m[182588.909845] [0m[1m ffff880072eff540 ffff8801764032d8 0000000000000012 0000000000000001[0m
[32m[182588.909865] [0m[1mCall Trace:[0m
[32m[182588.909877] [0m[1m <IRQ>  [<ffffffff813f7c63>] dump_stack+0x63/0x90[0m
[32m[182588.909928] [0m[1m [<ffffffff810812d2>] warn_slowpath_common+0x82/0xc0[0m
[32m[182588.909944] [0m[1m [<ffffffff8108141a>] warn_slowpath_null+0x1a/0x20[0m
[32m[182588.909968] [0m[1m [<ffffffffc0037914>] sdhci_send_command+0x714/0xc30 [sdhci][0m
[32m[182588.909991] [0m[1m [<ffffffff81404dbb>] ? __const_udelay+0x2b/0x30[0m
[32m[182588.910013] [0m[1m [<ffffffffc0034d49>] ? sdhci_reset+0x59/0xc0 [sdhci][0m
[32m[182588.910036] [0m[1m [<ffffffffc0037f32>] sdhci_finish_data+0x102/0x350 [sdhci][0m
[32m[182588.910059] [0m[1m [<ffffffffc0038180>] ? sdhci_finish_data+0x350/0x350 [sdhci][0m
[32m[182588.910081] [0m[1m [<ffffffffc00381fb>] sdhci_timeout_timer+0x7b/0xc0 [sdhci][0m
[32m[182588.910103] [0m[1m [<ffffffff810ecd55>] call_timer_fn+0x35/0x120[0m
[32m[182588.910125] [0m[1m [<ffffffffc0038180>] ? sdhci_finish_data+0x350/0x350 [sdhci][0m
[32m[182588.910142] [0m[1m [<ffffffff810ed70a>] run_timer_softirq+0x23a/0x2f0[0m
[32m[182588.910165] [0m[1m [<ffffffff81085db1>] __do_softirq+0x101/0x290[0m
[32m[182588.910182] [0m[1m [<ffffffff810860b3>] irq_exit+0xa3/0xb0[0m
[32m[182588.910201] [0m[1m [<ffffffff8183b0a2>] smp_apic_timer_interrupt+0x42/0x50[0m
[32m[182588.910223] [0m[1m [<ffffffff81839362>] apic_timer_interrupt+0x82/0x90[0m
[32m[182588.910232] [0m[1m <EOI>  [<ffffffff816cb5d1>] ? cpuidle_enter_state+0x111/0x2b0[0m
[32m[182588.910268] [0m[1m [<ffffffff816cb7a7>] cpuidle_enter+0x17/0x20[0m
[32m[182588.910288] [0m[1m [<ffffffff810c4522>] call_cpuidle+0x32/0x60[0m
[32m[182588.910304] [0m[1m [<ffffffff816cb783>] ? cpuidle_select+0x13/0x20[0m
[32m[182588.910323] [0m[1m [<ffffffff810c47e0>] cpu_startup_entry+0x290/0x350[0m
[32m[182588.910347] [0m[1m [<ffffffff81051784>] start_secondary+0x154/0x190[0m
[32m[182588.910366] [0m[1m---[ end trace a75223f48bc47874 ]---[0m
[32m[182588.912655] [0m[33mmmcblk0[0m: error -110 sending stop command, original cmd response 0x0, card status 0x400900
[32m[182588.913066] [0m[33mmmcblk0[0m[31m: error -110 transferring data, sector 25664576, nr 144, cmd response 0x0, card status 0x0[0m
[32m[182588.924130] [0m[33mblk_update_request[0m[1m: 118 callbacks suppressed[0m
[32m[182588.924138] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664576[0m
[32m[182588.931572] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664584[0m
[32m[182588.938716] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664592[0m
[32m[182588.944533] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664600[0m
[32m[182588.950266] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664608[0m
[32m[182588.955930] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664616[0m
[32m[182588.961535] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664624[0m
[32m[182588.967088] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664632[0m
[32m[182588.972553] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664640[0m
[32m[182588.977980] [0m[33mblk_update_request[0m[31m: I/O error, dev mmcblk0, sector 25664648[0m
[32m[182588.983380] [0m[31mAborting journal on device mmcblk0p1-8.[0m
[32m[182588.984452] [0m[33mEXT4-fs (mmcblk0p1)[0m[1m[31m: ext4_writepages: jbd2_start: 9223372036854775807 pages, ino 284387; err -30[0m
[32m[182589.000548] [0m[33mmmcblk0[0m[31m: error -84 sending status command, retrying[0m
[32m[182589.024206] [0m[33mmmcblk0[0m: error -84 sending stop command, original cmd response 0x900, card status 0x900
[32m[182589.024249] [0m[33mmmcblk0[0m: retrying because a re-tune was needed
[32m[182589.027668] [0m[33mEXT4-fs error (device mmcblk0p1)[0m[1m[31m: ext4_journal_check_start:56: Detected aborted journal[0m
[32m[182589.036281] [0m[33mEXT4-fs (mmcblk0p1)[0m[1m[31m: Remounting filesystem read-only[0m
[32m[182714.323308] [0m[33mdocker0[0m: port 2(veth8c4ca86) entered disabled state
[32m[182714.323502] [0m[33mvethfc1102d[0m: renamed from eth0
]0;maara@alkoholik: ~/dockerimm[01;32mmaara@alkoholik[00m:[01;34m~/dockerimm[00m$ sudo reboot

Thanks!

 

Hi @maara,
could you please open a ticket? We will closely take care of the problem.

 

At least it is not a DOA (Dead On Arrival), it worked when you got it . eMMC is like an SD card so you have to be cautious in switching off abruptly (pull the power plug). I don't know if eMMC in the X86 is protected against power interrupts but better safe then sorry.

 

Just for reference: what is the expected life of the eMMC chip you used?

 

Here is the exact EMMC IC used for the 32GB on my Ultra UDOO X86, SDINADF4-32G
http://www.mouser.com/ds/2/669/sandisk_12282015_Commercial Embedded Product Brief-792691.pdf

It is the high end model chip, so I cannot speak for the 8gb variant.
NAND® 7232
Fine-tuned for use in:
-Flagship Smartphones
-High-end Tablets
-Compute
16GB to 128GB
eMMC 5.1, HS400
Second Generation iNAND Accelerator Architecture Featuring SmartSLC technology
Command Queue
Seq Write upto 150MB/s

And sorry, I don't see a write lifetime or other value listed on the datasheet. Again, this is the higher end memory model NAND® 7232 for "High-end Tablets" and "Flagship Smartphones.

 

The eMMC used is 4.5 not 5.0 or 5.1 due to the SoC limitation.

 

The SDINADF4-32G is in its End of Life stage being superseded by an improved model, nonetheless I was unable to find any expected endurance or write-cycles parameter...
My concern is, if I use it to install my OS, am I going to kill it in a year or two considering the write rate of temporary files and swap?

 

use sync in scripts

 

Writes any data buffered in memory out to disk. This can include (but is not limited to) modified superblocks, modified inodes, and delayed reads and writes.
This must be implemented by the kernel; The `sync' program does nothing but exercise the `sync' system call. The kernel keeps data in memory to avoid doing (relatively slow) disk reads and writes. This improves performance, but if the computer crashes, data can be lost or the filesystem corrupted as a result. `sync' ensures everything in memory is written to disk.

Any arguments are ignored, except for a lone `--help' or `--version'

"The way to a mans heart is through his stomach" - Fanny Fern (writer)
​

It's hard for me to understand how that might help extend the flash life, especially considering there will be plenty of services and apps running on the system outside of my control and also I've never mentioned I would like to go GNU/Linux...

Apparently I'm being misunderstood or I didn't describe my concerns appropriately

 

Sorry, I'm newbie to linux and was remembering Unix from years ago. Your concerns are appropriate - I'm wrong.

 

I hope SEC will sort this out for you. I'm one of the pre-orders that'll have to wait a while 'til I get mine. Better to remain silent and be thought a fool than to speak out and remove all doubt.

 

@Brian McConnon, please do not be put off from participating in the community. Reaching a solution sometimes involves making little mistakes along the way, and no one here views them as foolish, because they understand that mistakes are part of the maker learning process

 

Thank you, you are kind.