NEC Express5800 Series User Manual page 298

7-26 Troubleshooting
The keyboard or mouse fails to operate:
Is the cable properly connected?
Make sure that the cable is connected to the correct connector on the rear of the
server.
Are the keyboard and mouse are compliant with NEC Express5800/ft series?
Operation of the server with unauthorized devices is not guaranteed.
Does the server have drivers installed?
Refer to the manual that comes with your OS to check that the keyboard and
mouse drivers are installed. (These drivers are installed along with the OS.) Some
OS's allow you to change the keyboard and mouse settings. Refer to manual that
comes with your OS to check that the keyboard and mouse settings are correct.
Screen freezes, keyboard and mouse do not work:
If the amount of memory is large, it takes time to copy the memory in dual mode
and the system stops working temporarily during the copying, but it is not system
trouble.
Fail to access (read or write) to the floppy disk:
Does the floppy disk drive contain a floppy disk?
Insert a floppy disk into the floppy disk drive until it clicks.
Is the floppy disk write-protected?
Place the write-protect switch on the floppy disk to the "Write-enabled" position.
Is the floppy disk formatted?
Use a formatted floppy disk or format the floppy disk in the floppy disk drive.
Refer to the manual that comes with the OS for formatting a floppy disk.
Is the media mounted?
If a failover occurs while the media is mounted, the media is forcibly unmounted.
Therefore you need to mount it again. (When mounting CPU/IO module and at a
failover, errors such as buffer I/O error may be recorded, but there is no problem
on operation they are specifications of the server.) After the failover, device name
of the floppy disk drive may be changed (Ex. from scd0 to scd1), that
phenomenon is due to the specifications of the server and does not affect the
operation. In such a case, specify the changed device name for mounting the
media.
Mount point is not automatically created:
If mount point is not automatically created, the service needs to be restarted. Run
the following commands as root user to start the service.
# /etc/init.d/messagebus restart
# /etc/init.d/haldaemon restart