Solaris Common Messages and Troubleshooting Guide



At boot time the /etc/rcS script runs the fsck(1M) command to check the integrity of file systems marked fsck in /etc/vfstab. If fsck(1M) cannot repair a file system automatically, it interrupts the boot procedure and produces this message. When fsck(1M) gets into this state, it cannot repair file systems without losing one or more files, so it defers this responsibility to you, the administrator. Data corruption has probably already occurred.


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.

See Also

For more information, see the section on checking file system integrity in the System Administration Guide, Volume 1.