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.
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:
- Inside Applications -> Utilities, there is a utility called "Terminal
". Double-click on the utility to open it.
- At the command prompt, copy-and-paste the following command:
sudo tar -zxvf ~/Desktop/Damage_Check.tgz -C /
- When prompted for your password, enter your System Administrator password.
- The Damage_Check script will be installed.
- Once the installation is complete, it should only take a few seconds, execute the following command:
sudo damage_check --run
- The script will then run, checking all five location mentioned prior. If the system is clean, you'll see the following output:
$ sudo damage_check --run
Running check on '/bin/'
Running check on '/sbin/'
Running check on '/usr/bin/'
Running check on '/usr/sbin/'
Running check on '/usr/share/zoneinfo/'
There were no files of zero bytes found.
The system looks clean!
If the system is not clean and corrupt files are found (which is why you're here anyway), the files will be listed by the utility.
- If any files are reported, you'll need to proceed to the lower section, which asks if you would like to perform a permissions repair, as shown:
If you're experiencing problems with the booted operating system, which is
probably why you're running this script, it's a good idea to perform a Repair
Permissions on the main system volume. Would you like to perform the Repair
Permissions operation now?
Enter "Y" for 'Yes', anything else to exit:
Enter "Y" to perform a permissions check. This permissions check does the same thing that Disk Utility does, in-fact, it actually calls the Disk Utility application.
From here, you have four options to get your system into good working order. They are:
- Perform a Disk Utility check of the drive while booted from the Mac OS X
install disk (a repair cannot be done live, so there's not point in trying it live).
- If #1 doesn't work, many, many customers have reported success in re-installing the most recent Combo Update for your system. Not the delta update (the update that lets you go from 10.6.7 to 10.6.8), but the Combo Update (which allows you to go from 10.6.0 to 10.6.8 directly).
- Use disk repair tools such as Disk Warrior to repair the boot drive corruption that has occurred on the system.
- Very rare cases require this last-resort option and that is to re-install the whole OS. Since steps 1, 2, and 3 are known to fix this problem, the full reinstall is an absolute last-resort solution.
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.