Were you in the middle of processing something when you encountered the hardware problem? If you can determine what processes were running, it is likely that those files might be the suspects for corruption, as they may have been open when the system went down. To determine which files should be checked, open the process on a workstation, go to pervasive monitor, and note the open files that process shows in the pervasive monitor. Then try the btrieve maintenance, macola export, or run a report that should access the file to see if you get an error 2.
Another type of file that sits out there when you have a system failure are files that have MM???###.btr, where MM is the module designator, ??? is something related to the process, ### is a numeric designator. I've seen these files in GL and OE commonly, and I believe they are created when a process begins and is updated periodically as records are processed. When a process fails, it allows a rollback using these temporary files. If the process terminates abnormally, these files are left behind and are not removed. I've never seen them prevent the process from restarting later, but it would be a good idea to delete them as part of your cleanup process here.