Neo won't boot anymore (corrupt SD card) ?

Discussion in 'UDOO NEO' started by ddewaele, Dec 5, 2015.

  1. ddewaele

    ddewaele Member

    Joined:
    Dec 2, 2014
    Messages:
    48
    Likes Received:
    11
    After a power outage today my UDOO Neo didn't boot anymore.
    When I hooked up a serial cable to see what was wrong I saw the following on /dev/cu.SLAB_USBtoUART298 .

    Seems to be a file-system issue. Can it recover from that or is the sd card bad and do I need to start over ?

    Code:
    
    [    2.032244] EXT4-fs (mmcblk0p2): recovery complete
    [    2.037053] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
    [    2.045250] VFS: Mounted root (ext4 filesystem) on device 179:2.
    [    2.052336] devtmpfs: mounted
    [    2.055524] Freeing unused kernel memory: 260K (80a74000 - 80ab5000)
    [    2.662409] random: init urandom read with 41 bits of entropy available
    [    2.806824] mmcblk0: error -110 sending status command, retrying
    [    2.821034] mmcblk0: error -110 sending status command, retrying
    [    2.829143] mmcblk0: error -110 sending status command, aborting
    [    2.835170] end_request: I/O error, dev mmcblk0, sector 135336
    [    2.841070] EXT4-fs error (device mmcblk0p2): ext4_find_entry:1302: inode #249: comm plymouth-upstar: reading directory lblock 0
    
    [    3.847170] mmcblk0: error -110 sending status command, retrying
    [    3.855254] mmcblk0: error -110 sending status command, aborting
    [    3.861509] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:3940: inode #89654: block 5796: comm init: unable to read itable block
    [    3.878103] mmcblk0: error -110 sending status command, retrying
    [    3.884166] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    3.893140] mmcblk0: error -110 sending status command, retrying
    [    3.954766] mmcblk0: error -110 sending status command, aborting
    [    3.960827] Buffer I/O error on device mmcblk0p2, logical block 0
    [    3.966944] lost page write due to I/O error on mmcblk0p2
    [    3.972757] init: startpar-bridge (plymouth-ready-startup-started) main process (89) terminated with status 2
    [    3.986982] mmcblk0: error -110 sending status command, retrying
    [    4.058382] mmcblk0: error -110 sending status command, aborting
    [    4.064661] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:3940: inode #89654: block 5796: comm init: unable to read itable block
    [    4.081305] mmcblk0: error -110 sending status command, retrying
    [    4.089425] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    4.096365] mmcblk0: error -110 sending status command, retrying
    [    4.159364] mmcblk0: error -110 sending status command, aborting
    [    4.165404] Buffer I/O error on device mmcblk0p2, logical block 0
    [    4.171552] lost page write due to I/O error on mmcblk0p2
    [    4.181725] mmcblk0: error -110 sending status command, retrying
    [    4.225464] mmcblk0: error -110 sending status command, aborting
    [    4.231751] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:3940: inode #89654: block 5796: comm init: unable to read itable block
    [    4.244296] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    4.263466] mmcblk0: error -110 sending status command, retrying
    [    4.271550] mmcblk0: error -110 sending status command, aborting
    [    4.277589] Buffer I/O error on device mmcblk0p2, logical block 0
    [    4.283720] lost page write due to I/O error on mmcblk0p2
    [    4.294291] mmcblk0: error -110 sending status command, retrying
    [    4.302446] mmcblk0: error -110 sending status command, retrying
    [    4.310559] mmcblk0: error -110 sending status command, aborting
    [    4.316786] EXT4-fs error (device mmcblk0p2): __ext4_get_inode_loc:3940: inode #89654: block 5796: comm init: unable to read itable block
    [    4.329344] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    4.340409] mmcblk0: error -110 sending status command, retrying
    [    4.348512] mmcblk0: error -110 sending status command, retrying
    [    4.356607] mmcblk0: error -110 sending status command, aborting
    [    4.362675] Buffer I/O error on device mmcblk0p2, logical block 0
    [    4.368791] lost page write due to I/O error on mmcblk0p2
    [    4.378812] mmcblk0: error -110 sending status command, retrying
    [    4.386941] mmcblk0: error -110 sending status command, retrying
    [    4.395041] mmcblk0: error -110 sending status command, aborting
    [    4.401285] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    4.412453] mmcblk0: error -110 sending status command, retrying
    [    4.420541] mmcblk0: error -110 sending status command, retrying
    [    4.428605] mmcblk0: error -110 sending status command, aborting
    [    4.435057] init: startpar-bridge (hostname--started) main process (88) terminated with status 2
    [    4.448262] mmcblk0: error -110 sending status command, retrying
    [    4.456559] mmcblk0: error -110 sending status command, retrying
    [    4.463715] mmcblk0: error -110 sending status command, aborting
    [    4.474080] mmcblk0: error -110 sending status command, retrying
    [    4.482188] mmcblk0: error -110 sending status command, retrying
    [    4.490308] mmcblk0: error -110 sending status command, aborting
    [    4.496519] EXT4-fs (mmcblk0p2): previous I/O error to superblock detected
    [    4.577379] mmcblk0: error -110 sending status command, aborting
    [    4.583840] init: startpar-bridge (plymouth-upstart-bridge--started) main process (90) terminated with status 2
    [    6.341137] init: plymouth-stop pre-start process (106) terminated with status 2
    [    6.353207] mmcblk0: error -110 sending status command, retrying
    [    6.448657] mmcblk0: error -110 sending status command, aborting
    [    6.455123] init: startpar-bridge (console-setup--stopped) main process (107) terminated with status 2
    [    6.468843] mmcblk0: error -110 sending status command, retrying
    [    6.477144] mmcblk0: error -110 sending status command, retrying
    Filesystem check or mount failed.
    A maintenance shell will now be[    6.645841] mmcblk0: error -110 sending status command, aborting
    started.
    CONTROL-D will terminate this shell and continue bootin[    6.659927] mmcblk0: error -110 sending status command, retrying
    g after re-trying
    filesystems.  [    6.668693] mmcblk0: error -110 sending status command, retrying
    Any further errors will be ignore[    6.677618] mmcblk0: error -110 sending status command, aborting
    d
    [    6.688601] mmcblk0: error -110 sending status command, retrying
    [    6.696721] mmcblk0: error -110 sending status command, retrying
    [    6.704790] mmcblk0: error -110 sending status command, aborting
    [    6.715592] mmcblk0: error -110 sending status command, retrying
    [    6.723710] mmcblk0: error -110 sending status command, retrying
    [    6.731788] mmcblk0: error -110 sending status command, aborting
    /proc/self/fd/9: 21: /proc/self/f[    6.743125] mmcblk0: error -110 sending status command, retrying
    /proc/self/fd/9: 6: exec: [    7.121072] init: mountall-shell post-stop process (112) terminated with status 2
    [    7.150574] mmcblk0: error -110 sending status command, retrying
    [    7.212920] mmcblk0: error -110 sending status command, retrying
    [    7.221009] mmcblk0: error -110 sending status command, aborting
    [    7.227375] init: startpar-bridge (mountall-shell--stopped) main process (113) terminated with status 2
    [    7.241214] mmcblk0: error -110 sending status command, retrying
    [    8.096204] blk_update_request: 1420 callbacks suppressed
    [    8.102060] end_request: I/O error, dev mmcblk0, sector 2164736
    [    8.108173] quiet_error: 33 callbacks suppressed
    [    8.113026] Buffer I/O error on device mmcblk0p2, logical block 262144
    [    8.120075] lost page write due to I/O error on mmcblk0p2
    [    8.125513] JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8.
    [    8.137687] mmcblk0: error -110 sending status command, retrying
    [    8.145819] mmcblk0: error -110 sending status command, retrying
    [    8.153899] mmcblk0: error -110 sending status command, aborting
    [    8.159942] end_request: I/O error, dev mmcblk0, sector 2164744
    [    8.165883] end_request: I/O error, dev mmcblk0, sector 2164752
    [    8.171844] end_request: I/O error, dev mmcblk0, sector 2164760
    [    8.177802] Aborting journal on device mmcblk0p2-8.
    [    8.186882] mmcblk0: error -110 sending status command, retrying
    [    8.194979] mmcblk0: error -110 sending status command, retrying
    [    8.203058] mmcblk0: error -110 sending status command, aborting
    [    8.209107] end_request: I/O error, dev mmcblk0, sector 2164736
    [    8.215052] Buffer I/O error on device mmcblk0p2, logical block 262144
    [    8.221613] lost page write due to I/O error on mmcblk0p2
    [    8.227044] JBD2: Error -5 detected when updating journal superblock for mmcblk0p2-8.
    [   41.689079] random: nonblocking pool is initialized
    
     
  2. ddewaele

    ddewaele Member

    Joined:
    Dec 2, 2014
    Messages:
    48
    Likes Received:
    11
    Issue was related to a faulty USB (power) cable.
     

Share This Page