X system cannot start normally, there are no more than five common symptoms:
☆The screen is an empty blue screen, and you may also see an icon representing a process. , looks like a colorful death feng shui wheel or rotating disk.
☆On the screen is a cracked folder, a forbidden symbol, or a "kernel chaos" prompt box in multiple languages.
☆The screen is an empty gray screen.
☆Question marks flashed on the screen.
☆If there is no one of the above symptoms, the machine just doesn’t respond.
The screen is empty, only a blue screen, and sometimes an icon representing the process, like a colorful death feng shui wheel or a rotating disk
When encountering this If you have any symptoms, you can do the following nine steps in order to help us find out the crux step by step, and finally eliminate the fault that cannot be started. Although some of these methods are relatively technical, you can still try to use these methods to repair the system:
1. When the X system starts, it will preview the files in the system folder of the Classic Platform System 9 If the fonts in the font library are damaged, the X system will not be able to start.
Tip: Installing or updating to X 10.2.4 or later versions can avoid this problem. In other words, if your system is already X 10.2.5 or above, then such symptoms are definitely not caused by the system font of the classical platform. You can skip this step and go directly to step 2. step.
Method:
⑴ Start the machine from system 9 (or use the system 9 CD). If your machine can only start from system Just hold down the Shift key when starting.
⑵ Drag the font folder in the system folder of System 9 to the desktop.
⑶ Restart to the X system.
If the x system starts normally, it means that the problem lies in the font library of the classical system. From now on, we can only reinstall the font library of the classical system to completely fix this fault. If the problem persists, please proceed to the next step.
2. Remove incompatible third-party startup items.
⑴ Start the machine from system 9 (or use the system 9 CD). If your machine can only be started with the X system, boot the system into safe mode.
⑵Open the startup disk of the X system.
⑶ Drag the third-party startup items out of the /Library/StartupItems and System/Library/StartupItems folders and put them in one place temporarily. If you are not sure whether an item is a third-party item or an item installed on the Apple system, don't drag it out.
⑷Restart the machine to the X system.
If the problem is solved, it will be determined that a third-party startup project is causing the system to fail to start. But if the situation persists, proceed to the following steps.
3. Incompatible login items may also cause this symptom
⑴ If it is a system after Jaguar, you can start the machine in safe mode.
⑵ Select System Preferences from the Apple menu.
⑶ Remove all login items in the account control panel. If it is a Jaguar system, select the login items directly in the system settings and remove them.
⑷Restart the system.
⑸If the system startup returns to normal, add the login items just removed one by one. Each time you add one, start the system until you find an incompatible login item and delete it.
If the fault cannot be solved even after removing all the login items, it means that the problem is not a compatibility issue with the login items, then go to the next step.
4. If "Automatically connect when starting a TCP/IP program" is selected in the system's network settings, this symptom may sometimes occur. This requires deleting this profile. After deleting the preset file, you need to reset all network settings of your machine.
⑴ Start the machine into single-user mode (press the Command S key during startup and do not release it until the text interface appears).
⑵Enter: mount -uw / and press Enter. Note that there is a space between -uw and /.
⑶Enter: mv /var/db/SystemConfiguaration/preferences.xml/preferences.old and press Enter.
⑷Enter: reboot and press Enter.
If you still cannot start after doing this, go to step 5.
5. ⑴ Start the machine into single-user mode.
⑵Enter: mount -uw / and press Enter.
⑶Enter: mv /Library/Preferences/com.apple.loginwindow.plist preferences2.old and press Enter.
⑷Enter: mv /Library/Preferences/com.apple.windowserver.plist preferences3.old and press Enter.
⑸Enter: reboot and press Enter.
If the symptoms persist after the above treatments, proceed to step 6.
6. Reset some permissions
⑴ Start the machine into single-user mode.
⑵ Use the fsck program to check the disk. The method is to enter: /sbin/fsck -f and press Enter.
⑶Enter: mount -uw / and press Enter.
⑷Enter: chmod 1775 / and press Enter.
⑸Enter: reboot and press Enter.
Note: If performing any of the above steps can solve the problem, the repair ends here.
7. If the X system automatically logs in to your account when booting without entering your login password, do the following. Otherwise, proceed directly to step 8.
⑴ Start the machine into single-user mode.
⑵ Use the fsck program to check the disk.
⑶Enter: mount -uw / and press Enter.
⑷Enter: cd /Users/[affected user name]/Library. For example, if the affected username is wally, enter: cd /Users/wally/library and press Enter.
⑸Enter: mv Preferences Preferences_old and press Enter.
⑹Enter: mv Caches Caches_old and press Enter.
⑺Enter: reboot and press Enter.
If you can now successfully start and log in to your account, then take the following steps to completely eliminate this problem:
⑻Open the "Console" program in the utility folder ( Consale), select "Open Log" from the "File" menu:
⑼Enter: /var/log/system.log in the "Go to:" box, and click the "Open" button.
⑽ Select "Find" from the "Edit" menu.
⑾Enter: parse failed in the "Find:" box, and then click the "Next" button.
⑿View the entire log and find records similar to the following:
{date} Dock[500] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: com.apple.dock.plist --
/Users/us/Library/Preferences/ The parser will retry as in 10.1, but the problem should be corrected in the plist. {date} trident crashdump: Crash report written to: /Users/us/Library/Logs/CrashReporter/Dock.crash.log
⒀Every transaction found All files with the .plist suffix displayed on the Parse failed record are removed from the ~/Library/Preferences_old folder. ~ represents the folder of your username.
⒁Repeat steps ⑿ to ⒀ until all files with the .plist suffix displayed in the parse failed record are removed.
⒂Rename the ~/Library/Preferences folder to "Preferences_new" in Finder.
⒃Rename the Preferences_old folder to "Preferences".
⒄Select out of the Apple menu. Log in again after the login window appears again.
Note: If the issue is resolved at this time, this will be terminated immediately. Otherwise, skip directly to step 9.
8. If the system can be started, but the machine will be restarted every time you log in, perform the following steps:
⑴ Boot to single-user mode.
⑵ Use the fsck program to check the disk.
⑶Enter: -uw / and press Enter.
⑷Enter: cd /Users/(affected user name)/Library.
⑸Input: mv Preferences Preferences_old.
⑹Enter: reboot and press Enter.
If you can successfully log in to Finder at this time, follow the following steps to completely eradicate this fault:
⑻Open the "Console" program in the utility folder, and click "File" Select "Open Recording" from the menu.
⑼Enter:/var/log/system.log in the "Go to" field and click the "Open" button.
⑽ Select "Find" from the "Edit" menu.
⑾Enter: parse failed in the "Search" field, and then click the "Next" button.
⑿View the entire log and find records similar to the following:
{date} Finder[500] CFLog (0): CFPropertyListCreateFromXMLData(): plist parse failed; the data is not proper UTF-8. The file name for this data could be: com.apple.HIToolbox.plist -/Library/Preferences/ The parser will retry as in 10.1, but the problem should be corrected in the plist. {date} trident crashdump: Crash report written to: /Users/us/Library/Logs/CrashReporter/Finder.crash.log
⒀File with .plist suffix displayed on each Parse failed record found , removed from the ~/Library/Preferences_old folder.
⒁Repeat steps ⑿ to ⒀ until all files with the .plist suffix related to parse failed records are removed.
⒂Rename the ~/Library/Preferences folder to "Preferences_new" in Finder.
⒃Rename the Preferences_old folder to "Preferences".
⒄Select out of the Apple menu. Log in again when the login window appears again.
9. If the fault still exists, follow the steps below to troubleshoot the "blank gray screen fault".
The screen appears with a cracked folder icon, a forbidden symbol, or a kernel-messaging message box in five languages.
When the kernel panics, a message with white text on a black background will be displayed at the top of the video on the screen. The message begins with a sentence similar to this: "Unresolved kernel trap". In the Puma system, a cracked folder appears when a kernel panic occurs. However, in the Jaguar system and the Panther system, there is no cracked folder, but a forbidden road sign symbol.
1. Symptoms like this are usually caused by some files or folders being illegally removed, replaced or damaged. Of course, it may also be caused by some hardware or software inside the machine, and such problems must be avoided. Some system projects and folders are not visible in the X system, such as "mach_kernel". However, if the machine is started from System 9, or some programs that can see the system's invisible files are started, these files will become visible and will be deleted inadvertently, causing the X system to fail to start.
The following system items in the root directory of the X system boot disk must not be deleted, changed or moved to other places:
◆mach_kernel (invisible file)
p>◆Application (visible folder)
◆automount (invisible folder)
◆Resource library (visible folder)
◆System Folder
◆User Folder
Sometimes the mach_kernel file is damaged. You can start the machine from System 9, insert the X system CD, and open the CD. See a same mach_kernel file, drag this file into the startup disk of the X system, and select to replace the mach_kernel file in the original disk in the replacement dialog box that appears. Then select system X as the startup disk on the startup disk control panel. If the problem is solved after restarting the system, you can stop here. If the problem persists, you will have to reinstall the system.
2. Sometimes the above symptoms may appear even if the status of the above files or folders has not been changed, which requires further investigation. If you are sure that they are still in the correct location, you can do the following:
⑴Reset NVRAM and PRAM and change some system settings. How to reset NVRAM: Boot to open the firmware program, enter: reset-nvram, and press Enter. Enter: reset-all.
⑵ Then press the X key to force the machine to start from the X system. If you can boot to the X system in this step, you need to select the X system startup disk in the system preferences again. If it still doesn't work, go to the next step.
⑶ Start from system 9 (system CD or disk boot is acceptable), open the startup disk control panel, and select the X system disk as the startup disk.
⑷Close the startup disk control panel.
⑸ Restart the machine. If the problem is solved, you can stop here.
⑹ If the problem persists, the system must be reinstalled. If you use a system installation CD to boot your machine, make sure that the system CD is not too old for your machine. Because newer machines cannot be started with early X systems. For example, iBook G4 cannot be started with Jaguar system.
3. Some hardware will cause kernel panic during startup. If you have the following hardware installed, check to see if it is causing the problem:
◆AirPort Extreme Card
◆Matrox RTMac Card
◆128-Bit 2D/3D Professional Graphics Card
◆PC Card Modem
4. Some application installers may also cause this failure. Updating to Jaguar version 10.2.1 will cause this glitch. In other words, updating to 10.2.8 will not cause such system startup problems.
If the problem persists after the above troubleshooting methods, you have to troubleshoot according to the following "blank gray screen" symptoms.
A "blank gray screen" appears during startup
⑴ Check whether your machine has the latest firmware update installed. If not, please download and install it now.
⑵ In addition to the Apple keyboard and mouse, disconnect all peripheral devices, including all ADB, Serial, USB, Firewire, SCSI and PCMCIA interface devices. If this solves the problem, reconnect the disconnected devices individually. Connect one unit at a time and start the machine until you find the problematic peripheral.
⑶ Remove hardware upgrades from third-party manufacturers, such as memory modules, CPU upgrade cards, PCI cards, etc. If this eliminates the problem, reinstall the hardware one by one, one at a time and start it up, until the problematic hardware is identified.
⑷ Start the machine from the X system CD and use "Disk Utility" to check the hard disk.
If necessary, enter single-user mode and use the fsck program to troubleshoot.
⑸ If convenient, reset your computer’s power management unit (PMU).
A flashing question mark appears on the screen
Such a symptom usually means that the machine cannot find the system. Often after the question mark appears, there will be two different results: after a period of delay, the machine finds the system and starts; in the end, the machine cannot start.
If it is the former, it can usually be eliminated by reselecting the startup disk on the startup disk control panel. If it is the latter, you must follow the following steps to eliminate it:
⑴ Start the machine with the system CD, use the disk tool to repair the disk, and then try to start the system from the disk.
Tip: If your disk cannot be mounted after booting the machine from the CD, perform a PRAM reset, and then try booting from the CD again. If the disk still cannot be mounted after resetting the PRAM, it must be sent to an Apple technical center for repair.
⑵ Re-select the startup disk of the X system, or press the X key during startup.
⑶ If it still doesn’t work, reset the PRAM.
⑷ Check and troubleshoot SCSI peripheral equipment faults. For example, incorrect ID settings, terminators or SCSI cables may cause this failure. Exclude it according to the following methods:
① Shut down the system.
② Turn off all connected devices.
③ Remove all SCSI chain connections from the computer. If you have a third-party SCSI card installed, remove it as well.
④Restart the system.
⑸ If these measures fail to eliminate the fault, start the machine with the system CD and reinstall the X system. If your disk cannot be mounted after booting from the CD, send the machine for repair.
There are no symptoms, but it cannot be started and the system is unresponsive.
⑴ If the Ethernet cable is connected to your computer, temporarily unplug the network cable and then start it. If you have activated the NetInfo management program, turn it off temporarily.
⑵ The following system files and folders cannot be renamed or moved to other places:
◆Applications (visible folders)
◆automount (invisible folder)
◆Resource Library (visible folder)
◆mach_kernel (invisible file)
◆System Folder
◆User Folder
⑶ Follow the "blank gray screen" troubleshooting guide.