Print | Rate this content

Troubleshooting Guide: HP t5730/t5730w and t5735 Thin Client - Diagnostics and Troubleshooting

LEDs

Power and IDE Flash Activity LEDs
LED
Status
Power LED Off
When the unit is plugged into the wall socket and the Power LED is off, the unit is powered off. However, the network can trigger a Wake On LAN event in order to perform management functions.
Power LED On
Displays during boot sequence and while the unit is on. During boot sequence, hardware initialization is processed and startup tests are performed on the following:
  • Processor initialization

  • Memory detection and initialization

  • Video detection and initialization

If one of the tests fails, the unit will simply stop, but the LED will stay on. If the video test fails, the unit beeps. There are no messages sent to video for any of these failed tests.
After the video is initialized, anything that fails will have an error message.
RJ-45 LEDs are located inside the RJ-45 connector on the top, rear panel of the thin client. The LEDs are visible when the connector is installed. Blinking green indicates network activity, and amber indicates a 100MB speed connection.
IDE LED is Off
When the unit is powered on and the flash activity light is off, then there is no access to the system flash.
IDE LED blinks Green
Indicates the system is accessing the internal IDE flash.

Power-On Sequence

At power-on, the flash boot block code initializes the hardware to a known state, then performs basic power-on diagnostic tests to determine the integrity of the hardware. Initialization performs the following functions:

  1. Initializes CPU and memory controller.

  2. Initializes VGA software.

  3. Initializes and configures all PCI devices.

  4. Initializes the video to a known state.

  5. Initializes USB devices to a known state.

  6. Performs power-on diagnostics. For more information, see “Power-On Diagnostic Tests”.

  7. The unit boots the operating system.

Power-On Diagnostic Tests

The Power-on diagnostics performs basic integrity tests of the hardware to determine its functionality and configuration. If a diagnostic test fails during hardware initialization the unit simply stops. There are no messages sent to video.

You may try to restart the unit and run through the diagnostic tests a second time to confirm the first shutdown.

The following table lists the tests that are performed on the t5000 units.

Power-On Diagnostic Test
Test
Description
Boot Block Checksum
Tests boot block code for proper checksum value
DRAM
Simple write/read pattern test of the first 640k of memory
Parallel Port
Initiates the port’s driver and determines if the device is present
Serial Port
Tests the serial port using simple port verification test to determine if ports are present
Timer
Tests timer interrupt by using polling method
RTC CMOS battery
Tests integrity of RTC CMOS battery
NAND flash device
Tests for proper NAND flash device ID present

Beep Codes

If there are no video errors, the system goes directly to POST messages.

Beep Code
Description
1 long, 2 short
A video error has occurred and the BIOS cannot initialize the video screen to display any additional information.
1 long, 3 short
System running in boot block recovery mode.

POST Error Messages

POST Error Messages
POST Error Message
Description
BIOS ROM checksum error - System halted
The checksum of the BIOS code in the BIOS chip is incorrect, indicating the BIOS code may have become corrupt. To restore a corrupt BIOS, refer to Appendix D, “System BIOS” or call your local HP Call Center for a diagnosis. For phone numbers of an HP Call Center near you, visit the following Web site: http://www.hp.com/cgi-bin/hpsupport/index.pl
CMOS battery failed
The CMOS battery is no longer functional. For information on replacing the battery, refer to Appendix E, “Replacing the CMOS Battery.”
CMOS checksum error - Defaults loaded
Checksum of CMOS is incorrect, so the system loads the default equipment configuration. A checksum error may indicate that CMOS has become corrupt. A weak battery may have caused this error. Replace the battery if necessary. For more information, refer to Appendix E, “Replacing the CMOS Battery.”
CPU at nnnn
Displays the running speed of the CPU.
Press ESC to skip memory test
The user may press Esc to skip the full memory test.
Hard Disk Install Failure
Cannot find or initialize the hard drive controller or the drive. Make sure the controller is installed correctly. If no hard drives are installed, be sure the Hard Drive selection in Setup is set to NONE.
Keyboard error or no keyboard present
Cannot initialize the keyboard. Make sure the keyboard is attached correctly and no keys are pressed during POST. To purposely configure the system without a keyboard, set the error halt condition in Setup to HALT ON ALL, BUT KEYBOARD. The BIOS then ignores the missing keyboard during POST
Memory Test
This message displays during a full memory test, counting down the memory areas being tested.
Memory Test Fail
If POST detects an error during memory testing, additional information appears giving specifics about the type and location of the memory error
Override enabled - Defaults loaded
If the system cannot boot using the current CMOS configuration, the BIOS can override the current configuration with a set of BIOS defaults designed for the most stable, minimal-performance system operations.
Press TAB to show POST screen
Press the TAB key during POST to display messages hidden by the HP logo.
Error: Non-System disk or disk error
The BIOS was unable to find a suitable boot device. For the t5000 Series, this may mean an uninitialized or corrupt ATA Flash. Reflash the unit and press any key when ready. For more information, refer to Chapter 5, “Restoring the Flash Image.”

