<?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: Unable to get into maintenance mode in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285630#M76450</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I would place it back under warranty, if its something you need asap, buy a new one :(.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Aug 2019 20:15:56 GMT</pubDate>
    <dc:creator>OtakarKlier</dc:creator>
    <dc:date>2019-08-28T20:15:56Z</dc:date>
    <item>
      <title>Unable to get into maintenance mode</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285583#M76444</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;I was in the process of upgrading our firmware of our PA500 to 8.1 and when the device rebooted, it did not want to come back online.&amp;nbsp; Checked the startup and noticed I was getting this error message.&amp;nbsp;&amp;nbsp;I did read online that it might be an issue with the hard drive?&amp;nbsp; Is there a way I can resolve this?&amp;nbsp; I cannot even get into maintenance mode to run a hard drive repair.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Entry: maint8935587 bytes read in 217 ms (39.3 MiB/s)&lt;BR /&gt;Allocating memory for ELF segment: addr: 0xffffffff80100000 (adjusted to: 0x100000), size 0x74b2a0&lt;BR /&gt;Bootloader: Done loading app on coremask: 0x3&lt;BR /&gt;Starting cores:&lt;BR /&gt;0x3&lt;BR /&gt;Linux version 3.10.20-mp-7.1.0.0.22 (build@eng-bf0-1.paloaltonetworks.local) (gcc version 4.7.0 (Cav ium Inc. Version: SDK_BUILD build 41) ) #2 SMP Fri Feb 5 14:19:56 PST 2016&lt;BR /&gt;CVMSEG size: 2 cache lines (256 bytes)&lt;BR /&gt;Cavium Inc. SDK-3.1&lt;BR /&gt;bootconsole [early0] enabled&lt;BR /&gt;CPU revision is: 000d0708 (Cavium Octeon+)&lt;BR /&gt;Checking for the multiply/shift bug... no.&lt;BR /&gt;Checking for the daddiu bug... no.&lt;BR /&gt;Determined physical RAM map:&lt;BR /&gt;memory: 000000000b400000 @ 0000000000900000 (usable)&lt;BR /&gt;memory: 0000000003c00000 @ 000000000c200000 (usable)&lt;BR /&gt;memory: 0000000060000000 @ 0000000020000000 (usable)&lt;BR /&gt;memory: 000000000f000000 @ 0000000410000000 (usable)&lt;BR /&gt;memory: 0000000000615000 @ 0000000000100000 (usable)&lt;BR /&gt;memory: 000000000005b000 @ 0000000000715000 (usable after init)&lt;BR /&gt;ata1.00: exception Emask 0x0 SAct 0x7f000001 SErr 0x0 action 0x6&lt;BR /&gt;ata1.00: irq_stat 0x00020002, device error via SDB FIS&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:00:6d:20:b9/00:00:00:00:00/40 tag 0 ncq 4096 in&lt;BR /&gt;res 6c/1e:00:00:00:00/00:00:00:00:6c/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:c0:35:20:b9/00:00:00:00:00/40 tag 24 ncq 4096 in&lt;BR /&gt;res 41/40:00:35:20:b9/00:00:00:00:00/40 Emask 0x409 (media error) &amp;lt;F&amp;gt;&lt;BR /&gt;ata1.00: status: { DRDY ERR }&lt;BR /&gt;ata1.00: error: { UNC }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:c8:3d:20:b9/00:00:00:00:00/40 tag 25 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:90:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:d0:45:20:b9/00:00:00:00:00/40 tag 26 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:a0:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:d8:4d:20:b9/00:00:00:00:00/40 tag 27 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:b0:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:e0:55:20:b9/00:00:00:00:00/40 tag 28 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:c0:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:e8:5d:20:b9/00:00:00:00:00/40 tag 29 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:d0:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;ata1.00: failed command: READ FPDMA QUEUED&lt;BR /&gt;ata1.00: cmd 60/08:f0:65:20:b9/00:00:00:00:00/40 tag 30 ncq 4096 in&lt;BR /&gt;res 6d/1e:00:00:00:00/00:00:00:e0:6d/00 Emask 0x2 (HSM violation)&lt;BR /&gt;ata1.00: status: { DRDY DF DRQ ERR }&lt;BR /&gt;ata1.00: error: { IDNF ABRT }&lt;BR /&gt;end_request: I/O error, dev sda, sector 12132405&lt;BR /&gt;JBD: Failed to read block at offset 11692&lt;BR /&gt;EXT3-fs (sda3): error loading journal&lt;BR /&gt;EXT2-fs (sda3): error: couldn't mount because of unsupported optional features (4)&lt;BR /&gt;Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 18:02:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285583#M76444</guid>
      <dc:creator>jsuttor</dc:creator>
      <dc:date>2019-08-28T18:02:49Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to get into maintenance mode</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285618#M76445</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;That is a support call and possible RMA.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 19:29:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285618#M76445</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-08-28T19:29:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to get into maintenance mode</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285629#M76449</link>
      <description>&lt;P&gt;Unfortunately the warranty has expired on this unit.&amp;nbsp; &amp;nbsp;Is there anything else I might be able to do?&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 20:12:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285629#M76449</guid>
      <dc:creator>jsuttor</dc:creator>
      <dc:date>2019-08-28T20:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to get into maintenance mode</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285630#M76450</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I would place it back under warranty, if its something you need asap, buy a new one :(.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Aug 2019 20:15:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unable-to-get-into-maintenance-mode/m-p/285630#M76450</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-08-28T20:15:56Z</dc:date>
    </item>
  </channel>
</rss>

