free inodes

I am getting this in /var/adm/messages:

Jan 6 10:21:00 prod ufs: [ID 879645 kern.warning] WARNING: /: unexpected free inode 377371, run fsck(1M)

Jan 16 09:51:20 prod ufs: [ID 879645 kern.warning] WARNING: /: unexpected free inode 377371, run fsck(1M)

Jan 16 11:44:24 prod ufs: [ID 879645 kern.warning] WARNING: /: unexpected free inode 107621, run fsck(1M)

I did many fsck on / in Single user mode and it did not seem to help.

Anyone has any suggestion?

[497 byte] By [danzak1] at [2007-11-25 23:18:41]
# 1
Just for kicks run a iostat -e and see if your root disk is showing errors. But disks error shows up in /var/adm/messages so not sure if you'll see anything showing up.
swoneill at 2007-7-5 18:07:00 > top of Java-index,General,Talk to the Sysop...
# 2

The disk was replaced recently, in /var/adm/messages I get those inodes errors , and some commands such :find . / -name xx -print terminate with I/O error, which writes in /messages the inode error mentioned in my first post. so there are some certain things that dont work on that disk. because find /user1 -name xx -print where /user1 is another physical disk works just fine.

danzak1 at 2007-7-5 18:07:00 > top of Java-index,General,Talk to the Sysop...
# 3
Sounds like you have a bad disk then. I would run format and look for bad blocks and then reformat the disk to see if that fixes the problem.
swoneill at 2007-7-5 18:07:00 > top of Java-index,General,Talk to the Sysop...
# 4

From a boot cdrom -s you could try the force option to fsck which will ignore the clean flag and fsck all blocks. Example: fsck -o f /dev/rdsk/c0t0d0s0

Note that a cdrom boot will build it's own device tree in memory so your controller # may change from what you are use to seeing so fsck the dev/rdsk that format identifies as your boot disk. If you are mirrored then fsck the mirror as well.

jds2n at 2007-7-5 18:07:00 > top of Java-index,General,Talk to the Sysop...
# 5
The disk was recently replaced, so I do not think it's a disk problem, I booted into S mode before and did the fsck -y thingy, it never helped, but never done the boot cdrom -s as of yet, I'll try that and fsck both boot disks since I have a mirror group.
danzak1 at 2007-7-5 18:07:00 > top of Java-index,General,Talk to the Sysop...