Phase 2 Error Messages

ROOT INODE UNALLOCATED. TERMINATING

The root inode points to incorrect information. There is no way to fix this problem, so the command stops.

If this problem occurs on the Root filesystem, you must reinstall IRIX. If it occurs on another filesystem, you must recreate the filesystem using mkfs and recover files and data from backups.

ROOT INODE NOT A DIRECTORY. FIX?

The root directory inode does not seem to describe a directory. This error is usually fatal. The typical answer is yes.

DUPS/BAD IN ROOT INODE. CONTINUE?

Something is wrong with the block addressing information of the root directory. The typical answer is yes.

I OUT OF RANGE I=I NAME=F (REMOVE?)

A directory entry F has an inode number I that is greater than the end of the inode list. The typical answer is yes.

UNALLOCATED I=I OWNER=O MODE=M SIZE=S MTIME=T NAME=F(REMOVE?)

A directory entry F has an inode I that is not marked as allocated. The owner O, mode M, size S, modify time T, and filename F are printed. If the filesystem is not mounted and the -n option is not specified, and if the inode that the entry points to is size 0, the entry is removed automatically.

DUP/BAD I=I OWNER=O MODE=M SIZE=S MTIME=T DIR=F (REMOVE?)

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with directory entry F, directory inode I. The owner O, mode M, size S, modify time T, and directory name F are printed. Typically, you should answer no the first time this error appears and yes the second time if you know the files claimed by the other inode.

DUP/BAD I=I OWNER=O MODE=M SIZE=S MTIME=T FILE=F (REMOVE?)

Phase 1 or Phase 1B found duplicate blocks or bad blocks associated with file entry F, inode I. The owner O, mode M, size S, modify time T, and filename F are printed. Typically, you should answer no the first time this error appears and yes the second time if you know the files claimed by the other inode.