<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Corrupted file system on eMMC with iMX6SL in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499981#M80780</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Samuel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;corruptions can be caused by sudden turning off board power,&amp;nbsp; so&lt;/P&gt;&lt;P&gt;recommended to use linux command poweroff. Also in general flash&lt;/P&gt;&lt;P&gt;memory has a limited lifespan with a limited number of write cycles, so&lt;/P&gt;&lt;P&gt;one can try brand new emmc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Apr 2016 01:36:58 GMT</pubDate>
    <dc:creator>igorpadykov</dc:creator>
    <dc:date>2016-04-13T01:36:58Z</dc:date>
    <item>
      <title>Corrupted file system on eMMC with iMX6SL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499980#M80779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We observe sometimes a file system corruption on the eMMC that we are not able to explain. Once it happened, either on rootfs or on data partition, the system is still working but affected files cannot be accessed as input / output error appears when we try to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The output 'fsck' the command is as following :&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;fsck from util-linux 2.27.1&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;e2fsck 1.42.13 (17-May-2015)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;/dev/sdc2 contains a file system with errors, check forced.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Pass 1: Checking inodes, blocks, and sizes&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Pass 2: Checking directory structure&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Entry 'bluetooth' in /var/lib (4103) has deleted/unused inode 16391.&amp;nbsp; Clear? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Entry 'bluetooth' in /var/lib (4103) has an incorrect filetype (was 2, should be 0).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Fix? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Entry 'dropbear' in /etc (8193) has deleted/unused inode 16390.&amp;nbsp; Clear? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Entry 'dropbear' in /etc (8193) has an incorrect filetype (was 2, should be 0).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Fix? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Entry 'random-seed' in /etc (8193) has deleted/unused inode 8243.&amp;nbsp; Clear? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Pass 3: Checking directory connectivity&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Pass 4: Checking reference counts&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Pass 5: Checking group summary information&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Block bitmap differences:&amp;nbsp; -36700 -65798 -(66561--66562)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Fix? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Inode bitmap differences:&amp;nbsp; -8243 -(16390--16392) -16394&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Fix? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Directories count wrong for group #8 (6, counted=3).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;Fix? no&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;/dev/sdc2: ********** WARNING: Filesystem still has errors **********&lt;/SPAN&gt;&lt;SPAN class="para_break" style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;&lt;EM class="copy_only" style="font-size: 0px; background-position: no-repeat;"&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #2c2d30; font-family: Slack-Lato, appleLogo, sans-serif; background-color: #f9f9f9;"&gt;/dev/sdc2: 941/32768 files (17.3% non-contiguous), 58432/131072 blocks&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our system configuration :&lt;/P&gt;&lt;P&gt;- iMX6SL&lt;/P&gt;&lt;P&gt;- eMMC Micron in MCP package (&lt;SPAN style="color: #000000; font-family: Arial; font-size: 16px;"&gt;MT29PZZZ4D4BKESK-18&lt;/SPAN&gt;)&lt;/P&gt;&lt;P&gt;- Freescale BSP 3.14.52&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any known issues on that topic? Can mistake be on driver side? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For now, only way to fix it is formatting corrupted partition. Is there any other workaround which would fix file system without formatting (keeping data alive)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Samuel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Apr 2016 17:37:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499980#M80779</guid>
      <dc:creator>samuelrythm</dc:creator>
      <dc:date>2016-04-12T17:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted file system on eMMC with iMX6SL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499981#M80780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Samuel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;corruptions can be caused by sudden turning off board power,&amp;nbsp; so&lt;/P&gt;&lt;P&gt;recommended to use linux command poweroff. Also in general flash&lt;/P&gt;&lt;P&gt;memory has a limited lifespan with a limited number of write cycles, so&lt;/P&gt;&lt;P&gt;one can try brand new emmc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Apr 2016 01:36:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499981#M80780</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-04-13T01:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted file system on eMMC with iMX6SL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499982#M80781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Igor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you think think that setting rootfs in Read Only mode can limit corruption appearance?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, if we diagnose one, do you know a way to fix it properly without formatting the whole partition? Any specific options in fsck?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Samuel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Apr 2016 08:52:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499982#M80781</guid>
      <dc:creator>samuelrythm</dc:creator>
      <dc:date>2016-04-13T08:52:27Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted file system on eMMC with iMX6SL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499983#M80782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Samuel&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think setting rootfs in Read Only mode will not help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;igor&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Apr 2016 09:29:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499983#M80782</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2016-04-13T09:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: Corrupted file system on eMMC with iMX6SL</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499984#M80783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Samual,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I couldnt help you in case of these corrupted Files, but maybe you can try using User Enhanced Area to extend the normal P/E Cycles of the MLC Flash inside the Micron eMMC from 3K up to approx. 30K. Normally the Boot Area and the two RPMB Areas are already using SLC Mode, only the User Data Area is working completely as MLC (with 3K P/E Cycle). You can split this Area into 4 general purpose Areas, with ea formattet either as MLC or SLC. But remember, that using SLC mode instead of MLC mode, will decrease your overall capacity by 2. So using your EMMC completely in SLC Mode will dercrease capacity frm 4GB to 2GB, but increasig relaibility by a factor of ~10&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;for a more detailed Information, you can use Micron technical note TN-52-07&lt;/P&gt;&lt;P&gt;Your Micron MCP consits by a 128Mx32 Elpida LPDDR2 EDB4432BBBJ-1D and a 4GB Micron MTFC4GACAAAM-1M WT&lt;/P&gt;&lt;P&gt;eMMC Datasheet could be found here: &lt;A href="https://www.micron.com/~/media/documents/products/data-sheet/emmc/broadmarket_embedded/emmc_ps8210_v451_80s_153b_wt.pdf" title="https://www.micron.com/~/media/documents/products/data-sheet/emmc/broadmarket_embedded/emmc_ps8210_v451_80s_153b_wt.pdf"&gt;https://www.micron.com/~/media/documents/products/data-sheet/emmc/broadmarket_embedded/emmc_ps8210_v451_80s_153b_wt.pdf&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jul 2016 12:09:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Corrupted-file-system-on-eMMC-with-iMX6SL/m-p/499984#M80783</guid>
      <dc:creator>larsweyrauch</dc:creator>
      <dc:date>2016-07-21T12:09:30Z</dc:date>
    </item>
  </channel>
</rss>

