When booting a SEE-encrypted machine, the boot process halts during the pre-OS with the error "Volume files contains errors".
"Volume files contains errors"
This problem is caused by corruption of the SEE Volume files, which contain the SEE Pre-OS and File System. Generally, this corruption will only affect a small number of machines and is usually caused by a hard reset of the affected machine during or after encryption. In the unlikely event that all machines of a certain model are affected by this issue, then you should open a ticket with Symantec Technical Support.
During the encryption process (and, to a lesser extent, after the encryption process has completed), the system is sensitive to problems caused by forcibly switching off the machine. This is because it can corrupt the volume files which are the protected OS files in which the Pre-OS is located. There is a SEE system driver that is designed to protect these files, but a hard reset during a delayed shutdown can still provoke issues.
A SEE-encrypted system might be forcibly shut down because of a real or perceived delay in the shut down process. Also, an issue such as that reported in TECH140569 could lead a user to conclude that they have no other option available.
This issue can be remediated by booting the affected machine with the bootable Recover CD tool. The "recover /a" option, which runs automatically should fix the problem. Do not run any of the other options.
Customers should be aware that a hard shutdown should never be performed on an encrypted computer even if there is a delay shutting down.
If it is the case that the user is prevented from shutting down their system because the following popup message appears: "The system cannot end your windows session right now, SEE is applying new settings this may take several mins please try again later", consult KB TECH140569.
Other tips that may prevent help to prevent this issue from occuring include the following:
Running "chkdsk /f /R" (preferably) before installing SEE.
Performing a full disk defragmentation (preferably) before installing SEE.
This issue has been known to occur on systems with RAID or IRRT arrays which are not supported.
Imported Document ID: TECH145119
Subscribing will provide email updates when this Article is updated. Login is required.