<?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: The PA-220 is unable to boot into the system. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228223#M124192</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/967386347"&gt;@p.chunwei&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try with factory reset to restore the device.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CldXCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CldXCAS&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 06 May 2025 07:38:22 GMT</pubDate>
    <dc:creator>mshekh</dc:creator>
    <dc:date>2025-05-06T07:38:22Z</dc:date>
    <item>
      <title>The PA-220 is unable to boot into the system.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228219#M124188</link>
      <description>&lt;P&gt;As stated in the subject, I encountered an error during boot-up. The details are as follows:&lt;BR /&gt;&lt;BR /&gt;SPI ID: ef:40:18:00:00&lt;BR /&gt;header found at offset 0x1d80&lt;BR /&gt;Image 1.2: address: 0xffffffff81000000, header length: 192, data length: 8160&lt;BR /&gt;Validating data...&lt;BR /&gt;Starting next bootloader at 0xffffffff81000000&lt;BR /&gt;SPI stage 1.5 bootloader&lt;BR /&gt;SPI ID: ef:40:18:00:00&lt;BR /&gt;Header 1 found at offset 0x10000&lt;BR /&gt;Header 2 found at offset 0x100000&lt;BR /&gt;Found bootloaders, booting bootloader 1 of 2 at offset 0x10000.&lt;BR /&gt;Starting next bootloader at 0xffffffff81000000&lt;BR /&gt;Board type: KINGFISHER&lt;BR /&gt;Welcome to the PanOS Bootloader.&lt;/P&gt;
&lt;P&gt;U-Boot 11.0.0.0-48 (Build time: Dec 26 2021 - 23:04:40)&lt;/P&gt;
&lt;P&gt;Octeon unique ID: 09c000118321f31e0493&lt;BR /&gt;N0.LMC0 Configuration Completed: 8192 MB&lt;BR /&gt;Warning: Board descriptor tuple not found in eeprom, using defaults&lt;BR /&gt;KINGFISHER board revision major:1, minor:0, serial #: unknown&lt;BR /&gt;OCTEON CN7130-AAP pass 1.2, Core clock: 1000 MHz, IO clock: 500 MHz, DDR clock: 800 MHz (1600 Mhz DDR)&lt;BR /&gt;Base DRAM address used by u-boot: 0x20fc00000, size: 0x400000&lt;BR /&gt;DRAM: 8 GiB&lt;BR /&gt;Clearing DRAM...... done&lt;BR /&gt;Using default environment&lt;/P&gt;
&lt;P&gt;SF: Detected W25Q128BV with page size 256 Bytes, erase size 4 KiB, total 16 MiB&lt;BR /&gt;Found valid SPI bootloader at offset: 0x100000, size: 1308968 bytes&lt;BR /&gt;Loading bootloader from SPI offset 0x100000, size: 1308968 bytes&lt;/P&gt;
&lt;P&gt;Welcome to the PanOS Failsafe Bootloader.&lt;/P&gt;
&lt;P&gt;U-Boot 11.0.0.0-48 (Build time: Dec 26 2021 - 23:11:00)&lt;/P&gt;
&lt;P&gt;Octeon unique ID: 09c000118321f31e0493&lt;BR /&gt;N0.LMC0 Configuration Completed: 8192 MB&lt;BR /&gt;KINGFISHER board revision major:1, minor:4, serial #: 012801174150&lt;BR /&gt;OCTEON CN7130-AAP pass 1.2, Core clock: 1000 MHz, IO clock: 500 MHz, DDR clock: 800 MHz (1600 Mhz DDR)&lt;BR /&gt;Base DRAM address used by u-boot: 0x20f000000, size: 0x1000000&lt;BR /&gt;DRAM: 8 GiB&lt;BR /&gt;Clearing DRAM...... done&lt;BR /&gt;Octeon MMC/SD0: 0&lt;BR /&gt;Using default environment&lt;/P&gt;
&lt;P&gt;MMC: Octeon MMC/SD0: 0, Octeon MMC/SD0: 0&lt;BR /&gt;Net: Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;Phy not found&lt;BR /&gt;PHY reset timed out for Generic PHY (devad: -1, reg: 0xffff)&lt;BR /&gt;octeth0, octeth1, octeth2, octeth3, octeth4, octeth5, octeth6, octeth7, octrgmii0 [PRIME]&lt;BR /&gt;Type the command 'usb start' to scan for USB storage devices.&lt;/P&gt;
&lt;P&gt;Hit any key to stop autoboot: 0&lt;BR /&gt;** File not found /boot/vmlinux.oct3-mp **&lt;BR /&gt;## No elf image at address 0x21000000&lt;BR /&gt;Octeon Kingfisher Failsafe bootloader (mp)# (ram)#&lt;BR /&gt;&lt;BR /&gt;May I ask how this issue can be resolved?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 06:22:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228219#M124188</guid>
      <dc:creator>p.chunwei</dc:creator>
      <dc:date>2025-05-06T06:22:36Z</dc:date>
    </item>
    <item>
      <title>Re: The PA-220 is unable to boot into the system.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228223#M124192</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/967386347"&gt;@p.chunwei&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Try with factory reset to restore the device.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CldXCAS" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CldXCAS&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 07:38:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228223#M124192</guid>
      <dc:creator>mshekh</dc:creator>
      <dc:date>2025-05-06T07:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: The PA-220 is unable to boot into the system.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228225#M124193</link>
      <description>&lt;P&gt;Hi,&lt;BR data-start="12" data-end="15" /&gt;Sorry to bother you, but I'm currently unable to enter Maintenance Mode.&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 07:43:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228225#M124193</guid>
      <dc:creator>p.chunwei</dc:creator>
      <dc:date>2025-05-06T07:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: The PA-220 is unable to boot into the system.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228253#M124198</link>
      <description>&lt;P&gt;"No elf image" means your hard disk sectors are messed up/broken (cant find a valid boot image).&lt;/P&gt;
&lt;P&gt;Maintenance mode is your last resort, you can try to run an FSCK to fix any damaged sectors&lt;/P&gt;
&lt;P&gt;if you can't get into maintenance mode, your only recourse is to put in an RMA with palo support to have the device replacers (you need to have an active support subscription for this)&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 13:35:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/the-pa-220-is-unable-to-boot-into-the-system/m-p/1228253#M124198</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2025-05-06T13:35:32Z</dc:date>
    </item>
  </channel>
</rss>

