Action

First run fsck -n on the filesystem, to see how many and what type of problems exist. Then run fsck(1M) again to repair the filesystem. If you have a backup of the filesystem, you can generally answer "y" to all the fsck(1M) questions. It's a good idea to keep a record of all problematic files and inode numbers for later reference. To run fsck(1M) yourself, specify options as recommended by the boot script. For example:

# fsck /dev/rdsk/c0t4d0s0

If you don't have a backup, ask an expert to run fsck(1M) for you.