Technical article 109985

ncheck -i returns "ncheck: read error <big number>" on SCO OpenServer 5.0.5 and 5.0.6.

OpenServer 5.0.5OpenServer 5.0.6

Written · Last revised

Problem

I run ncheck -i on a known inode number from the root filesystem, and ncheck returns the error:

ncheck: read error <number>

where <number> is usually a very large number, and always the same no matter which inode number is specified.

Cause

The message "ncheck: read error 134511972" means ncheck has failed to read block #134511972 of the filesystem. Blocks are 1KB in size, so these large numbers are usually out of the range of the filesystem, meaning that ncheck is following a bad pointer.

This usually means the filesystem is corrupt, but with SCO OpenServer 5.0.5, 5.0.6 this error is seen on a clean filesystem.

Solution

If there is a chance the filesystem is dirty, go to single-user mode and run:

# fsck  -o  full  /dev/root

If the read error persists, it is due to a problem inherent in SCO OpenServer 5.0.5 and 5.0.6 for which there is currently no solution or workaround.

This problem is scheduled to be addressed in a future release of SCO OpenServer.

From the Xinuos technical article database, record 109985. Reproduced with permission. The original is at www.sco.com/ta/109985, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.