Veritas File System 5.1 SP1 Administrator"s Guide (5900-1499, April 2011)

The remount of the root file system failed. The system will not be usable if the
root file system cannot be remounted for read/write access.
When a root Veritas File System is first mounted, it is mounted for read-only
access. After fsck is run, the file system is remounted for read/write access. The
remount fails if fsck completed a resize operation or modified a file that was
opened before the fsck was run. It also fails if an I/O error occurred during the
remount.
Usually, the system halts or reboots automatically.
Recommended action:
Reboot the system. The system either remounts the root cleanly or runs a full
structural fsck and remounts cleanly. If the remount succeeds, no further action
is necessary.
Check the console log for I/O errors. If the disk has failed, replace it before the
file system is mounted for write access.
If the system won't come up and a full structural fsck hasn't been run, reboot the
system on a backup root and manually run a full structural fsck. If the problem
persists after the full structural fsck and there are no I/O errors, contact your
customer support organization.
V-2-23
WARNING: msgcnt x: mesg 023: V-2-23: vx_unmountroot - root file system is busy
and cannot be unmounted cleanly
Description:
There were active files in the file system and they caused the unmount to fail.
When the system is halted, the root file system is unmounted. This happens
occasionally when a process is hung and it cannot be killed before unmounting
the root.
Recommended action:
fsck will run when the system is rebooted. It should clean up the file system. No
other action is necessary.
If the problem occurs every time the system is halted, determine the cause and
contact your customer support organization.
Diagnostic messages
Dewey kernel messages
200