<?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>i.MX ProcessorsのトピックRe: U-Boot and Kernel not recognizing ubi file system</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255345#M171903</link>
    <description>&lt;P&gt;I found the following useful information on ubifs:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfubifs" target="_self"&gt;http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfubifs&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In order to create the ubifs successfully you need parameters set for the NAND.&amp;nbsp; I was able to boot from SD card and inspect my NAND with:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;mtdinfo /dev/mtd0 -u&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was then able to set the following ubifs parameters in my conf/machine/${MACHINE} file:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;MKUBIFS_ARGS = "-m 4096 -e 253952 -c 1932"
UBINIZE_ARGS = "-p 256KiB -m 4096"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Apr 2021 00:55:01 GMT</pubDate>
    <dc:creator>JohnKlug</dc:creator>
    <dc:date>2021-04-01T00:55:01Z</dc:date>
    <item>
      <title>U-Boot and Kernel not recognizing ubi file system</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255125#M171889</link>
      <description>&lt;P&gt;I am using Yocto Zeus with 5.4 kernel and u-boot 2020.04.&lt;BR /&gt;&lt;BR /&gt;I build the ubi image, and the only message I see from ubinize is:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ubinize: volume size was not specified in section "ubifs", assume minimum to fit image.&lt;/LI-CODE&gt;&lt;P&gt;&lt;BR /&gt;In U-Boot:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;=&amp;gt; ubi part nandrootfs
ubi0: attaching mtd7
ubi0: scanning is finished
ubi0: volume table was restored
ubi0: volume 0 ("imx6ull14x14evk-rootfs") re-sized from 290 to 1916 LEBs
ubi0: attached mtd7 (name "nandrootfs", size 490 MiB)
ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
ubi0: good PEBs: 1956, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 159654406
ubi0: available PEBs: 0, total reserved PEBs: 1956, PEBs reserved for bad PEB handling: 36&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know the device has 4 blocks marked bad.&lt;BR /&gt;&lt;BR /&gt;Layout:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;=&amp;gt; ubi info layout
Volume information dump:
        vol_id          0
        reserved_pebs   1916
        alignment       1
        data_pad        0
        vol_type        3
        name_len        22
        usable_leb_size 253952
        used_ebs        1916
        used_bytes      486572032
        last_eb_bytes   253952
        corrupted       0
        upd_marker      0
        skip_check      0
        name            imx6ull14x14evk-rootfs
Volume information dump:
        vol_id          2147479551
        reserved_pebs   2
        alignment       1
        data_pad        0
        vol_type        3
        name_len        13
        usable_leb_size 253952
        used_ebs        2
        used_bytes      507904
        last_eb_bytes   2
        corrupted       0
        upd_marker      0
        skip_check      0
        name            layout volume&lt;/LI-CODE&gt;&lt;P&gt;Mount result:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;=&amp;gt; ubifsmount ubi0:imx6ull14x14evk-rootfs
UBIFS error (ubi0:0 pid 0): ubifs_read_node: bad node type (255 but expected 6)
UBIFS error (ubi0:0 pid 0): ubifs_read_node: bad node at LEB 0:0, LEB mapping status 0
Not a node, first 24 bytes:Error reading superblock on volume 'ubi0:imx6ull14x14evk-rootfs' errno=-22!
ubifsmount - mount UBIFS volume

Usage:
ubifsmount &amp;lt;volume-name&amp;gt;
    - mount 'volume-name' volume&lt;/LI-CODE&gt;&lt;P&gt;Kernel:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[    2.495649] ubi0: default fastmap pool size: 95
[    2.500225] ubi0: default fastmap WL pool size: 47
[    2.505216] ubi0: attaching mtd6
[    3.056892] ubi0: scanning is finished
[    3.072096] ubi0 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 34, need 36
[    3.085277] ubi0: attached mtd6 (name "nandrootfs", size 490 MiB)
[    3.091421] ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
[    3.098413] ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
[    3.105337] ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
[    3.112327] ubi0: good PEBs: 1956, bad PEBs: 4, corrupted PEBs: 0
[    3.118481] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[    3.125852] ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 159654406
[    3.134966] ubi0: available PEBs: 0, total reserved PEBs: 1956, PEBs reserved for bad PEB handling: 34
[    3.144319] ubi0: background thread "ubi_bgt0d" started, PID 114
 ...
[    3.343148]  (driver?)
[    3.349749] 1f06          501760 mtdblock6 
[    3.349755]  (driver?)
[    3.356337] No filesystem could mount root, tried: 
[    3.356341]  ubifs
[    3.361228] 
[    3.364747] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    3.373038] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---&lt;/LI-CODE&gt;</description>
      <pubDate>Wed, 31 Mar 2021 18:27:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255125#M171889</guid>
      <dc:creator>JohnKlug</dc:creator>
      <dc:date>2021-03-31T18:27:09Z</dc:date>
    </item>
    <item>
      <title>Re: U-Boot and Kernel not recognizing ubi file system</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255337#M171899</link>
      <description>&lt;P&gt;Hi John&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;for that issue one can recheck nand programming procedure, for example&lt;/P&gt;
&lt;P&gt;&lt;A href="https://variwiki.com/index.php?title=Yocto_NAND_Flash_Burning" target="_blank"&gt;https://variwiki.com/index.php?title=Yocto_NAND_Flash_Burning&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/How-To-use-NAND-boot-on-i-MX6UL-EVK-board/ta-p/1116178" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/How-To-use-NAND-boot-on-i-MX6UL-EVK-board/ta-p/1116178&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 00:27:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255337#M171899</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2021-04-01T00:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: U-Boot and Kernel not recognizing ubi file system</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255345#M171903</link>
      <description>&lt;P&gt;I found the following useful information on ubifs:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfubifs" target="_self"&gt;http://www.linux-mtd.infradead.org/faq/ubifs.html#L_mkfubifs&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In order to create the ubifs successfully you need parameters set for the NAND.&amp;nbsp; I was able to boot from SD card and inspect my NAND with:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;mtdinfo /dev/mtd0 -u&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was then able to set the following ubifs parameters in my conf/machine/${MACHINE} file:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;MKUBIFS_ARGS = "-m 4096 -e 253952 -c 1932"
UBINIZE_ARGS = "-p 256KiB -m 4096"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Apr 2021 00:55:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/U-Boot-and-Kernel-not-recognizing-ubi-file-system/m-p/1255345#M171903</guid>
      <dc:creator>JohnKlug</dc:creator>
      <dc:date>2021-04-01T00:55:01Z</dc:date>
    </item>
  </channel>
</rss>

