Can't Upgrade (Virtual) Firewall Home from 19.0.0GA

Hi,

there is another thread on this subject that I cannot locate at the moment.

Ian

What hypervisor are you using? (ESXi/KVM ect.)? Can the /var partition be resized? If the /var partition contains the logs, can all the logs be deleted or the contents of /var deleted before upgrading?

ESXi 7.x

There is an older thread on the same subject, I have searched for and cannot locate. A number of people made suggestions, the outcome was the changes you are suggesting do not work and that is why there is an NC active.

Ian

Hi rfcat,

Is this the one you’re referring to? 

 Not able to upload firmware and upgrade firmware on Sophos XG SFVH 

HI Gary,

Kindly check if this would be able to assist you. 

Hi Erick,

yes, thank you.

Ian

Thanks for the effort  rfcat_vk and Erick Jan.
Ultimately though, this leads to the Support instance that says, to paraphrase, "we have a workaround to grow /var from within the OS after it has been "grown" at the logical volume level.... contact support for that workaround".
The only other course of action is to reload with 19.0MR1 or above and restore from backup. I'm still trying to avoid that.

Does anyone have that "work around" mentioned in (+) v19 VMware disk usage, reporting full - Discussions - Sophos Firewall - Sophos Community

• Offline bobbylam 8 months ago in reply to Gerd Rehders1

  Hi Gerd Rehders1, TomasLavicky, Jiri Hadamek,

  We have developed a workaround that will resize the /var partition on a running VM (while keeping your data), but requires a reboot of the VM. 

  Can you please PM me your email address, so I can send you the workaround & instructions how to run it? 

Hello,

Support can only apply the workaround since it requires uploading a script; in your case, since this is a home installation, please Reinstall with v19MR1 Build 350 or higher to fix this issue.

Regards,

OK emmosophos 
Thanks for the definitive answer. 

Summary:
For Firewall Home instances, mitigating the deficient size provision of /var introduced by the 19.0GA installer requires that you back up the configuration of the 19.0GA implementation, reinstall using 19.0MR1 or later then reinstall the configuration from backup.