string

or more files, so it wants to defer this responsibility to you, the administrator. Data
corruption has probably already occurred.
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
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 don’t have a backup, ask an expert to run fsck(1M) for you.
See Also
For more information, see the section on checking filesystem integrity in the System
Administration Guide, Volume I.
The SCSI bus is hung. Perhaps an
external device is turned off.
Cause
This message appears near the beginning of rebooting, immediately after a "Boot
device: ..." message, then the system hangs. The problem is conflicting SCSI targets
for a non-boot device. Having an external device turned off is unlikely to cause this
problem.
Action
See the message "Boot device: /iommu/sbus/string/string/sd@3,0" for a solution.
Alphabetical Message Listing 183