So you’re saying this specific FPBX instance was compromised by a bad actor? If it were me, I’d spin up a new instance and restore the most recent “good” backup before the existing instance has been confirmed to have IOC. Is this not an option in your situation?
Hi - thank you for your input! The last known good backup is from 2021, though I did copy the complete virtual machine in March. I was able to recover that older version, and bring it up to date - I have yet to try a backup on that older version.
My current objective remains to try to figure out how to get my latest version “un compromised” - that’s because I have made quite a few changes to the system since March 2026.
It’s pretty wild that every time I update “Framework”, the file system gets corrupted and crashes. I’ve tripled the ram, and there’s plenty of space (I think!).
I’m considering downloading a CENTOS DVD ISO file to be able to for a repair of the file system once the update will corrupt the operating system, but I would have preferred to find what is causing the issue before it happens, rather than letting it happen and then trying to fix it.
Fortunately, I do have a checkpoint on the VM that allows me to roll back if needed (which I’ve been abusing today!)
My other concern is that the backup is not completing successfully. I would’ve loved to get mesylf onboard with version 17 and restore the backup…
Seems like my system has become unhealthy overtime, and clearly: my MSDOS skills are not sufficient to efficiently navigate Linux. I’ll take all the help this community can offer!
Booting using an ISO and running the following commmand:
xfs_repair /dev/mapper/SangomaVG-root
has found corruption and repaired it. Once the FS repaired, I was able to refreshsignatures without a full crash, and I was able to update Framework to the latest version, as well as all the other modules.
This issue is resolved… now on to the next issue: the backup not completing!