New in the Community? Get started here

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Building Automation Knowledge Base
Showing results for 
Show  only  | Search instead for 
Did you mean: 
PSST, your community homepage is getting a new face - stay tuned and experience the change in few days

Network 8000 HOST will not boot up, message "Unrecoverable error has occurred"


Network 8000 HOST will not boot up, message "Unrecoverable error has occurred."

In some cases where the HOST loses power or is shut down without exiting properly, it will not boot up, and displays the following series of messages:

"Strong possibility that 3:/DMC.fmon / 011 has lost data.
** ERROR** In Shell call to fcompress to Routine error –1.
** ERROR** In Routine rebuild_fx_file error -14.
** ERROR** In Call to routine rebuild_db_file.
** ERROR** Unrecoverable error has occurred."

Product Line

TAC IA Series


Network 8000


Host was not properly shut down.


To correct the problem, login to the QNX operating system and perform the following steps. QNX commands are enclosed in angle brackets, < cmd >. Type just the command, not the brackets, followed by ENTER.
See the HOST 8000 Troubleshooting Guide, F–26369, for more details on QNX commands and syntax.

  1. Check disk space, < files 3:/ >, note results, if less than 90% full, no problem.
  2. Check for busy files, < files 3:/ +b >, note results.
  3. Check for busy directories, < files 3:/ +d +b >, delete the 3:/tmp temporary directory, < zap 3:/tmp >. Should be prompted “file zapped”.
  4. Check the 3:/DMC.fmon directory, delete file new.f if it exists.
    1. Change directory, < cd DMC.fmon >.
    2. Verify change of directory, < pwd >,should be “3:/DMC.fmon”
    3. List contents of directory, < ls > ( lower-case L, not the number 1).
    4. Delete file new.f if it exists, < zap new.f >, should see “file zapped”.
  5. Delete the 011 file group, as follows:
    1. < zap 011.f >, should see “file zapped”.
    2. < zap 011.k >, should see “file zapped”.
    3. < zap 011.x >, should see “file zapped”.
    4. Verify file deletion, < ls > ; 011.f, 011.k, and 011.x should be gone.
  6. Recreate the 011 file group, as follows:
    1. < fconstruct 011 >
    2. < kconstruct 011 >
    3. Verify files have been rebuilt, < ls >; contents should include 011.f, 011.k, 011.x as well as the 021 and 054 files.
  7. Reboot the system, it should now boot all the way to the white Barber-Colman login screen.
Tags (1)
Labels (1)
No ratings