<?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: Panorama VM OS Disk size modified in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-vm-os-disk-size-modified/m-p/299711#M78400</link>
    <description>&lt;P&gt;You can shutdown/reboot the Panorama.&amp;nbsp; Should not be an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am just curious if possible, to download a brand new 9.0.0 version of Panorama and create a new Panorama install.&lt;/P&gt;&lt;P&gt;Not sure how far you have gotten with your logs, significance of logs (which I understand... probably important... )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just at the end of day (so to speak) what is the most efficient way to get your Panorama back up and operational.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 20 Nov 2019 16:15:42 GMT</pubDate>
    <dc:creator>S.Cantwell</dc:creator>
    <dc:date>2019-11-20T16:15:42Z</dc:date>
    <item>
      <title>Panorama VM OS Disk size modified</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-vm-os-disk-size-modified/m-p/299590#M78378</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;Today whilst we were investigating the process of upgrading the disk size for our Panorama Legacy Mode VM we have accidentally re-configured the disk size from 81gb (as per the template import original size) to 150gb. This was of course different to the process as outlined by Palo Alto documentation. Within VMWARE VCSA we are unable to change the disk size back down to 81gb as we are advised that a disk size cannot be reduced below it's current size.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I would like to know that if we restart the Panorama OS or it is shut down will it cause any issues with Panorama OS working properly? My thoughts are there should be no issues as essentially Panorama OS will not know about the increase of disk space as it can't extend a partition table. I am just not sure how much it checks the disk during the boot stages and if it detects a change to the disk if that will cause a boot issue...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Can you please advise if this is a problem, as we are thinking of upgrading Panorama which is currently in Legacy mode to Panorama mode which of course requires a shutdown to begin the change.&lt;/DIV&gt;</description>
      <pubDate>Tue, 19 Nov 2019 22:47:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-vm-os-disk-size-modified/m-p/299590#M78378</guid>
      <dc:creator>Jatin.Singh</dc:creator>
      <dc:date>2019-11-19T22:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama VM OS Disk size modified</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-vm-os-disk-size-modified/m-p/299711#M78400</link>
      <description>&lt;P&gt;You can shutdown/reboot the Panorama.&amp;nbsp; Should not be an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am just curious if possible, to download a brand new 9.0.0 version of Panorama and create a new Panorama install.&lt;/P&gt;&lt;P&gt;Not sure how far you have gotten with your logs, significance of logs (which I understand... probably important... )&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just at the end of day (so to speak) what is the most efficient way to get your Panorama back up and operational.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Nov 2019 16:15:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-vm-os-disk-size-modified/m-p/299711#M78400</guid>
      <dc:creator>S.Cantwell</dc:creator>
      <dc:date>2019-11-20T16:15:42Z</dc:date>
    </item>
  </channel>
</rss>

