SD card of Raspberry Pi dead - after almost (or only?) a year runtime

Written by Claudio Kuenzler - 0 comments

Published on July 6th 2016 - Listed in Hardware Linux

---

In a previous article I wrote about Raspberry Pi SD card issue after power outage (constant red led). That was a month ago at the begin of June 2016. Back then I was able to "fix" the SD card and therefore save the Raspbian OS by running fsck on it.

Seems that was just the beginning. As of today, the card is defect. I cannot even run fsck on it anymore. dmesg shows:

Jul  6 10:55:43 kernel: [14554.229237] mmc0: Timeout waiting for hardware interrupt.
Jul  6 10:55:43 kernel: [14554.231234] ------------[ cut here ]------------
Jul  6 10:55:43 kernel: [14554.231255] WARNING: CPU: 0 PID: 0 at /build/linux-lts-vivid-naHA4g/linux-lts-vivid-3.19.0/drivers/mmc/host/sdhci.c:1013 sdhci_send_command+0x336/0x390 [sdhci]()
Jul  6 10:55:43 kernel: [14554.231256] Modules linked in: xfs libcrc32c jfs nls_iso8859_1 mmc_block vmnet(OE) vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) hid_plantronics cdc_mbim cdc_wdm cdc_ncm usbnet mii qcserial usb_wwan usbserial pn544_mei mei_phy pn544 hci nfc arc4 dell_wmi sparse_keymap dell_laptop dcdbas i8k rfcomm dm_multipath scsi_dh bnep intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_usb_audio binfmt_misc snd_usbmidi_lib hid_logitech_hidpp snd_hda_codec_hdmi uvcvideo iwlmvm videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media snd_hda_codec_realtek snd_hda_codec_generic mac80211 joydev serio_raw snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep btusb snd_soc_rt5640 snd_soc_rl6231 bluetooth snd_soc_core snd_compress snd_pcm_dmaengine snd_seq_midi snd_seq_midi_event snd_rawmidi iwlwifi snd_seq snd_seq_device cfg80211 lpc_ich snd_pcm shpchp mei_me mei snd_timer 8250_fintek snd dell_smo8800 soundcore i2c_hid dw_dmac dw_dmac_core snd_soc_sst_acpi 8250_dw i2c_designware_platform dell_rbtn spi_pxa2xx_platform i2c_designware_core mac_hid parport_pc ppdev lp parport dm_mirror dm_region_hash dm_log hid_generic hid_logitech_dj usbhid hid psmouse i915 ahci libahci sdhci_pci i2c_algo_bit drm_kms_helper e1000e drm ptp pps_core wmi video sdhci_acpi sdhci
Jul  6 10:55:43 kernel: [14554.231298] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W  OE  3.19.0-32-generic #37~14.04.1-Ubuntu
Jul  6 10:55:43 kernel: [14554.231299] Hardware name: Dell Inc. Latitude E7440/07F3F4, BIOS A09 05/01/2014
Jul  6 10:55:43 kernel: [14554.231300]  ffffffffc02b2460 ffff88041ea03d28 ffffffff817af41b 0000000000000000
Jul  6 10:55:43 kernel: [14554.231301]  0000000000000000 ffff88041ea03d68 ffffffff81074daa 0000000000000004
Jul  6 10:55:43 kernel: [14554.231303]  0000000000000002 ffff88040b4bd500 ffff880407053310 ffff8804070532d0
Jul  6 10:55:43 kernel: [14554.231305] Call Trace:
Jul  6 10:55:43 kernel: [14554.231306]  <IRQ>  [<ffffffff817af41b>] dump_stack+0x45/0x57
Jul  6 10:55:43 kernel: [14554.231313]  [<ffffffff81074daa>] warn_slowpath_common+0x8a/0xc0
Jul  6 10:55:43 kernel: [14554.231315]  [<ffffffff81074e9a>] warn_slowpath_null+0x1a/0x20
Jul  6 10:55:43 kernel: [14554.231319]  [<ffffffffc02ae616>] sdhci_send_command+0x336/0x390 [sdhci]
Jul  6 10:55:43 kernel: [14554.231323]  [<ffffffffc02aee85>] sdhci_finish_data+0x115/0x3c0 [sdhci]
Jul  6 10:55:43 kernel: [14554.231325]  [<ffffffff817a9a6d>] ? printk+0x46/0x48
Jul  6 10:55:43 kernel: [14554.231329]  [<ffffffffc02af290>] ? sdhci_finish_command+0x160/0x160 [sdhci]
Jul  6 10:55:43 kernel: [14554.231333]  [<ffffffffc02af315>] sdhci_timeout_timer+0x85/0xc0 [sdhci]
Jul  6 10:55:43 kernel: [14554.231335]  [<ffffffff810daba9>] call_timer_fn+0x39/0x110
Jul  6 10:55:43 kernel: [14554.231339]  [<ffffffffc02af290>] ? sdhci_finish_command+0x160/0x160 [sdhci]
Jul  6 10:55:43 kernel: [14554.231341]  [<ffffffff810dc370>] run_timer_softirq+0x220/0x320
Jul  6 10:55:43 kernel: [14554.231344]  [<ffffffff8104a3e3>] ? lapic_next_deadline+0x33/0x40
Jul  6 10:55:43 kernel: [14554.231346]  [<ffffffff81078f04>] __do_softirq+0xe4/0x270
Jul  6 10:55:43 kernel: [14554.231348]  [<ffffffff810792cd>] irq_exit+0x9d/0xb0
Jul  6 10:55:43 kernel: [14554.231351]  [<ffffffff817b9e4a>] smp_apic_timer_interrupt+0x4a/0x60
Jul  6 10:55:43 kernel: [14554.231353]  [<ffffffff817b7e7d>] apic_timer_interrupt+0x6d/0x80
Jul  6 10:55:43 kernel: [14554.231354]  <EOI>  [<ffffffff8164ff30>] ? cpuidle_enter_state+0x70/0x170
Jul  6 10:55:43 kernel: [14554.231359]  [<ffffffff8164ff1d>] ? cpuidle_enter_state+0x5d/0x170
Jul  6 10:55:43 kernel: [14554.231360]  [<ffffffff816500e7>] cpuidle_enter+0x17/0x20
Jul  6 10:55:43 kernel: [14554.231362]  [<ffffffff810b5424>] cpu_startup_entry+0x334/0x3d0
Jul  6 10:55:43 kernel: [14554.231365]  [<ffffffff8179f987>] rest_init+0x77/0x80
Jul  6 10:55:43 kernel: [14554.231368]  [<ffffffff81d3e101>] start_kernel+0x499/0x4a6
Jul  6 10:55:43 kernel: [14554.231370]  [<ffffffff81d3da58>] ? set_init_arg+0x55/0x55
Jul  6 10:55:43 kernel: [14554.231371]  [<ffffffff81d3d120>] ? early_idt_handler_array+0x120/0x120
Jul  6 10:55:43 kernel: [14554.231373]  [<ffffffff81d3d5ee>] x86_64_start_reservations+0x2a/0x2c
Jul  6 10:55:43 kernel: [14554.231375]  [<ffffffff81d3d733>] x86_64_start_kernel+0x143/0x152
Jul  6 10:55:43 kernel: [14554.231375] ---[ end trace a7dffb2e9a4ede53 ]---
Jul  6 10:55:43 kernel: [14554.237089] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.237092] mmcblk0: error -110 transferring data, sector 8, nr 8, cmd response 0x0, card status 0x0
Jul  6 10:55:43 kernel: [14554.237094] mmcblk0: retrying using single block read
Jul  6 10:55:43 kernel: [14554.239266] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.241358] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.243460] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.245545] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.247592] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.249648] mmcblk0: timed out sending r/w cmd command, card status 0x400f00
Jul  6 10:55:43 kernel: [14554.249651] blk_update_request: I/O error, dev mmcblk0, sector 8
Jul  6 10:55:43 kernel: [14554.249655] Buffer I/O error on dev mmcblk0, logical block 1, async page read

The SD card was bundled with the Raspberry Pi and was bought not even a year ago, on July 17 2015. A few days after this, the Pi started running and displaying our monitoring and was running 24/7.

Are SD cards considered "stable"? I wouldn't say so, as this wasn't the first time I experienced problems with SD cards (see article How to test if a SDHC card is defect or dying). Luckily we only used the Pi for displaying the monitoring status and graphs on the screen, no data was saved on it.

Add a comment

Show form to leave a comment

Comments (newest first)

No comments yet.