Step 4: Identify problems using the startup sequence
The startup sequence is your primary tool for identifying a K2 Summit system fault. As the different levels of the K2 Summit system system become operational in the startup process, the primary components of the system are checked. You can identify most problems by evaluating the messages and other indicators that occur during the startup sequence.
Note: This procedure assumes that the
K2 Summit system is not in Storage Utility’s “offline”
mode.
To identify problems using the startup sequence, do the following:
- Connect mouse, keyboard, and monitor. You must observe the VGA screen and be able to interact with the system via keyboard and mouse to fully identify problems.
- Restart the K2 Summit system.
-
Once the startup sequence begins, observe the
progression of behaviors as listed in the following table. These are the
behaviors you should expect for a normally operating
K2 Summit system. If you observe behaviors other
than those listed, refer to the indicated troubleshooting topics to identify
problems.
Note: You can press the Pause/Break key on the keyboard to keep startup text on the screen for longer viewing.
At about this time… This behavior should occur… If not, refer to the following: — Pressing the standby button starts the K2 Summit system. Shutdown/restart problems 0 seconds Power on LED goes on and stays on. Power supply problems Service LED stays off. Shutdown/restart problems Front bezel assembly and processor fan start. Windows startup problems 10 seconds System BIOS screen appears. BIOS startup 35 seconds Grass Valley logo screen appears. — 70 seconds Windows logon screen appears. Windows startup Logon to Windows to continue the startup sequence.
After Windows logon:
At about this time… This behavior should occur… If not, refer to the following: 0 seconds Grass Valley logo desktop appears. K2 Summit system startup 5 seconds Service LED goes on for a few seconds, then off. 20 seconds Desktop icons, startbar, and AppCenter logon box appear. Windows startup, K2 Summit system startup Logon to AppCenter to continue the startup sequence.
After AppCenter logon:
At about this time… This behavior should occur… If not, refer to the following: 0 seconds System Startup messages appear. K2 Summit system startup Time varies. Between 30 seconds and 2 minutes. All system components check out as OK and AppCenter opens. Media operations are functional. Operational problems