Specifications

MDR User Guide  85 
A Troubleshooting 
Below is a table of the most frequently occurring error situations and the actions for 
correcting them. 
Symptom/Error Message  Remedy 
The MDR client (Shell or API) is unable 
to connect to the MDR server. 
Connect a terminal to the MDR (i960) serial 
port, and check for error messages. 
The MDR system reports that some 
disks could not be found. 
Make sure that the Fibre Channel cable is 
properly attached between the MDR and 
JBOD/RAID. Check also that all the disks are 
properly inserted. 
There is no message sent to the i960 
serial port when the MDR is powered 
up. 
Check that the MDR board is properly inserted 
into your VME crate. Contact VMETRO to 
verify that the board is correctly inserted. 
The MDR client (Shell or API) is unable 
to connect to the MDR server and the 
latter does not print any error messages 
to the serial port. 
Check that the network (boot) parameters are 
correctly set up. 
The MDR server reports either DPIO 
FIFO overflow or MIDAS Memory 
buffer overflow during a recording. 
Make sure that your data source is not sending 
data faster than the MDR system is able to 
handle. Also, check that the expected number 
of disks is being used by the MDR server. 
The MDR system only uses X out of Y 
(expected) disks (with X<Y). 
Check that the value of the item Disks in 
section StorageInfo in mdr.ini is set to X. 
The MDR system reports that it is unable 
to configure a VMFC-2100 card. 
Check that the VMFC-2100 card is positioned 
in the PMC slot specified by the item VMFC-
2100UnitXPmcSlot
 (X is 3 or 4) in section 
StorageInfo in the mdr.ini file. Contact 
VMETRO to verify that the card is in the 
correct PMC slot. 
FC Loop is : DOWN  Check that the Fibre Channel cable is correctly 
inserted into the JBOD/RAID and the VMFC-
2X00. Power up the JBOD/RAID and reboot 
the system by pressing the Reset button on the 
MIDAS board. Check that there is proper air-
cooling. 
MDR client unable to connect to the 
server. 
Check the sX parameters in the mdr.ini file. 
Recording table is invalid: should be 
cleared. 
If the recording data is not critical, clear the 
recording table (MDR Shell command Clear), 
Otherwise, try to swap disks in use (JBOD) if 
some of them have been previously swapped. 
If a new version has been installed on the 
MDR, call VMETRO for information on how 
to update the recording table without losing 
data. 
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com










