<?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: UBIFS: recovery needed ,, in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-recovery-needed/m-p/464522#M73094</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which board you are using and which version of Linux you are running there?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I see &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.freescale.com/external-link.jspa?url=http%3A%2F%2Fgit.infradead.org%2Fusers%2Fdedekind%2Fubifs-v2.6.27.git" rel="nofollow" target="_blank"&gt;http://git.infradead.org/users/dedekind/ubifs-v2.6.27.git&lt;/A&gt;&lt;SPAN&gt; fixes the issue for 2.6.27 kernel you mentioned:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.freescale.com/external-link.jspa?url=http%3A%2F%2Flists.infradead.org%2Fpipermail%2Flinux-mtd%2F2009-May%2F025609.html" rel="nofollow" target="_blank"&gt;http://lists.infradead.org/pipermail/linux-mtd/2009-May/025609.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;/P&gt;&lt;P&gt;Victor&lt;/P&gt;&lt;P&gt;&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>Fri, 22 Apr 2016 06:44:53 GMT</pubDate>
    <dc:creator>b36401</dc:creator>
    <dc:date>2016-04-22T06:44:53Z</dc:date>
    <item>
      <title>UBIFS: recovery needed ,,</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-recovery-needed/m-p/464521#M73093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;normaly the ubifs recovery prozess will be startet automaticly on mount, if nesessary.&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;&lt;BR /&gt;mount -o sync -t ubifs ubi0:data /mnt/data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UBIFS: recovery needed&lt;BR /&gt;UBIFS: recovery completed&lt;BR /&gt;UBIFS: mounted UBI device 0, volume 2, name "data"&lt;BR /&gt;UBIFS: file system size:&amp;nbsp;&amp;nbsp; 33013760 bytes (32240 KiB, 31 MiB, 260 LEBs)&lt;BR /&gt;UBIFS: journal size:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1650688 bytes (1612 KiB, 1 MiB, 13 LEBs)&lt;BR /&gt;UBIFS: media format:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; w4/r0 (latest is w4/r0)&lt;BR /&gt;UBIFS: default compressor: lzo&lt;BR /&gt;UBIFS: reserved for root:&amp;nbsp; 1559321 bytes (1522 KiB)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here everything works fine. But sometimes the recovery prozess failes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mount -o sync -t ubifs ubi0:firmware /mnt/firmware&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UBIFS: recovery needed&lt;BR /&gt;UBI error: ubi_io_read: error -74 while reading 34816 bytes from PEB 467:96256,&lt;BR /&gt;read 34816 bytes&lt;BR /&gt;UBIFS error (pid 772): ubifs_recover_leb: corrupt empty space LEB 253:114688, co&lt;BR /&gt;rruption starts at 811&lt;BR /&gt;UBIFS error (pid 772): ubifs_scanned_corruption: corruption at LEB 253:811&lt;BR /&gt;UBIFS error (pid 772): ubifs_recover_leb: LEB 253 scanning failed&lt;BR /&gt;mount: mounting ubi0:firmware on /mnt/firmware failed: Structure needs cleaning&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;I suppose that is similar to following mailing list entry:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A class="jive-link-external-small" data-content-finding="Community" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Flists.infradead.org%2Fpipermail%2Flinux-mtd%2F2009-March%2F024953.html" rel="nofollow" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #017bba;" target="_blank"&gt;http://lists.infradead.org/pipermail/linux-mtd/2009-March/024953.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to the ubifs documentation, chapter "Power-cuts tolerance", the problem were seen on NOR flash with kernel version 2.6.27 and should be solved in later versions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;A class="jive-link-external-small" data-content-finding="Community" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fwww.linux-mtd.infradead.org%2Fdoc%2Fubifs.html" rel="nofollow" style="font-weight: inherit; font-style: inherit; font-family: inherit; color: #017bba;" target="_blank"&gt;http://www.linux-mtd.infradead.org/doc/ubifs.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Any idea, how can we solve this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Kind regards,&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;Birger&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;p.s. We got these error also on the rootfs ubifs partition, which will be mounted by the kernel via kernel command line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;CONFIG_PKG_BOOT_STREAM_CMDLINE1="noinitrd console=ttyAM0,115200 ubi.mtd=1 root=ubi0:rootfs0 rootfstype=ubifs rw gpmi"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H2 style="font-family: arial, helvetica, 'helvetica neue', verdana, sans-serif; color: #51626f;"&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;mxs-rtc mxs-rtc.0: setting system clock to 1970-01-17 07:02:25 UTC (1407745)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;UBIFS: recovery needed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;UBI error: ubi_io_read: error -74 while reading 73728 bytes from PEB 108:57344, read 73728 bytes&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;UBIFS error (pid 1): ubifs_recover_leb: corrupt empty space LEB 326:53248, corruption starts at 3653&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;UBIFS error (pid 1): ubifs_scanned_corruption: corruption at LEB 326:3653&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;UBIFS error (pid 1): ubifs_recover_leb: LEB 326 scanning failed&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;VFS: Cannot open root device "ubi0:rootfs0" or unknown-block(0,0)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;Please append a correct "root=" boot option; here are the available partitions:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;1f00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10240 mtdblock0 (driver?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;1f01&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 120832 mtdblock1 (driver?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;fe00&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 41044 ubiblka (driver?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;fe08&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 41044 ubiblkb (driver?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;fe10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 32860 ubiblkc (driver?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;Backtrace:&lt;/SPAN&gt; &lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt;[&amp;lt;c0031260&amp;gt;] (dump_backtrace+0x0/0x114) from [&amp;lt;c02eb078&amp;gt;] (dump_stack+0x18/0x1c)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN style="font-weight: inherit; font-style: inherit; font-family: 'courier new', courier;"&gt; r7:c0028a24 r6:00008000 r5:c7c15000 r4:c0402818&lt;/SPAN&gt;&lt;/H2&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Apr 2016 07:05:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-recovery-needed/m-p/464521#M73093</guid>
      <dc:creator>sywksmstkadlfgk</dc:creator>
      <dc:date>2016-04-21T07:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: UBIFS: recovery needed ,,</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UBIFS-recovery-needed/m-p/464522#M73094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Which board you are using and which version of Linux you are running there?&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I see &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.freescale.com/external-link.jspa?url=http%3A%2F%2Fgit.infradead.org%2Fusers%2Fdedekind%2Fubifs-v2.6.27.git" rel="nofollow" target="_blank"&gt;http://git.infradead.org/users/dedekind/ubifs-v2.6.27.git&lt;/A&gt;&lt;SPAN&gt; fixes the issue for 2.6.27 kernel you mentioned:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.freescale.com/external-link.jspa?url=http%3A%2F%2Flists.infradead.org%2Fpipermail%2Flinux-mtd%2F2009-May%2F025609.html" rel="nofollow" target="_blank"&gt;http://lists.infradead.org/pipermail/linux-mtd/2009-May/025609.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;/P&gt;&lt;P&gt;Victor&lt;/P&gt;&lt;P&gt;&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>Fri, 22 Apr 2016 06:44:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UBIFS-recovery-needed/m-p/464522#M73094</guid>
      <dc:creator>b36401</dc:creator>
      <dc:date>2016-04-22T06:44:53Z</dc:date>
    </item>
  </channel>
</rss>

