Browse KB by category:
Go to KB #:
BRU PE Reports My System Is Corrupt, Why?
Upon starting BRU PE, prompt is displayed telling the user that "System Drive Corruption Detected", as shown below.
Users that have a non-corrupt Python binary (in some installations it is corrupt), users can download the "damage_check" script. This script will step through each of the major system binary folders of /bin, /sbin, /usr/bin, and /usr/sbin. It also goes a step farther and checks /usr/share/zoneinfo (yes, the Timezone folder). This is because we have seen corruption still cause problems if left undetected. These five locations are the most prevalent locations and the locations where the most damage can be done.
TOLIS Group, Inc. ('TOLIS') provides scripts written by BRU Software ('BRU') users, for BRU users and assumes no responsibility for their content or operation in any particular environment. Further, TOLIS assumes no liability for potential harm or damage, software or hardware, that may result from their use. The scripts are provided as examples only and must be modified for your use. VERIFY THE USEFULNESS of the script before you use it.
Once the script has been downloaded to your Desktop, execute the following command:
From here, you have four options to get your system into good working order. They are:
Until your system is back into a good, working state, any data on that system is considered to be at risk. Therefore, getting the system in question back up and running should be considered the first priority.
For technical assistance, customers with technical support agreements may contact TOLIS Group Technical Support.
|Others in this Category|
|Here We Come, NAB 2013!|
|TOLIS Group Partnership Brings Archival to Thunderbolt|
|Lion Update Warning for BRU PE 2.2.x Users|
|Smaller & Quieter Chassis|
|Datestamp Not Added to Scheduled Disk-Based Archives|
|» More Articles|