Troubleshooting

Basic Troubleshooting

If the thin client is experiencing operating problems or will not power on, review the following items.

Power-On Troubleshooting
Issue
Procedures
The thin client unit is experiencing operating problems.
Ensure that the following connectors are securely plugged into the thin client unit:
  • Power connector

  • Keyboard

  • Mouse

  • Network RJ-45 connector

  • Monitor

The thin client unit does not power on.
  1. Verify that the power supply is good by installing it on a known working unit and testing it. If the power supply does not work on the test unit, replace the power supply.

  2. If the unit does not work properly with the replaced power supply, have the unit serviced.

The thin client unit powers on and displays a splash screen, but does not connect to the server.
  1. Verify that the network is operating and the network cable is working properly.

  2. Verify that the unit is communicating with the server by having the System Administrator ping the unit from the server:

    • If the thin client pings back, then the signal was accepted and the unit is working. This indicates a configuration issue.

    • If the thin client does not ping back and the thin client does not connect to the server, re-image the unit.

No link or activity on the network RJ-45 LEDs or the LEDs do not illuminate blinking green after powering on the thin client unit. (The network LEDs are located inside the RJ-45 connector on the top, rear panel of the thin client. Indicator lights are visible when the connector is installed.)
  1. Verify that the network is not down.

  2. Make sure the RJ-45 cable is good by installing the RJ-45 cable onto a known working device—if a network signal is detected then the cable is good.

  3. Verify the power supply is good by replacing the power cable to the unit with a known working power supply cable and testing it.

  4. If network LED's still do not light and you know the power supply is good, then re-image the unit.

  5. If network LED’s still do not light, run the IP configuration procedure.

  6. If network LED’s still do not light, have the unit serviced.

A newly connected unknown USB peripheral does not respond or USB peripherals connected prior to the newly connected USB peripheral will not complete their device actions.
An unknown USB peripheral may be connected and disconnected to a running platform as long as you do not reboot the system. If problems occur, disconnect the unknown USB peripheral and reboot the platform.
Video does not display.
  1. Verify that the monitor brightness is set to a readable level.

  2. Verify the monitor is good by connecting it to a known working computer and ensure its front LED turns green (assuming the monitor is Energy Star compliant). If the monitor is defective, replace it with a working monitor and repeat testing.

  3. Re-image the thin client unit and power on the monitor again.

  4. Test the thin client unit on a known working monitor. If the monitor does not display video, replace the thin client unit.

Diskless (No-Flash) Unit Troubleshooting

This section is only for those units that do not have ATA Flash capability. Because there is no ATA Flash in this model the boot priority sequence is:

  • USB device

  • PXE

  1. When the unit boots, the monitor should display the following information:

    Diskless Unit Troubleshooting
    Item
    Information
    Action
    MAC Address
    NIC portion of the system board is OK
    If no MAC Address, the system board is at fault. Contact the Call Center for service.
    GUID
    General system board information
    If no GUID information, the system board is at fault and should be replaced.
    Client ID
    Information from server
    If no Client ID information there is no network connection. This may be caused by a bad cable, the server is down, or a bad system board. Contact the Call Center for service for the bad system board.
    MASK
    Information from server
    If no MASK information there is no network connection. This may be caused by a bad cable, the server is down, or a bad system board. Contact the Call Center for service for the bad system board.
    DHCP IP
    Information from server
    If no DHCP IP information there is no network connection. This may be caused by a bad cable, the server is down, or a bad system board. Contact the Call Center for service for the bad system board.

    If you are running in an MS RIS PXE environment go to step 2.

    If you are running in a Linux environment go to step 3.

  2. If you are running in an MS RIS PXE environment press the F12 key to activate the network service boot as soon as the DHCP IP information appears on the screen.

    If the unit does not boot to the network the server is not configured to PXE.

    If you missed the F12 cue, the system will try to boot to the ATA flash that is not present. The message on the screen will read: ERROR: Non-system disk or disk error. Replace and press any key when ready.

    Pressing any key will restart the boot cycle.

  3. If you are running in a Linux environment an error message will appear on the screen if there is no Client IP. ERROR: Non-system disk or disk error. Replace and press any key when ready.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!