FortiSOAR: Security Orchestration and Response software provides innovative case management, automation, and orchestration. It pulls together all of an organization's tools, helps unify operations, and reduce alert fatigue, context switching, and the mean time to respond to incidents.
This article describes the steps to resolve the issue of LVM partitions not being found post-reboot.
Scope
FortiSOAR instance v7.5.0 fresh installation on Rocky Linux v9.0, 9.1, and 9.2.
Solution
When installing FortiSOAR v7.5.0 on Rocky Linux OS version 9.0/9.1/9.2, it will also upgrade the Rocky Linux OS version to 9.3 with updates in LVM. This may cause the VM to not boot due to changes in the LVM disk layout. To prevent such a scenario before rebooting the system, perform the below steps:
Before rebooting, rename the `#/etc/lvm/devices/system.devices` file (e.g., `#mv /etc/lvm/devices/system.devices /etc/lvm/devices/system.devices.bak`).
Run `#vgimportdevices --all` to regenerate the file in the new format.
Reboot system.
If the system is already rebooted and in a recovery mode, as a workaround, log in using the root access and perform the below steps:
From recovery mode, move the `/etc/lvm/devices/system.devices` file out of the way (e.g., `#mv /etc/lvm/devices/system.devices /etc/lvm/devices/system.devices.bak`).
Reboot the system.
After rebooting, regenerate the file in the new format by running `#vgimportdevices --all`.
Note: Take a VM snapshot before performing these changes.
