Note: A corrupt file on Cloudstack--gluster primary storage causes SSVM to fail to start

Cloudstack System VMS (SSVM failed to rebuild). -

Key logs for 1.cloudstack-management

This line cannot read header ' mnt ... ': Invalid argument

Critical logs for 2.cloudstack storage (Gluster)

There are no helpful error logs in sight here

3.cloudstack agent (LIBVIRTD) log (rebuilding system VMs will be randomly rebuilt on all compute nodes)

Here also appeared the cannot read header ' mnt ... ': Invalid argument

Workaround: Delete a36023 on primary storage .... 0623 This file

Finally on the host to mount the primary storage, find the above file, deleted, the system VM rebuilt successfully.

For specific reasons, it is possible that this file, which is stored on the Gluster primary storage, is corrupted, causing the file to be found each time the system VM rebuilds itself, but the file has been broken, causing the rebuild to fail.

Note: A corrupt file on Cloudstack--gluster primary storage causes SSVM to fail to start