Strange disk errors (with Ubuntu)

Discussion in 'Troubleshooting' started by Stefano Tognon, Nov 10, 2017.

  1. Stefano Tognon

    Stefano Tognon New Member

    Joined:
    Nov 10, 2017
    Messages:
    9
    Likes Received:
    3
    hi,

    I started to use the Udoo X64 board only from 2 months and it runs 24h/24h as a little BOINC server (20 clients attacched, but BOINC is running only from two weeks).

    However after less of 7 weeks of usage I had Ubuntu thathas mount the filesystem as read only for disk errors (I use EXT4 filesystem on the eMMC intenal 32GB disk).
    After a reboot I need to fix some orphan inodes by hand.
    Yesterday I get the same errors, so now looking to log message, I get many messages like this:

    Nov 10 22:27:25 udoox64 kernel: [ 6336.771086] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure
    , falling back to fixed sampling clock
    Nov 10 22:27:35 udoox64 kernel: [ 6346.804180] mmc0: Timeout waiting for hardware interrupt.
    Nov 10 22:27:35 udoox64 kernel: [ 6346.806446] ------------[ cut here ]------------
    Nov 10 22:27:35 udoox64 kernel: [ 6346.806499] WARNING: CPU: 2 PID: 0 at /build/linux-3phnTq/linux-4.4.0/drivers/mmc/host/sdh
    ci.c:1018 sdhci_send_command+0x714/0xc30 [sdhci]()
    Nov 10 22:27:35 udoox64 kernel: [ 6346.806509] Modules linked in: cdc_acm snd_hda_codec_hdmi intel_rapl snd_hda_codec_realtek
    intel_powerclamp snd_hda_codec_generic coretemp kvm_intel snd_hda_intel kvm snd_hda_codec snd_hda_core joydev irqbypass puni
    t_atom_debug mei_txe input_leds snd_hwdep snd_pcm mei snd_timer shpchp lpc_ich snd soundcore 8250_fintek dwc3 dw_dmac udc_cor
    e dw_dmac_core pwm_lpss_platform ulpi i2c_designware_platform i2c_designware_core soc_button_array 8250_dw tpm_crb pwm_lpss m
    ac_hid spi_pxa2xx_platform ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT n
    f_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack i
    p6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast ib_iser nf_nat_ftp rdma_cm nf_nat iw_cm nf_conntrack
    _ftp ib_cm ib_sa nf_conntrack ib_mad ib_core iptable_filter ib_addr ip_tables iscsi_tcp x_tables libiscsi_tcp libiscsi scsi_t
    ransport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c
    raid1 raid0 multipath linear mmc_block crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 aesni_intel aes_x86_64 lrw gf1
    28mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm
    mii libahci fjes hid_generic video sdhci_acpi sdhci usbhid hid
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807271] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G W 4.4.0-98-generic #121-
    Ubuntu
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807283] Hardware name: SECO UDOO x86/UDOO x86, BIOS 1.03 08/04/2017
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807296] 0000000000000086 6dccc0fd639cc83d ffff88017fd03d28 ffffffff813fb2c3
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807316] 0000000000000000 ffffffffc0024460 ffff88017fd03d60 ffffffff810812e2
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807335] ffff88017a7af540 ffff88017a46f930 0000000000000001 0000000000000001
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807355] Call Trace:
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807367] <IRQ> [<ffffffff813fb2c3>] dump_stack+0x63/0x90
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807415] [<ffffffff810812e2>] warn_slowpath_common+0x82/0xc0
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807434] [<ffffffff8108142a>] warn_slowpath_null+0x1a/0x20
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807458] [<ffffffffc00219e4>] sdhci_send_command+0x714/0xc30 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807477] [<ffffffff8140847b>] ? __const_udelay+0x2b/0x30
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807499] [<ffffffffc001ede9>] ? sdhci_reset+0x59/0xc0 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807523] [<ffffffffc0022002>] sdhci_finish_data+0x102/0x350 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807546] [<ffffffffc0022250>] ? sdhci_finish_data+0x350/0x350 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807569] [<ffffffffc00222cb>] sdhci_timeout_timer+0x7b/0xc0 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807591] [<ffffffff810ecfc5>] call_timer_fn+0x35/0x120
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807614] [<ffffffffc0022250>] ? sdhci_finish_data+0x350/0x350 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807569] [<ffffffffc00222cb>] sdhci_timeout_timer+0x7b/0xc0 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807591] [<ffffffff810ecfc5>] call_timer_fn+0x35/0x120
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807614] [<ffffffffc0022250>] ? sdhci_finish_data+0x350/0x350 [sdhci]
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807633] [<ffffffff810ed97a>] run_timer_softirq+0x23a/0x2f0
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807656] [<ffffffff81085dc1>] __do_softirq+0x101/0x290
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807676] [<ffffffff810860c3>] irq_exit+0xa3/0xb0
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807695] [<ffffffff81847162>] smp_apic_timer_interrupt+0x42/0x50
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807718] [<ffffffff81845422>] apic_timer_interrupt+0x82/0x90
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807727] <EOI> [<ffffffff816d69a1>] ? cpuidle_enter_state+0x111/0x2b0
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807759] [<ffffffff816d6b77>] cpuidle_enter+0x17/0x20
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807779] [<ffffffff810c4752>] call_cpuidle+0x32/0x60
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807793] [<ffffffff816d6b53>] ? cpuidle_select+0x13/0x20
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807810] [<ffffffff810c4a10>] cpu_startup_entry+0x290/0x350
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807830] [<ffffffff81051844>] start_secondary+0x154/0x190
    Nov 10 22:27:35 udoox64 kernel: [ 6346.807845] ---[ end trace 47d966c9f1c9b9f2 ]---
    Nov 10 22:27:35 udoox64 kernel: [ 6346.810354] mmcblk0: error -110 sending stop command, original cmd response 0x0, card status 0x400900
    Nov 10 22:27:35 udoox64 kernel: [ 6346.810656] mmcblk0: error -110 transferring data, sector 2577640, nr 8, cmd response 0x0, card status 0x0
    Nov 10 22:27:35 udoox64 kernel: [ 6346.811110] blk_update_request: I/O error, dev mmcblk0, sector 2577640
    Nov 10 22:27:35 udoox64 kernel: [ 6346.811409] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:330: I/O error -5 writing to inode 395341 (offset 0 size 0 starting block 322206)
    Nov 10 22:27:35 udoox64 kernel: [ 6346.811442] Buffer I/O error on device mmcblk0p1, logical block 321949
    Nov 10 22:27:35 udoox64 kernel: [ 6346.818461] mmcblk0: error -84 sending status command, retrying
    Nov 10 22:27:35 udoox64 kernel: [ 6346.825240] mmcblk0: error -84 sending stop command, original cmd response 0x900, card status 0x900
    Nov 10 22:27:35 udoox64 kernel: [ 6346.825542] mmcblk0: retrying because a re-tune was needed

    In the past I had uses Raspberry Pi and Pine 64 as 24h/24h pool servers (with a cpu/ram usage that get 100% of resources almost all the time) without having a single ploblem using SD memory as disk. When I get errors, it was after 1,5 years of 24h/24h usage as SD memory finish his write cycles and get broken.

    From my experience, those errors seems related to broken hardware, but maybe it could comes from some kernel/driver bugs onto EXT4 filesystem, but in this case I expect that many users had find that issues too.

    Any idea?

    This is the Ubuntu used:
    Distributor ID: Ubuntu
    Description: Ubuntu 16.04.3 LTS
    Release: 16.04
    Codename: xenial

    Thanks
     
  2. Laura

    Laura UDOOer

    Joined:
    Apr 22, 2016
    Messages:
    374
    Likes Received:
    155
    Sorry @Stefano Tognon that this thread was mislaid in the moderation queue. Are you still experiencing this error? If yes, could you please open a support ticket and a technician from the customer care team will look into it for you.

    To open a ticket, click on the following link: https://www.udoo.org/customer-care/
     

Share This Page