<?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: New Problem faced after recreating the corrupt partition in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5240695#M279220</link>
    <description>&lt;P&gt;Re-flashing the AP using the u-boot procedure Jagan shared takes a few minutes and definitely going to be a whole lot quicker than RMA Leo ...&amp;nbsp;&amp;nbsp;I've used it a few times.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Dec 2024 12:56:19 GMT</pubDate>
    <dc:creator>Rich R</dc:creator>
    <dc:date>2024-12-25T12:56:19Z</dc:date>
    <item>
      <title>New Problem faced after recreating the corrupt partition</title>
      <link>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5238896#M279036</link>
      <description>&lt;P&gt;Hello Everyone.&lt;BR /&gt;&lt;BR /&gt;I have a corrupt image / boot loop problem on my Access Point - Model 9120 AXI&lt;/P&gt;&lt;P&gt;Error -&amp;nbsp;verify signature failed for /bootpart/part2/ramfs_data_cisco.cpio.lzma&lt;BR /&gt;&lt;BR /&gt;I recreated the part 2 using below command :&lt;/P&gt;&lt;P&gt;(u-boot)&amp;gt; ubi part fs&lt;BR /&gt;(u-boot)&amp;gt; ubi remove part2&amp;nbsp;&amp;nbsp;&lt;BR /&gt;(u-boot)&amp;gt; ubi create part2&amp;nbsp;&lt;BR /&gt;(u-boot)&amp;gt; boot&lt;BR /&gt;however upon hitting boot I face below problem which I think where the problem. I have omitted normal logs output from below. Could someone explain how to solve it?&lt;BR /&gt;&lt;BR /&gt;u-boot&amp;gt; ubi part fs&lt;BR /&gt;ubi0: attaching mtd3&lt;BR /&gt;ubi0: scanning is finished&lt;BR /&gt;ubi0: attached mtd3 (name "mtd=2", size 1017 MiB)&lt;BR /&gt;ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes&lt;BR /&gt;ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096&lt;BR /&gt;ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192&lt;BR /&gt;ubi0: good PEBs: 4069, bad PEBs: 0, corrupted PEBs: 0&lt;BR /&gt;ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128&lt;BR /&gt;ubi0: max/mean erase counter: 37/20, WL threshold: 4096, image sequence number: 839138221&lt;BR /&gt;ubi0: available PEBs: 33, total reserved PEBs: 4036, PEBs reserved for bad PEB handling: 80&lt;BR /&gt;u-boot&amp;gt; ubi remove part2&lt;BR /&gt;Remove UBI volume part2 (id 1)&lt;BR /&gt;u-boot&amp;gt; ubi create part2&lt;BR /&gt;No size specified -&amp;gt; Using max size (592470016)&lt;BR /&gt;Creating dynamic volume part2 of size 592470016&lt;BR /&gt;u-boot&amp;gt; boot&lt;BR /&gt;Mounting UBI device fs&lt;BR /&gt;ubi0: detaching mtd3&lt;BR /&gt;ubi0: mtd3 is detached&lt;BR /&gt;ubi0: attaching mtd3&lt;BR /&gt;ubi0: scanning is finished&lt;BR /&gt;ubi0: attached mtd3 (name "mtd=2", size 1017 MiB)&lt;BR /&gt;ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes&lt;BR /&gt;ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096&lt;BR /&gt;ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192&lt;BR /&gt;ubi0: good PEBs: 4069, bad PEBs: 0, corrupted PEBs: 0&lt;BR /&gt;ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128&lt;BR /&gt;ubi0: max/mean erase counter: 37/21, WL threshold: 4096, image sequence number: 839138221&lt;BR /&gt;ubi0: available PEBs: 0, total reserved PEBs: 4069, PEBs reserved for bad PEB handling: 80&lt;BR /&gt;Load Addr 0x10000000&lt;BR /&gt;Mount UBIFS PARTITION part2 ...&lt;BR /&gt;Error reading superblock on volume 'ubi0:part2' errno=-30!&lt;BR /&gt;ubifsmount - mount UBIFS volume&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Now coming to the mail logs where It again goes into u-boot without pressing esc button automatically and got stuck with below logs :&lt;/STRONG&gt;&lt;BR /&gt;Hit ESC key to stop autoboot: 3 &amp;#8;&amp;#8;&amp;#8; 2 &amp;#8;&amp;#8;&amp;#8; 1 MG link 1G&lt;BR /&gt;&amp;#8;&amp;#8;&amp;#8; 0&lt;BR /&gt;Mounting UBI device fs&lt;BR /&gt;ubi0: attaching mtd3&lt;BR /&gt;ubi0: scanning is finished&lt;BR /&gt;UBI init error 22&lt;BR /&gt;Error: Unable to ubi mount mtd device fs&lt;BR /&gt;u-boot&amp;gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 14:32:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5238896#M279036</guid>
      <dc:creator>Sam Caprio</dc:creator>
      <dc:date>2024-12-19T14:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: New Problem faced after recreating the corrupt partition</title>
      <link>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5238901#M279037</link>
      <description>&lt;P&gt;Have you tried recovery procedure given in the following document?&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9120axi-access-point/217537-repairing-c9120-c9115-access-points-from.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Jagan Chowdam&lt;/P&gt;
&lt;P&gt;/**Pls rate useful responses**/&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 14:38:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5238901#M279037</guid>
      <dc:creator>jagan.chowdam</dc:creator>
      <dc:date>2024-12-19T14:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: New Problem faced after recreating the corrupt partition</title>
      <link>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5239070#M279047</link>
      <description>&lt;P&gt;It is easier and a lot faster to RMA the AP.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 22:30:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5239070#M279047</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2024-12-19T22:30:01Z</dc:date>
    </item>
    <item>
      <title>Re: New Problem faced after recreating the corrupt partition</title>
      <link>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5240695#M279220</link>
      <description>&lt;P&gt;Re-flashing the AP using the u-boot procedure Jagan shared takes a few minutes and definitely going to be a whole lot quicker than RMA Leo ...&amp;nbsp;&amp;nbsp;I've used it a few times.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Dec 2024 12:56:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/new-problem-faced-after-recreating-the-corrupt-partition/m-p/5240695#M279220</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2024-12-25T12:56:19Z</dc:date>
    </item>
  </channel>
</rss>

