75.0 VREPAIR Messages

The following includes messages from VREPAIR.NLM.

VREPAIR-X-10: Unable to get resource tags.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-11: Unable to open VREPAIR status screen.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-12: Unable to open VREPAIR error screen.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-14: Unable to allocate memory for VREPAIR process stack.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-208: Error writing to error log file name. Message: message not written to file. Error log file closed.

Source: VREPAIR.NLM
Possible Cause: The log file’s disk media has failed (for example, removing the floppy diskette) or run out of space.
Action: If you want a log file, then stop VREPAIR using the F1 option, fix the media problem, and then run VREPAIR again. VREPAIR will continue to repair the volume if you do nothing.

VREPAIR-X-209: Error writing to error log file name. Error log file closed.

Source: VREPAIR.NLM
Possible Cause: The log file’s disk media has failed (for example, removing the floppy diskette) or run out of space.
Action: If you want a log file, then stop VREPAIR using the F1 option, fix the media problem, and then run VREPAIR again. VREPAIR will continue to repair the volume if you do nothing.

VREPAIR-X-279: Unable to allocate memory to read mirror FAT block sequence number.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-301: Unable to allocate memory to record needed FAT entry correction. Try using the Save Changes Immediately option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-302: Unable to allocate memory to record needed FAT entry correction.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-304: Unable to allocate memory to record needed FAT entry correction. Try using the Save Changes Immediately option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-305: Unable to allocate memory to record needed FAT entry correction.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-425: Unable to get enough memory to set up directory cache buffers.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-427: Unable to get enough memory to set up directory hash tables.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-441: Unable to allocate memory to record needed directory entry correction. Try using the Write Changes Immediately To Disk option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-442: Unable to allocate memory to record needed directory entry correction.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-444: Unable to allocate memory to record needed directory entry correction. Try using the Write Changes Immediately To Disk option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-462: This VREPAIR is not compatible with this OS.

Source: VREPAIR.NLM
Explanation: This VREPAIR version is not compatible with the current NetWare operating system. As changes are made to the NetWare file system, you must change VREPAIR.
Action: Load a version of VREPAIR that is compatible with the operating system.

VREPAIR-X-677: More than 999,999 new directory names have been generated.

Source: VREPAIR.NLM
Explanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.
Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.

VREPAIR-X-713: More than 999,999 new file names have been generated.

Source: VREPAIR.NLM
Action: See message VREPAIR-X-677: More than 999,999 new directory names have been generated..

VREPAIR-X-766: Unable to read directory entry number which was previously read.

Source: VREPAIR.NLM
Possible Cause: Volume data that VREPAIR previously read is not available because a major hardware failure occurred.
Action: Try to get the disk hardware back in working condition. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide..Then run VREPAIR again.

VREPAIR-X-767: Unable to read directory entry number which was previously read.

Source: VREPAIR.NLM
Action: See message VREPAIR-X-766: Unable to read directory entry number which was previously read..

VREPAIR-X-768: Unable to read directory entry number which was previously read.

Source: VREPAIR.NLM
Action: See message VREPAIR-X-766: Unable to read directory entry number which was previously read..

VREPAIR-X-769: Trustee entry was not found in directory trustee chain as expected.

Source: VREPAIR.NLM
Possible Cause: Volume data that VREPAIR previously read is not available because a major hardware failure occurred.
Action: Try to get the disk hardware back in working condition. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then run VREPAIR again.

VREPAIR-X-770: Unable to read directory entry number which was previously read.

Source: VREPAIR.NLM
Possible Cause: Volume data that VREPAIR previously read is not available because a major hardware failure occurred.
Action: Try to get the disk hardware back in working condition. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then run VREPAIR again.

VREPAIR-X-771: Trustee entry was not found in file trustee chain as expected.

Source: VREPAIR.NLM
Possible Cause: Volume data that VREPAIR previously read is not available because a major hardware failure occurred.
Action: Try to get the disk hardware back in working condition. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then run VREPAIR again.

VREPAIR-X-810: The name space list for entry number could not be corrected. To complete repairs, save changes and run VREPAIR again.

Source: VREPAIR.NLM
Explanation: The name space list for an entry could not be repaired. VREPAIR needs to start over to correct the problem.
Action: Save the changes you have made so far. Then run VREPAIR again.

VREPAIR-X-828: Unable to allocate memory to record needed directory corrections. Try using the Write Changes Immediately To Disk option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-829: Unable to allocate memory to record needed directory corrections.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-831: Unable to allocate memory to record needed directory corrections. Try using the Write Changes Immediately To Disk option.

Source: VREPAIR.NLM
Possible Cause: The server does not have enough memory available.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

VREPAIR-X-845: More than 999,999 new MAC names have been generated.

Source: VREPAIR.NLM
Explanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.
Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.

VREPAIR-X-849: More than 999,999 new OS/2 names have been generated.

Source: VREPAIR.NLM
Explanation: During the process of volume repair, VREPAIR sometimes needs to generate a new unique name for files and directories that have invalid or conflicting names. This error occurs when VREPAIR has run out of unique names for use during volume repair. The problem occurs only when the volume is badly damaged.
Action: If the volume is this badly damaged, try restoring it from a backup. If you do not have a backup, then try using a volume editor and rename the files manually.

VREPAIR-X-871: Unable to read directory entry number which was previously read.

Source: VREPAIR.NLM
Possible Cause: Volume data that VREPAIR previously read is not available because a major hardware failure occurred.
Action: Try to get the disk hardware back in working condition. See Disk Errors in the NW 6.5 SP8: Server Operating SystemAdministration Guide. Then run VREPAIR again.