- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
11-17-2021 08:17 AM
Hello ,
We were running Panorama on Esxi . The version was 9.0.9
First we upgraded to 9.0.14 and it went smooth
Then we went to 9.1.0 and it never came up ; we saw it went to maintenace mode with below error
A critical error has been detected preventing proper boot
up of the device. Please contact Palo Alto Networks to resolve this
issue.
Entry Reason: Failed to migrate system disk
How to resolve this ?
03-11-2023 03:12 PM - edited 03-11-2023 04:04 PM
So I know this post was 2 years ago, but we saw the same issue today upgrading from 9.0 to 9.1 so I thought I'd post our solution in case anyone else has the same error. From maintenance mode, we reverted the code version to get Panorama working. Looking at the VM settings I saw 4 disks on the VM. I ran "show system disk details" and saw that there was a 32GB and a 500GB disk that were admin disabled on the Panorama server. The disks are legacy from when Panorama required less resources. The fix was to power down the VM and delete the two un-used disks from the vServer and power it back on. You should just have an 81Gb disk (running Panorama) and a 2TB disk (for Logging). Once powered back on, the system will come up on the new code version.
11-18-2021 03:01 AM
Hi , Can anyone assist ?
03-11-2023 03:12 PM - edited 03-11-2023 04:04 PM
So I know this post was 2 years ago, but we saw the same issue today upgrading from 9.0 to 9.1 so I thought I'd post our solution in case anyone else has the same error. From maintenance mode, we reverted the code version to get Panorama working. Looking at the VM settings I saw 4 disks on the VM. I ran "show system disk details" and saw that there was a 32GB and a 500GB disk that were admin disabled on the Panorama server. The disks are legacy from when Panorama required less resources. The fix was to power down the VM and delete the two un-used disks from the vServer and power it back on. You should just have an 81Gb disk (running Panorama) and a 2TB disk (for Logging). Once powered back on, the system will come up on the new code version.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!