Singler user mode is too late to run fsck on '/'. It's already mounted read-write. You can damage the filesystem doing that.
It will run fsck on the filesystem automatically at boot, so you shouldn't have to do so again when it reaches single-user.
Does 'ls /' or 'ls -l /' give a similar error?
--
Darren
ls -l and ls work ok. Finf gets the following error:
root@nnnnnnnnn: / # find / -name etc
find: cannot open /: I/O error
I noticed in /var/adm/messages the following after the find command ran:
Dec 1 09:55:19 unknown ufs: [ID 879645 kern.notice] NOTICE: /: unexpected free inode 371826, run fsck(1M) -o f
Never seen this before.
Boot from some other media (CDrom, network, other disk...). Then run fsck on the root filesystem.
*don't* do it by booting from that filesystem to single-user.
[cdrom boot....]
# fsck /dev/rdsk/c0t0d0s0
If that clears anything up, check messages for previous hardware errors and make sure you're up to date on patches.
--
Darren