Encryption Management server fails to boot. At the console it displays errors relating to a corrupt file system.
Error messages like these appear in the console:
/ contains a file system with errors, check forced.
Corrupt File System Error - UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
Symantec Encryption Management Server 3.3.2 MP13 and above.
File system corruption is almost always the result of hardware failure. Reasons include:
If Encryption Management Server is running as a VMWare ESXi virtual machine, the file system may be started in read only mode. Please see article TECH149087 for further details.
The file system can often be repaired using the fsck file system check utility. However, there are no guarantees that this will be successful.
If you are running into a "grub>" prompt and will not even get beyond this, please reach out to Symantec Encryption Support for further guidance.