Operational Defect Database
BugZero found this defect 1357 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
WatchGuard Technologies | kA10H000000bpKwSAI
Disk errors after upgrade of Firebox Cloud in Azure to Fireware v12.6.2
Last update date:
8/31/2020
Affected products:
Firebox Cloud
Affected releases:
All
Fireware
12.x
12.6.x
Fixed releases:
v12.6.2 Update 2
Description:
Issue
After you upgrade Firebox Cloud in Azure to Fireware v12.6.2, log messages such as these appear in the diagnostic logs: 2020-08-31 20:41:14 kernel [ 229.803534] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x02020-08-31 20:41:14 kernel [ 229.803536] ata1.00: failed command: FLUSH CACHE2020-08-31 20:41:14 kernel [ 229.803540] ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 02020-08-31 20:41:14 kernel [ 229.803540] res 51/04:00:1a:00:00/00:00:00:00:00/a0 Emask 0x1 (device error)2020-08-31 20:41:14 kernel [ 229.803542] ata1.00: status: { DRDY ERR }2020-08-31 20:41:14 kernel [ 229.803543] ata1.00: error: { ABRT } Other symptoms of this issue include: The device resets to factory-default settings after the upgrade or after a post-upgrade rebootConfiguration changes fail to save in Policy Manager and Fireware Web UI In the event of a factory reset, Azure might generate an event message with this information: Unavailable : Redeploying due to host failureAt Tuesday, August 25, 2020, 12:18:40 PM PDT, the Azure monitoring system received the following information regarding your Virtual machine:We're sorry, your virtual machine isn't available and it is being redeployed due to an unexpected failure on the host server. Azure has begun the auto-recovery process and is currently starting the virtual machine on a different host. No additional action is required from you at this time.
Workaround/Solution
There is no workaround for this issue. The only resolution is to deploy a new Firebox Cloud instance and restore a backup configuration that you created before the upgrade.If you have a BYOL device and need to redeploy because of this issue, you must contact Customer Care to update your feature key with the new Firebox Cloud instance ID.
