Solaris Common Messages and Troubleshooting Guide


First run fsck -n on the file system to see how many and what type of problems exist. Then run fsck(1M) again to repair the file system. If you have a backup of the file system, you can generally answer "y" to all the fsck(1M) questions. It is a good practice 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
Usually, files lost during fsck(1M) repair were created just before a crash or power outage, and cannot be recovered. If important files are lost, you can recover them from backup tapes.

If you do not have a backup, ask an expert to run fsck(1M) for you.