PRIORIS ZX MP5 SERVICE INFORMATION
Troubleshooting
Guide
Initial Troubleshooting
Record all configuration information and have readily available.
•
Turn off server, wait until all hard disk drives completely spin down, and
•
then turn back on.
Record all error messages.
•
Make sure all cables and connections are secure.
•
Make sure all necessary video, printer, and application device drivers
•
are properly installed.
Troubleshoot one problem at a time.
•
Try to duplicate the problem.
•
Run the diagnostic software.
•
Run the SCU.
•
1
Initial Troubleshooting
1-1
Server Troubleshooting
Problem Possible Cause Action
2
Troubleshooting
No response when the
server is turned on.
Server is not plugged
in.
No power at the wall
outlet.
Main logic board failed.
Main logic board
jumpers incorrectly set.
CPU module has failed.
No memory module or
SIMMs installed.
Side panels removed.
Power supply failed.
Turn off the server, plug it in,
and then turn it back on again.
Use another wall outlet.
Replace main logic board.
Set all appropriate jumpers.
Reseat the CPU module. If
failure continues, replace CPU
module.
Install SIMMs and memory
module.
Install side panels.
Replace power supply.
continued
2-1
Troubleshooting
Problem Possible Cause Action
Power is on, but there is
no screen display.
Power is on but no
OCP display.
Power is on but cooling
fans do not work.
Server operates
incorrectly after
installing a CPU
module.
Monitor brightness and
contrast controls are
not correctly set.
Monitor is off.
Monitor cable is
incorrectly installed.
Incorrect video drivers
installed.
Video controller has
failed.
Monitor has failed.
OCP button not turned
on or OCP backlight is
disabled in SCU.
OCP has failed.
Fans disconnected
from main logic board.
One or more fans
failed.
CPU module installed
incorrectly.
Primary CPU module
has failed.
Adjust the brightness and
contrast controls.
Turn on the monitor.
Check all monitor connections.
Install the correct video
drivers.
Replace main logic board.
Replace monitor.
Press any keyboard key or
OCP button at the front of the
server.
Make sure OCP backlight is
set to ON in the SCU.
Replace OCP display.
Connect the fans.
Replace fan(s).
Reinstall CPU module.
Replace CPU module.
2-2
Secondary CPU
module has failed.
Remove CPU module and
reboot. If server boots without
errors, replace CPU module.
continued
Problem Possible Cause Action
Troubleshooting
Server operates
incorrectly after
installing optional
expansion board.
Server operates
incorrectly after
installing optional
memory (SIMMs).
No response to
keyboard commands.
Expansion board
installed incorrectly.
Did not run SCU to
configure expansion
board after installation.
Did not install CFG file
for expansion board.
Expansion board has
failed.
SIMMs installed
incorrectly.
SIMMs have failed.
Memory module
installed incorrectly.
Memory module failed.
Keyboard might be
password protected by
a local or remote
control program.
Keyboard is not
connected.
Keyboard is connected
to the mouse port.
Keyboard failed.
Remove expansion board and
reinstall.
Run the SCU to properly
configure expansion board.
Run SCU and add CFG file (if
necessary).
Remove expansion board and
reboot. If server boots without
errors, replace expansion
board.
Remove SIMMs and reinstall.
Reorder SIMMs. Make sure
SIMMs are installed in the
appropriate memory banks
and are completely filled. If
problem persists, replace
SIMMs.
Reinstall memory module.
Replace memory module.
Enter the keyboard password.
Power down the server and
connect the keyboard.
Power down the server and
connect the keyboard to the
keyboard port.
Replace keyboard.
continued
2-3
Troubleshooting
Problem Possible Cause Action
No response to mouse
commands.
Server operates
correctly but application
software does not.
Mouse might be
password protected by
a local or remote
control program.
Mouse is not
connected.
Mouse is connected to
the keyboard port.
Mouse driver not
installed.
Mouse trackball dirty.
Mouse failed.
Application software
installed incorrectly.
CPU speed setting
causes conflict with
application software.
Having system cache
enabled causes conflict
with application
software.
SCSI device has failed.
Enter the keyboard and
mouse password.
Power down the server and
connect the mouse.
Power down the server and
connect the mouse to the
mouse port.
Install the appropriate mouse
driver.
Clean trackball.
Replace mouse.
Refer to your application
software documentation.
Run the SCU and reduce CPU
speed setting.
Run the SCU and disable
system cache.
Replace SCSI device.
2-4
continued
Problem Possible Cause Action
Troubleshooting
Server does not boot
from CD-ROM drive.
Target diskette drive
cannot read or write
information.
CD-ROM drive is not
connected to the
Adaptec controller.
CD-ROM drive not
configured as a
bootable device.
CD-ROM disk is not
bootable.
SCSI device has failed. Make sure CD-ROM disk is
Diskette is not
formatted.
Diskette is worn or
damaged.
Diskette is writeprotected.
Diskette drive is empty.
Diskette write
protection enabled.
Diskette drive has
failed.
Connect the CD-ROM drive to
the onboard 7870 Adaptec
controller.
Change the CD-ROM setting
to “bootable” using
Select
SCSI
CD-ROM disk media must be
bootable to boot from CDROM disk.
bootable. If failure continues,
replace SCSI device.
Format the diskette.
Try another diskette.
Slide the write-protect switch
so the hole is not visible.
Insert a diskette.
Run the SCU and set the
Diskette Write Protection
option to “Disabled.”
Secure ribbon cable and other
connectors on back of diskette
drive. If failure continues,
replace diskette drive.
.
2-5
Troubleshooting
Disk Drive Troubleshooting
Problem Possible Cause Action
Server does not
recognize an
internal SCSI
device.
Server does not
recognize an
external SCSI
device.
SCSI device jumpers
incorrectly set.
SCSI ID conflicts.
Terminating resistors not
removed from the SCSI
device.
SCSI controller has failed.
Loose SCSI cable.
SCSI cable incorrectly
installed between SCSI
controller, SCSI device or
backplane.
SCSI device jumpers
incorrectly set.
SCSI ID conflicts.
Terminating resistors not
removed from the SCSI
device.
SCSI controller has failed.
Refer to the supplied kit
installation instructions.
Refer to the supplied kit
installation instructions.
Remove terminating resistors.
Refer to the supplied kit
installation instructions.
Replace main logic board.
Secure all cable connections.
Correctly install SCSI cable.
Refer to the supplied kit
installation instructions.
Refer to the supplied kit
installation instructions.
Remove terminating resistors.
Refer to the supplied kit
installation instructions.
Replace main logic board.
2-6
Loose SCSI cable.
SCSI cable incorrectly
installed between SCSI
controller and rear panel
connector or external
SCSI device and rear
panel connector.
Secure all cable connections.
Correctly install SCSI cable.
continued
Problem Possible Cause Action
Troubleshooting
Server does not
boot from an internal
SCSI hard disk
drive.
SCSI boot hard disk
drive not formatted.
SCSI device drivers not
installed or incorrectly
installed on SCSI boot
hard disk drive.
Operating system
software is not installed
on the SCSI boot hard
disk drive.
Requested partition does
not exist.
SCSI boot hard disk
drive at wrong SCSI
address.
Format the SCSI hard disk
drive.
CAUTION: Formatting the
SCSI hard disk drive will destroy
all the data on the drive.
Properly install all required SCSI
device drivers.
Install the appropriate operating
system.
Partition the SCSI hard disk
drive and then reload the
operating software.
Set SCSI boot hard disk drive to
lowest “primary” SCSI address.
continued
2-7
Troubleshooting
Problem Possible Cause Action
Server does not
boot from a target
diskette drive.
Drive ID incorrectly set.
Diskette drive not
enabled.
Diskette boot option
disabled.
Diskette does not contain
start-up files.
Diskette drive is empty.
Diskette is worn or
damaged.
Loose cables.
Make sure the drive ID is
correctly set. Refer to the
documentation that was
supplied with the diskette drive.
Run the BIOS Setup utility to
enable the diskette drive.
Run the SCU and set boot
option A then C.
Insert a diskette with the correct
start-up files.
Insert a diskette that contains
an operating system.
Try another diskette.
Secure all cable connections.
continued
2-8
Problem Possible Cause Action
Troubleshooting
SCSI hard disk drive
cannot read or write
information.
SBB failure. Check SBB status
Incorrect disk drive
jumper settings.
Loose or incorrectly
installed cables.
SCSI hard disk drive is
not correctly formatted
or partitioned.
SCSI hard disk has
failed.
LEDs for a drive failure
indication.
Refer to the supplied kit
installation instructions.
Make sure all cables are
correctly installed.
Format and partition as
required using the supplied
operating system.
Secure ribbon cable and other
connectors on back of SCSI
hard disk drive. If failure
continues, replace SCSI hard
disk drive.
If drive failed, replace SBB.
2-9
Troubleshooting
Monitor Troubleshooting
Problem Possible Cause Action
Monitor power indicator
is not on.
No screen display. Configuration error.
No monitor display
while loading Windows
video drivers.
Distorted, rolling, or
flickering screen
display, or
wrong/uneven color.
Monitor is turned off.
Power cord is not
connected.
No power at wall outlet.
Power indicator is
defective.
Monitor brightness and
contrast controls are
incorrectly set.
Monitor has failed.
Monitor type incorrectly
set.
Monitor incorrectly
adjusted.
Monitor signal cable
incorrectly installed.
Turn on the monitor.
Connect the power cord to the
server.
Use another outlet.
Replace power indicator.
Run the SCU to configure the
server for VGA operation.
Adjust the monitor brightness
and contrast controls.
Secure all cables and power
connections. If failure
continues, replace monitor.
Set the correct monitor type.
Adjust accordingly.
Straighten any bent connector
pins and then reconnect.
2-10
continued
Problem Possible Cause Action
Troubleshooting
Color monitor
displaying
monochrome.
Monitor fails to switch
to high-resolution
mode.
Monitor display not
centered while loading
Windows video drivers.
Server was turned on
before the monitor was
turned on.
Appropriate highresolution video drivers
are not installed or
incorrectly installed.
Monitor type incorrectly
set.
CD-ROM Troubleshooting
Problem Possible Cause Action
Cannot access the CDROM drive. Error
message reading drive
x.
Device drivers not
installed.
No disk in the CDROM drive.
Accessing wrong drive.
Tray open.
Turn off the server, turn on the
monitor, then turn the server
back on.
Correctly install all appropriate
high-resolution video drivers.
Refer to the documentation
supplied with your monitor.
Set the correct monitor type.
Install correct device drivers.
Insert a disk.
Make sure correct SCSI ID is
assigned.
Close the tray.
Power is on but
indicator shows no
activity.
Disk is spinning but
drive is idle.
No disk or tray is open.
Check cable
connections.
Application software not
running.
Insert a disk and close the
tray.
Make sure cables are correctly
connected.
Run application software.
2-11
Loading...